[This place is by Bart Sears, who manages the Android Browser team.Tim Bray]
This bill describes whatever issues when feeding websites with ambulatory variants using large-form-factor Android devices. This bill will be of interest 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 decide to wage either a ambulatory version, a screen version, or a large-form-factor touch figure edition of the site).
Details
With the advent of Android devices with larger modify factors, weve been evaluating the best way for scheme sites to wage a UI pertinent for the different 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 off of the protocol User-Agent brick field to determine whether to wage the flooded place or a ambulatory version.
While large-form-factor Android devices could use User Agent Spoofing to wage a screen User Agent in the protocol header, we recommend against this. There may be place customizations needed for Android devices (for warning changes in the way 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 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, like 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 bourgeois devices), if available.
We recommend that manufactures of large-form-factor devices (where the individual may favour the accepted scheme place over a ambulatory optimized version) remove "Mobile" from the User Agent (and keep the rest of the User Agent as currently implemented). Web sites crapper then key off "Mobile" in the User Agent to decide on which UI edition to inform to the device. So a large screen figure running 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, like Gecko) Version/4.0 Safari/533.1
Where "device" would be replaced with the actualised study of the new device. Sites crapper move to use Android in the User Agent to optimize for Android limited features and crapper also key off of Mobile to determine which UI to present.
Thanks
basyar.com
Tidak ada komentar:
Posting Komentar