Databases
StackOverflow2013
Postsdbo
POServer-side options to deliver different page structure (HTML) to different mobile devices
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POServer-side options to deliver different page structure (HTML) to different mobile devices
    primarykey
    data
    text
    <p>I am researching best practices for developing 'classic' style mobile sites, i.e., mobile sites that are delivered and experienced as mobile HTML pages vs. small JavaScript applications (jQuery Mobile, Sencha, etc.). </p> <p>There are two prevailing approaches:</p> <ol> <li>Deliver the same page structure (HTML) to all mobile devices, then use CSS media queries or JavaScript to improve the experience for more capable devices. </li> <li>Deliver an entirely <em>different</em> page structure (and possibly content) to devices with enhanced capabilities.</li> </ol> <p>I'm specifically interested in best practices for the <strong>second</strong> approach. Two good examples are:</p> <ol> <li>MIT's mobile site: different for Blackberries and feature(less) phones than for iOS &amp; Android devices, but available at the same URLs -- <a href="http://m.mit.edu/" rel="nofollow noreferrer">http://m.mit.edu/</a></li> </ol> <p><img src="https://i.stack.imgur.com/MhPD4.jpg" alt="m.mit.edu side-by-side on two different devices"></p> <ol start="2"> <li>CNN's mobile site: ditto -- <a href="http://m.cnn.com/" rel="nofollow noreferrer">http://m.cnn.com/</a></li> </ol> <p><img src="https://i.stack.imgur.com/02GBm.jpg" alt="m.cnn.com side-by-side on two different devices"></p> <p>I'd like to hear from people here at SO have actually worked on something like this, and can explain what the best practices are for delivering this type of device-dependent structure/content/experience. </p> <p>I don't need a primer on mobile user-agent detection, or WURFL, or any of the concepts covered in other (great) SO threads like <a href="https://stackoverflow.com/questions/6066848/mobile-device-detection-for-rendering-rich-web-content">this one</a>. I've used jQuery Mobile and Sencha Touch and I'm familiar with most approaches for delivering the <em>final</em> mobile experience, so no pointers required there either thanks. </p> <p>What I really would like to understand is: how these specific types of experiences are delivered in terms of server-side detection and delivery based on user-agent groups -- where there's one stripped down page structure (different HTML) delivered to one group of devices, and another richer type of HTML document delivered to newer devices, but both at the same sub-domain / URLs.</p> <p>Hope that all makes sense. Many thanks in advance.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USphillipadsmith
    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. POServer-side options to deliver different page structure (HTML) to different mobile devices
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POServer-side options to deliver different page structure (HTML) to different mobile devices
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POServer-side options to deliver different page structure (HTML) to different mobile devices
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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