Apple's "fragmentation" chart says more about iOS than Android

This article may contain personal views and opinion from the author.
Apple's
*Writer's note: I started this article last Friday, when Apple first released the image in question. I had hoped to be able to add a new chart to the Apple section which showed more accurately the fragmentation of the iOS device ecosystem. I had asked Chitika to run numbers for me, but as I was told "big data is a tricky thing", and the data has been delayed until next week. But, I didn't want to delay this article anymore. The points all still stand, but I'm sorry I don't have the fancy chart to go along with it. 

Last Friday, Apple released the image that it used during its Worldwide Developers Conference keynote to "prove" that there was no fragmentation in iOS compared to the "problem" with Android. Of course, this is the narrative that Apple wants, and it is maddening how often this argument keeps popping up, and how often the media runs with the flashy headline rather than explaining the issue as it is. The fact of the matter is that Apple's chart doesn't prove anything, all it does is mislabel the argument, and hide the real issues with iOS. 

I have written at length before about how silly it is to lump together the various issues that face Android under the heading of "fragmentation", and even worked to rid our website of using the inappropriate term. I've also written about the issues facing iOS, and how Apple is more than a little hypocritical to be calling out Android on these issues. The truth is that there are issues on both platforms, and in both cases, they are issues that plague developers more than they cause any trouble for consumers.

The truth behind the Android platform distribution chart

Apple's "fragmentation" chart says more about iOS than Android

The chart that Apple has released is the accurate Android platform distribution chart, and it does show accurately exactly what it is designed to, which is different from what Apple uses it for. The point of the Android platform distribution chart is to give developers a guide as to what API level they should use when developing an app. Each API level has certain advantages, and OS features of which developers can take advantage.

Apple took a shot at Google during its keynote calling the chart "the most ideal state of Android" because it only shows Android devices that check in with the Google Play Store. But, counting this way makes perfect sense, because once again: the chart is designed for developers. The change in the way Google counted proved that many users with older devices (Android 2.x) don't ever go to the Play Store to download apps. So, why would a developer care about users that never downloads apps?

There is obviously a user side to the chart, but it is less insidious than Apple would imply. While there is a vocal group of users who know that their devices haven't been updated to the newest version of Android, and are angry about it, the majority of users don't know or care what version of Android they have (repeat: the majority of users, not the majority of PhoneArena readers, I know that you guys are disproportionately in the know on these things.) So, there are users that don't get certain features because they don't have the newest version of Android. For example, only 33% of Android devices are on Jelly Bean, which means 64% of devices don't have Google Now.

But, as we know by now, just because you have the newest version of iOS doesn't mean that you have all the features.

The truth behind the iOS platform distribution chart

Apple has been very clear that just because you upgrade to iOS 6, you shouldn't expect to get all of the improvements, and the same will hold true for iOS 7. The trouble is that Apple doesn't release the information about device distribution in the wild. If you have an iPhone 4S, iPhone 5, iPad 3, or iPad 4, you're in luck and your device got all of the goodies included in iOS 6. However, if you have an older device, you'll be missing some key elements like Siri, turn-by-turn navigation, and FaceTime over 3G. For iOS 7, it's actually worse, because you'll only get the full range of iOS 7 features if you have an iPhone 5. Even if you have an iPad 4 or iPad mini, you won't get the Panorama feature, and iPad mini users also won't get the photo filters. 

Apple's "fragmentation" chart says more about iOS than Android
But, of course, that's just the user side of the iOS platform distribution chart. We can't fully explain the troubles for developers, because the data doesn't exist. We'll try to break it down the best we can: for iOS developers, there is little-to-no interaction between apps, and few hooks into the iOS platform itself, so the iOS version doesn't matter too much when it comes to developing an app. The iOS version does matter, but the far more important metric is screen resolution.

As it stands right now, there are five different screen resolutions in the iOS ecosystem, even when you exclude the iPhone and iPhone 3G neither of which can run iOS 6: the iPhone 3Gs is at 320x480, iPhone 4/4S are 640x960, iPhone 5 is 640x1136, iPad 2/mini are both 768x1024, and the iPad 3 and newer are 1536x2048. (This is where I had hoped to have a chart showing what proportion of the iOS ecosystem is held by the various screen resolutions, but unfortunately, that data is extremely hard to come by.) This is the real issue for developers because iOS does not do responsive design, aside from scaling down app assets made for the 640x960 screen to display on the iPhone 3Gs screen. 

