Tuesday, February 7, 2012

Android inconsistencies

For an O/S authored by Google, Android (at least with Honeycomb 3.2) seems to handle web content in an inconsistent manner. The stock browser, Firefox or Safari maybe different -  I haven't tried them yet, interprets the user-agent string incorrectly.

I can understand that a website that wants to render a page on a phone differently to what you would see if you accessed a page on your computer (Real Estate pages for example). However, Google with their Blogger product renders the page as if it is a desktop page and has to be forced to look like a phone. There is no tablet rendering of Blogger.

I may have this wrong but I thought a tablet was a "mobile" product. To compete with Apple the user-agent string issue needs to be sorted. The real-estate pages look much better on the iPad without have to make obscure (for most users) config changes. The coders for the real-estate website know how to identify an iPad, Google need to do a better job so that coders know how to handle the Android User String. AND so do the coders of Google Blogger.


This is the user-agent string from my Android device:
Mozilla/5.0 (Linux; U; Linux Ventana; en-ca; Transformer TF101 Build/HTK75) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/8.0 Safari/534.13

No comments: