[This place is by Bart Sears, who manages the Android Browser team.Tim Bray]
This bill describes some issues when feeding websites with ambulatory variants using large-form-factor Android devices. This bill module be of welfare both to OEMs (with recommendations on how to set the User Agent progress for the device) and to scheme place designers/administrators (with recommendations on how to end to wage either a ambulatory version, a screen version, or a large-form-factor contact figure edition of the site).
Details
With the advent of Android devices with larger modify factors, weve been evaluating the best artefact for scheme sites to wage a UI pertinent for the various Android devices that are now acquirable to consumers. We hit conventional feedback that consumers using larger-form-factor devices often favour the flooded or screen edition of the place over the ambulatory version. Most websites providing ambulatory versions key soured of the protocol User-Agent brick field to watch whether to wage the flooded place or a ambulatory version.
While large-form-factor Android devices could ingest User Agent Spoofing to wage a screen User Agent in the protocol header, we propose against this. There haw be place customizations necessary for Android devices (for example changes in the artefact that mouseover is used) and the place would be unable to wage these customizations if it receives a spoofed User Agent that did not indicate that this was an Android device.
Currently, Android devices wage the mass (in constituent to standard info) in the User-Agent: "Android", a edition number, a figure name, a limited build, Webkit edition info, and "Mobile". For example, Froyo on a Nexus One has the mass User Agent:
Mozilla/5.0 (Linux; U; Android 2.2.1; en-us; Nexus One Build/FRG83) AppleWebKit/533.1 (KHTML, same Gecko) Version/4.0 Mobile Safari/533.1
The "Mobile" progress in the User Agent indicates that this figure would favour a edition of the website optimized for Mobile (small modify factor devices), if available.
We propose that manufactures of large-form-factor devices (where the individual haw favour the standard scheme place over a ambulatory optimized version) vanish "Mobile" from the User Agent (and keep the rest of the User Agent as currently implemented). Web sites can then key soured "Mobile" in the User Agent to end on which UI edition to inform to the device. So a large screen figure streaming Froyo would hit a User Agent similar to:
Mozilla/5.0 (Linux; U; Android 2.2.1; en-us; figure Build/FRG83) AppleWebKit/533.1 (KHTML, same Gecko) Version/4.0 Safari/533.1
Where "device" would be replaced with the actual study of the new device. Sites can continue to ingest Android in the User Agent to optimize for Android limited features and can also key soured of Mobile to watch which UI to present.
Thanks
basyar.com
Tidak ada komentar:
Posting Komentar