This means that developers have to specifically build assets for each screen resolution, because iOS doesn't do responsive design like Android does. On Android, you build your app once, and it will scale. If you don't build it properly, it may not scale well, but it will still work. On iOS, if you don't build the assets for new devices with different screen resolutions, your app may work, but it won't look good. Apps not updated for the iPhone 5 are letterboxed, "universal" apps without iPad assets run at iPhone size, and lower-res assets on a Retina display look a bit fuzzy compared to properly updated apps. All of this leads to pressure to developers to upgrade apps, but it also causes more work for developers, and inconsistent UI of apps on various devices. 

Conclusion

As I have argued in the past, it isn't that there are no problems with Android, but calling every problem "fragmentation" confuses the issue and places blame in the wrong place. Android has problems with slow updates, which is partially due to Google not making it easier for manufacturers to customize without needing to mess with the system layer itself, and partially due to manufacturers having limited resources to support too many devices, and carriers having absurdly long testing phases. Of course, except for a small, but vocal minority, most users don't really care what version of Android they are using, because the apps still work. Android has issues with apps not scaling well to tablets, but that is a problem with developers not building apps properly. The tools are there, and the users are there as well. Calling it all "fragmentation" makes it sound like all the problems are issues that Google should be able to fix alone. 

On the other hand, the term "fragmentation" works far better for the iOS ecosystem, because Apple controls everything from top to bottom, so if there is a problem, Apple would be the one to fix it. Apple is constantly retiring devices, but that doesn't make them disappear from use. And, just as often, Apple is adding new devices with a higher resolution screen, or different aspect ratio, which causes "fragmentation" problems for developers, because Apple doesn't update the development tools to include responsive design options. Each new upgrade adds new features, but Apple doesn't allow all new features on older devices, so there are "fragmentation" problems for users. The best Apple can say is that most of the userbase has the newest security updates, but if Apple wants to toss around accusations of "fragmentation", it works best if there are no such issues with iOS. Apple can hide them with incomplete charts, but as the saying goes, "People in glass houses shouldn't throw stones."

FEATURED VIDEO

59 Comments

1. ihatesmartphone unregistered

Key Lime Pie is the solution for fragmentation on Android :D

3. Mxyzptlk unregistered

That's what ICS was supposed to be for.

12. darkkjedii

Posts: 30833; Member since: Feb 05, 2011

Exactly. Frag isn't going away, as long as hardware limits what can be ran on said device.

47. taz89

Posts: 2014; Member since: May 03, 2011

Google are tackling "fragmentation" just not by getting is updates but through api levels and putting all there core apps on the play store..Google introduced Google play services so regardless what os you are on you can usually get new features same goes with getting there core apps on the play store..over the years they have taken there system apps like gmail maps and recently the keyboard out of the os and put it into the play store so more people are likely to get new features etc without having to wait for an os update..think of it this way if apple want to update there email,keyboard,maps or app store etc they have to do a OS update where as if Google want to do the same thing its all done through the play store...both have fragmentation but of different types.. Google has fragmentation of what build of android people are on and imo iOS has fragmentation of what features are available on what...just recently Google added new features to Google now via an app update but cannot just update siri via an app update... Neither solutions perfect but don't think its an "apples to apples" comparison the way apple likes to suggest it is.

14. protozeloz

Posts: 5396; Member since: Sep 16, 2010

Not at all ICS united tablet and phone UI into a single thing... But then again you already knew that

25. roldefol

Posts: 4744; Member since: Jan 28, 2011

ICS was never going to end fragmentation, because not all extant devices were capable of running it (similar to iPhone 3G not getting iOS 6). And if they didn't have the resources for it, manufacturers only updated their most popular/most recent devices.

28. icyrock1

Posts: 307; Member since: Mar 25, 2013

Actually, I think that them updating key apps outside of new releases (music, books, play, etc) is there plan to ease "fragmentation". They can bypass the carrier and manufacturers and update phones that way.

51. joey_sfb

Posts: 6794; Member since: Mar 29, 2012

Mxyzptlk is just a troll for Apple Inc.

55. roldefol

Posts: 4744; Member since: Jan 28, 2011

Apple wouldn't stoop that low. He's just a troll.

5. MichaelHeller

Posts: 2734; Member since: May 26, 2011

And, there's the first person to miss the point on the Android side...

10. exsymbian

Posts: 6; Member since: Mar 22, 2013

