[gks]

Fragmentation at the API level is the real problem. Not at lack of "built-in features."

An app written for iOS 6 can run on the iPhone 4S, iPhone 4, and iPhone 3GS (not to mention the iPad 2 and 3, and the newest iPod Touches).

An app written for ICS can only run on those 7% of devices running ICS.

This is how fragmentation works. The only fragmentation happening on iOS is for the original iPhone, iPhone 3G, iPad 1, and the old iPod Touches.

The only one that I don't quite grasp is the original iPad. Running on the same processor as the iPhone 4 and is much faster than the iPhone 3GS. Color me somewhat confused by this one.

[diminish]

First, APIs are simply features exposed for developers' use. A map function not supported on a device, means the API isn't supported neither, and if your 3rd party development needs this API, it needs this function, namely access to this feature.

Second, you are confining yourself to fragmentation from a developer perspective, and fragmentation matters for other purposes too.

Third, your Android example is flawed; to just shuffler your argument; a function developed for Android 2.3 can run on 2.3 and later versions. And you only need ICS, in case you need a new "built-in feature" available in ICS. Alas, an ios6 app benefiting from new maps, won't work in a substantial proportion of ios devices.

Fourth, the other side of fragmentation is diversity; and you may write a corporate app, for a pen based samsung galaxy note, with a giant screen and give it to your sales users.