What? Developing iOS apps means ensuring they work nicely on a small range of iPhones and/or iPads: generally 6-8 different devices depending how far back the developer wants to go.

On Android, it's a different story: nearly 12,000 different devices out there in the hands of people, with a wider range of screen sizes, processors and versions of the Android software still in use.

Many developers' lack of enthusiasm for Android is down to concerns not just about the costs of making and testing their apps for it, but also the resources required to support them once they're launched, if emails flood in about unspotted bugs on particular models.

Is this fair? Fragmentation, as it's called, may not be solved, but it's become a more-manageable problem – and thus a less-convincing excuse for avoiding Android altogether.

Improved development tools are making porting easier, and there's more data (including Google's own) to help developers decide which Android devices to focus their energies on first. If they're upfront with users about which phones and tablets their app will work on, the support queries aspect becomes less daunting too.

That said, many developers still prefer to launch on iOS, iterate their app over a couple of updates in response to feedback from their users, then tackle Android – with extra time for testing to ensure the app works well, and has Android-specific features (widgets, for example).

You could argue that these developers are making more of an effort to serve Android users, not less. But that may not make the wait for some apps less frustrating.

http://www.theguardian.com/technology/appsblog/2013/aug/15/android-v-ios-apps-apple-google