KLP wont solve anything. Google should enforce manufacturers to provide at least two incremental android updates for their products.,

2. AppleHateBoy unregistered

Michael. You are my hero.

8. abcdefgh

Posts: 471; Member since: Mar 29, 2013

people with glass house should not play ANGRY BIRDS BAD PIGGIES lol.XD

15. darkkjedii

Posts: 30833; Member since: Feb 05, 2011

You're gonna get yourself limited with the spamming dude

9. SellPhones82

Posts: 569; Member since: Dec 11, 2008

Great read Michael! I always found it funny that Apple allowed older devices to "upgrade" to a newer OS version, minus most of the the key new features, yet call out Android for fragmentation. So I guess Google should just remove Google Now and Project Butter from JB and then release it to the older non-supported phones and then fragmentation would be gone! Well, at least according to Apple it would...

52. joey_sfb

Posts: 6794; Member since: Mar 29, 2012

Well said!

11. SonyXperiaNexus

Posts: 374; Member since: Oct 01, 2012

Plzzzzz add that resolution chart as a separate article if you get it, i wanna see it. BTW awesome article michael, your effort really shows.

18. MichaelHeller

Posts: 2734; Member since: May 26, 2011

If Chitika can get the info (which is hard to generate in the first place), I hope to be able to have that chart in the next couple weeks or so.

45. roscuthiii

Posts: 2383; Member since: Jul 18, 2010

Careful... might get slapped with a libel lawsuit.

13. speckledapple

Posts: 902; Member since: Sep 29, 2011

Well written Michael. I enjoy reading insightful articles such as this. Its not about fanboys just about the facts of the matter. I think iOS is a strong OS and Apple certainly has done a great job making sure it is the beast they want it to be. But it has its problems as well and fragmentation is one of many. Though just as Android has its own issues, much of it on either os comes down to developers. As you said, there are all kinds of tools to create a better experience for users and they need to do that. Developers need to step it up.

21. JunkCreek

Posts: 407; Member since: Jul 13, 2012

but apple doesn't make that tool to their devs. devs must make all apps and games specifically for each device. and it is harder task to do than testing the apps and games for different hardwares and chips. apple devs must built it from the scratch again while on android the devs can only edit here and there then add it to the manifest.

16. JunkCreek

Posts: 407; Member since: Jul 13, 2012

yes, i thought about it also. i always wonder how suffer the devs builds apps and games for even ip3 and ip3gs and ip4/s and ip5 and also ipad2, 3 and 4. while on android, the devs could just attach graphics files for low, mid and high res.

17. Telemike

Posts: 43; Member since: Nov 30, 2012

What Google needs to do and I think I read they are doing this...is to make core components of the Android OS updatable from the Play store rather than from the Carrier. IF Google can somehow separate all the carrier related radio stuff from the Core OS, then updates to the OS should be faster and easier bypassing the Carrier.

53. kabhijeet.16

Posts: 884; Member since: Dec 05, 2012

Google is actually doing this.. Releasing all core apps one by one into Play Store. Latest examples are proprietary Keyboard, Camera app, etc.

19. rantao333

Posts: 345; Member since: May 21, 2013

and yet, i found myself crash most of the time with android apps....

22. JunkCreek

Posts: 407; Member since: Jul 13, 2012

buy htc, huawei, lg or motorolla..you get some incompactible if using samsung device. you can't even make swap your internal "sdcard" storage to real sdcard so you can get larger storage. but for 2-8gb "sdcard" internal storage, i think it is enough for us to install almost any apps and games. but if you only had 512mb, you'd feel the ass in the pain... :p

43. -box-

Posts: 3991; Member since: Jan 04, 2012

I have an HTC (it's sat dormant since my wife got a GS3) and both crash and freeze with disappointing frequency.

20. spideyhead256

Posts: 148; Member since: Nov 05, 2012

Lol love the thumbnail micheal.

23. MichaelHeller

Posts: 2734; Member since: May 26, 2011

Thanks! (side note: it's spelled Michael.)

27. spideyhead256

Posts: 148; Member since: Nov 05, 2012

sorry michael didn't pay attention!

* Some comments have been hidden, because they don't meet the discussions rules.

Latest Stories

This copy is for your personal, non-commercial use only. You can order presentation-ready copies for distribution to your colleagues, clients or customers at https://www.parsintl.com/phonearena or use the Reprints & Permissions tool that appears at the bottom of each web page. Visit https://www.parsintl.com/ for samples and additional information.