Re: Single Page Applications

Lots of good discussion and accurate information so far. The compelling reason for an SPA is not just architectural, it has to do with where all web content is going: To mobile devices. Unless you truly hate your users, conventional multi-page rendering and submittal is bandwidth hungry and slow to load. Caching helps but being a good citizen when you develop a mobile web application means that you send as little data over the wire as possible (charging per mb or gb is a trip to the 1990's that mobile wireless providers have made). SPA's using local storage and other caching techniques save the user bandwidth == $$.

Anything you develop today should be responsive and use SPA and other techniques to minimize bandwidth utilization. The industry has gone mobile, developers need to catch up! The rush to mobile devices while eschewing the traditional PC is reason enough to go SPA and responsive.

Pete


On 5/22/2015 3:12 PM, Nathan Andelin wrote:

Probably a poor choice to start a topic that has such far reaching impact
as this, on a Friday afternoon. Maybe we can pick it up on Monday.

This is a natural extension of the discussion this past week about which
server architecture might be best to support single page applications, or
SPA's.

I'll begin by asking, what is a single page application? Popular terms like
SPA tend to get hijacked by anyone interested in promoting a product.

Based on my readings, SPAs are essentially static content (HTML, CSS,
JavaScript), which have UI components which adapt to "data", which may be
downloaded after the static content.

SPAs are said to be "responsive" in that pages are not "refreshed"; just
page elements which adapt visually as data is refreshed asynchronously over
the life cycle of the application.

Much of the promotion of SPAs seems to originate from frameworks like
Angular and Bootstrap, which supplement HTML with "declarative elements"
such as <tags> and <tag attributes> which are bound to JavaScript and CSS
libraries.

SPAs have far reaching implications in that traditional server-based
frameworks and tools which are designed to generate HTML, manage sessions,
and provide gateways to data appear to be superfluous; perhaps obsolete.