Re: A Responsive Single Page App (SPA) with 3 Issues to Consider

On 7/15/2015 12:33 AM, Booth Martin wrote:

It is sounding like it can do everything that separate pages can do but
with more complexity. So, all of this work is just to save bandwidth?
Thats it? As we move towards 15 mbps speeds we are worrying over saving
a few text strings?

I think I am missing something. I am not seeing something that is clear
to everyone else.

There are (at least) two separate concepts being discussed in this thread:

Single Page Application (SPA)
Responsive application

An SPA is a way to minimise bandwidth, but mostly the idea is to provide
a more desktop-like user experience.

When you interact with a web browser, as a user you have a certain
expectations. For example, you don't want to press F12 to 'go back' one
screen and you don't want to press F14 to 'update'. Perfectly normal
for a 5250 app, but you don't expect that for a web app. Just as you
have different expectations between a 5250 app and a web app, you have
another set of expectations for an app rendered on a mobile.

A responsive application self-alters the... the interface so that the
user experience more closely matches her expectations; expectations
which change depending on the device she's using to interact with.

These two concepts can be implemented separately, or, as Kelly is doing,
together, to enhance the user's experience above what either could do alone.