Originally Posted by majjo
That said, fragmentation is definitely an issue with the platform, and its just the nature of the beast with how android works. The situation is improving, as OEMs move away from heavily bloated skins, and incorporate much more AOSP features and follow the holo design guidelines. (eg. sense 5.0)
I've been hearing that for years now. I'm so sick of hearing "soon" when it come to Android. Godot doesn't make you wait this long.
I have doubts that their terms of their SDK from late last year will do anything. It's just too out of control.
Last I checked 40%
are on Android 4.x, and every major new phone that I know of is launching with Jellybean.
Again, Google has fraked this up so bad that even those that use their OS and HW consider anything on 4.x as a single development platform despite 4.x covers 4 stages of API development and even both Jelly Bean and ICS cover two different API stages, each. And even among those there is no method to this madness. For instance, API level 14 is 4.0 to 4.0.2 and then API level 15 starts not with 4.1
but with 4.0.3 to 4.0.4, with API level 16 starting at 4.1.
iOS is highly structured and very clear: http://en.wikipedia.org/wiki/IOS_version_history
6.0 is a huge update with a lot of changes. Then 6.0.1 addresses bug fixes, security updates, reliability issues as it's a tertiary update. Same goes for 6.0.2. Version 6.1 actually adds some features, but not any API additions and the updates are adding to already existing apps or services. You can do this through the entire chain of updates with little to no variation. It shows a focused company with a clear path and structure to it. That's what I want to see when it comes to engineering.Edited by SolipsismX - 2/26/13 at 5:00am