Databases
StackOverflow2013
Postsdbo
POAre SPAs (Single Page Applications) suitable for sites aimed for mobiles?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAre SPAs (Single Page Applications) suitable for sites aimed for mobiles?
    primarykey
    data
    text
    <p>I am planning to create a website with around different 20 views/pages primary for mobile phones.</p> <p>If I want to focus on a making the user experience very responsive (as in rapid) while switching between the pages, is creating the site as a Single Page Application a good idea?</p> <p>I know there are many tips you can do to increase the overall performance of a mobile website:</p> <p><a href="http://www.slideshare.net/blazeio/mobile-web-performance-optimization-tips-and-tricks">http://www.slideshare.net/blazeio/mobile-web-performance-optimization-tips-and-tricks</a></p> <p>But my primary concern is that the client-side JavaScript (such as AngularJS) would actually decrease the performance, when it needs to do AJAX-requests and then show/hide/create elements dynamically, compared to creating a traditional HTTP request to get page and its contents and showing that directly.</p> <p>Any resources or comments that could help me understand what architecture would be more suitable for mobile sites?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. UScorgrath
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAre SPAs (Single Page Applications) suitable for sites aimed for mobiles?
      1. UScorgrath
      1. VTBountyStart
    2. VO
      singulars
      1. POAre SPAs (Single Page Applications) suitable for sites aimed for mobiles?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAre SPAs (Single Page Applications) suitable for sites aimed for mobiles?
      1. This table or related slice is empty.
      1. VTDownMod
    1. COI think this depends on the amount of processor-expensive content each page will have. In my experience, when you want the best user experience, an SPA is the way to go. I used jQuery mobile for a couple of small applications about 18 months ago. Despite the framework's shortcomings, the UX was really nice when compared to one that makes the screen go white while waiting for a new page to load. [This discussion](http://programmers.stackexchange.com/questions/144717/advantages-and-disadvantages-of-building-a-single-page-web-application) might provide some good insight.
      singulars
      1. POAre SPAs (Single Page Applications) suitable for sites aimed for mobiles?
      1. USjpodwys
    2. COAJAX requests aren't necessarily worse, as long as you don't do too many of them. Also, if the device supports http pipelining (keep-alive), then those requests can go over the same connection which shouldn't be too bad. But yes, predicting as much of the page that the user wants to see before hand is much better. I've noticed that showing and hiding elements isn't a good design in most cases anyway, because it usually means the site owner didn't consider what I wanted to see before hand and left it up to me in a way.
      singulars
      1. POAre SPAs (Single Page Applications) suitable for sites aimed for mobiles?
      1. USDavid d C e Freitas
    3. COYea. Usually you can get away with using RequireJS and fetch on-demand. However, I dont think that would be a good idea for a mobile site, where I basically want as few requests as possible.Meaning, if I want multiple views with an SPA setup on a mobile device, then I guess I need to try and get all the pages into one HTML at init(?).
      singulars
      1. POAre SPAs (Single Page Applications) suitable for sites aimed for mobiles?
      1. UScorgrath
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload