[This post is by Bart Sears, who manages the Android Browser team.Tim Bray]
This bill describes whatever issues when browsing websites with mobile variants using large-form-factor Android devices. This bill will be of interest both to OEMs (with recommendations on how to ordered the User Agent string for the device) and to scheme place designers/administrators (with recommendations on how to end to wage either a mobile version, a concealment version, or a large-form-factor touch figure edition of the site).
Details
With the advent of Android devices with large modify factors, weve been evaluating the prizewinning artefact for scheme sites to wage a UI pertinent for the various Android devices that are today acquirable to consumers. We hit conventional feedback that consumers using larger-form-factor devices ofttimes favour the flooded or concealment edition of the place over the mobile version. Most websites providing mobile versions key soured of the protocol User-Agent brick earth to watch whether to wage the flooded place or a mobile version.
While large-form-factor Android devices could ingest User Agent Spoofing to wage a concealment User Agent in the protocol header, we propose against this. There haw be place customizations necessary for Android devices (for warning 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 inform that this was an Android device.
Currently, Android devices wage the mass (in addition to accepted 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" string in the User Agent indicates that this figure would favour a edition of the website optimized for Mobile (small modify bourgeois devices), if available.
We propose that manufactures of large-form-factor devices (where the individual haw favour the accepted scheme place over a mobile optimized version) remove "Mobile" from the User Agent (and ready the rest of the User Agent as currently implemented). Web sites crapper then key soured "Mobile" in the User Agent to end on which UI edition to inform to the device. So a large concealment figure streaming Froyo would hit a User Agent kindred 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 actualised study of the new device. Sites crapper continue to ingest Android in the User Agent to optimize for Android limited features and crapper also key soured of Mobile to watch which UI to present.
Thanks
basyar.com
Tidak ada komentar:
Posting Komentar