3 ms·
Don't think there's any fragmentation problems on Android OS? Just try creating a mobile website that supports common "modern" devices. Have fun trying to wrap
by thathonkey 12y ago
Don't think there's any fragmentation problems on Android OS?
Just try creating a mobile website that supports common "modern" devices. Have fun trying to wrap your brain around all the idiosyncrasies across various versions and browser implementations (Android Stock vs Chrome etc) that will endlessly dirty your code if you want the site to look at all correct in a majority of Android devices.
The Android emulator is pretty nice... once you figure out how to set it up for whatever device you're trying to test. It's a ridiculous resource hog though by default (there are ways to mitigate this if you're on an Intel chip). Say what you will about simulation vs. emulation but the iOS Simulator is a dream to work with (again, for web development) and I've never had it mislead me even though it isn't truly emulated. But then you realize there is no way to install the Chrome browser unless you are hooked up to the Android Marketplace (even if you're on the latest version of OS). The best you can get is Chromium, which is a pain to install and doesn't work on some AVDs.
All that ranting aside, I've never had a problem with screen sizes, even when working on responsive stuff. But, yeah, Android is basically the Internet Explorer of the mobile space. You'll keep hearing "oh the next version will fix that!" and it may... but you'll be stuck supporting the versions that are broken for years to come.
- kllrnohj 12y agoThat's fragmentation in web browsers, that has fuck-all to do with the OS or Android's SDK or anything the author is talking about.
- thathonkey 12y agoOh thanks for breaking it down for me. When it comes to web development, for all intents and purposes, they can be thought of as one in the same since the browser version issued with a device is tied to OS version[1]. Of course some users will upgrade OS and/or browser, independently in some cases, which complicates things further. [1] http://jimbergman.net/webkit-version-in-android-version/ http://jimbergman.net/webkit-version-in-android-version/
- stusmall 12y agoIn that link he mentions it but it bears a little breaking down. His chart is showing the versions of the rendering engine that is used to back a WebView. It isn't for the browser included with the phone. Google has requirements how WebViews are implemented but the requirements for the default browser are pretty light. Even if the user doesn't swap out their browser you don't know what you might get. See section 3.4 of the CDD for the requirements.
- thathonkey 12y ago"Even if the user doesn't swap out their browser you don't know what you might get." My point exactly.