Linked by Thom Holwerda on Thu 3rd Jan 2013 23:42 UTC
Google So, Gingerbread has finally dropped below 50% of devices accessing Google Play. Ice Cream Sandwich has almost hit the 30%, and after six months, Jelly Bean (4.1 and 4.2) almost hit the 10%. Google's page listing these numbers is like a trainwreck in slowmotion.
Thread beginning with comment 547232
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Trainwreck?
by geertjan on Fri 4th Jan 2013 12:32 UTC in reply to "RE: Trainwreck?"
Member since:

I'm a developer and have developed for many (mobile) platforms, and I can tell you Android is my favorite to program for. The fragmentation problem is very much exaggerated, it's hardly worse than on iOS.

It doesn't matter if only a small percentage of users are on iOS 4, you still have to be backwards compatible. So you have the same problems on iOS.

Backwards compatibility for Android 1 was a pain in the ass though. But since Android 2 it's easy to handle. And everyone programs for Android 2.2 or higher anyway now.

So the way I see it:

- Android developers are fine with Android fragmentation.
- Average Android users are fine with Android fragmentation (don't even know what an OS is, don't care about updates).
- Advanced Android users that do care about updates can get a Nexus device.

It seems the only people whining about it are non-Android users/developers.

Reply Parent Score: 7

RE[3]: Trainwreck?
by Bill Shooter of Bul on Fri 4th Jan 2013 15:20 in reply to "RE[2]: Trainwreck?"
Bill Shooter of Bul Member since:

IOS, I would say is in someways worse. The current version of Xcode no longer has support for the iphone 3G or the first couple of generations of ipod touches. You simply can't do it ( without an incredible amount of hackery). So you either set up two dev stations and never ever update one to the newest version of xcode to do point releases on an app compatible with old and new. If you want to support newer features as well, you'd have to fork your app and submit it as a different one.

At least with Android you can create a one off version for that one customer still rocking donut without too much difficulty or requiring another computer.

Reply Parent Score: 4

RE[3]: Trainwreck?
by qbast on Sat 5th Jan 2013 17:35 in reply to "RE[2]: Trainwreck?"
qbast Member since:

You are fine, I am not. How do you provide good video streaming for Android? 3.x and higher have HLS support, so you can do adaptive streaming easily. Cool. But 2.x? Either Flash+OSMF (abysmal performance), RTSP (often blocked on 3G) or just mp4 over http - two last option are not adaptive (say hello to buffering and/or low quality). So yes, for me Android lack of updates is a big problem.

Reply Parent Score: 2

RE[3]: Trainwreck?
by lustyd on Mon 7th Jan 2013 11:19 in reply to "RE[2]: Trainwreck?"
lustyd Member since:

"It doesn't matter if only a small percentage of users are on iOS 4, you still have to be backwards compatible. So you have the same problems on iOS. "

I disagree. If a user is on iOS 4 then they know they have an old phone and they know they are out of date. When a user is on Android 2.3 they may have bought the phone that day meaning they think they have the latest and greatest. They will then find they cannot update to the latest. To the developer, this means that on iOS you may be forgiven for not supporting the older versions but on Android you definitely won't be.

Reply Parent Score: 1

RE[4]: Trainwreck?
by zima on Thu 10th Jan 2013 23:57 in reply to "RE[3]: Trainwreck?"
zima Member since:

With Apple there's fragmentation based on hardware, not much different. Apple actively promoted, pushed iPhone 3GS for a really long time - so that there are certainly people who bought it new fairly recently. Not even all the advertised OS functions work on it; plus there are demanding applications which won't run...

Reply Parent Score: 2