Android fragmentation is a huge problem. The fact that there are hundreds of different hardware devices running over half a dozen different versions of Google’s OS makes it annoying for users, but makes it an especially devastating issue for developers trying to make a business out of the Android ecosystem.
This was highlighted by the recent release of Temple Run on the Android platform. A previously (very) successful game on iOS, it was brought over to Android in order to take advantage of the huge number of devices that run the OS. And it has already hit 1 million downloads in just 3 days, good, even for a free app. But very quickly, the developers of the app discovered the pitfalls of fragmentation:
99.9% of support emails are complaining their device isn’t supported. We currently support 707 devices. Mindblowing.
— Natalia Luckyanova (@nattylux) March 27, 2012
F**k it, we'll do it live!
Our biggest ever edition of TNW Conference is fast approaching! Join 10,000 tech leaders this May in Amsterdam.
Natalia Luckyanova of Imangi tweeted out that most of their 1200 emails over the past 12 hours of release had been devoted to the fact that the app just didn’t work on one of the hundreds of devices owned by those users.
But then Developer David Smith replied to her, saying that he had some 1443 unique devices on the logs for his Android app Audiobooks (also Free). We contacted Smith to chat with him a bit about whether the fragmentation of Android software and devices had affected the process of making software for the platform. What he shared with us was shocking.
Smith confirmed for us that his Audiobooks app has been run on 1443 different Android devices by its users. This makes it absolutely impossible to determine whether an app will run without problems for all of your customers. To drive home how ridiculously shattered the Android landscape is, check out this list of the most used single devices based on 1.3M downloads of his app:
- Droid X (7.8% of users)
- Samsung Galaxy S2 (4.3%)
- Droid (4%)
- HTC Desire HD (4%)
- HTC Evo 4G (3.7%)
- Droid incredible (2.3%)
This is insanity when you look at it from the standpoint of an iOS developer, who has to support only a handful of hardware varietals. Of course, Android’s very nature causes this. It is designed to work on an enormous array of hardware with all kinds of different components and feature sets. The way Android is designed to be used means that developers will likely always have to deal with this kind of fractured hardware landscape, it’s a fact of life on the platform.
Smith says that with just 8-10 iOS devices (the pic above is from last summer and shows a dozen), he can cover 100% of his users. There’s just no way to keep every version of hardware around for quality assurance on every permutation of Android. “I have a handful of Android devices, but since the range is so spread out trying to cover a large array of devices just isn’t practical.”
“And that is only half the picture,” Smith says. “The other side is Android version, where 50% of users are on 2.3.3 and then the rest are are on things ranging from 1.6 to 4.0.3.”
The contrast with developing for iOS is sharp. “With iOS, it’s usually safe to maintain compatibility about one year back,” Instapaper developer Marco Arment told us a couple of weeks ago. “So today, iOS 4 is a very safe minimum. Very soon, iOS 5 will be. Sometimes, an OS update offers so much for developers that it’s worth jumping the gun a bit.”
“Those two things combined make helping users with problems almost impossible,” Smith says, and support emails are a huge part of that, with the ‘vast majority’ related to some issue running the app on a hardware and Android version combination that has caused an issue. “The hardest part is that you can’t drop support for old things because such a high number of users are stuck, so it is often the newer devices that are the trickiest to support well.”
All of this leads to low reviews of the app, an enormous volume of support email dedicated to errors due to versioning or hardware flukes and lost revenue for the developer.
“It is a nightmare…the worst part for me is that ultimately it means that I have a lot of grumpy users that I just can’t realistically help. It just doesn’t make sense (economically) to run down every bug that is specialized to a particular device/OS combo.”
This is especially important because the Android platform is generally far less profitable than Apple’s iOS. People expect to pay less for Android apps and they’re vocal about it. Check out this thread on Reddit about the recently released (and incredibly beautiful) doubleTwist Alarm app for an example of the way that some Android users view paying even $1 for an arguably AAA title.
“I think most droid users have never heard of the android market, whereas most iOS users get their phone and then immediately go looking for apps. That is just anecdotal, but it seems like a lot of people just view it as the ‘free’ phone option at the cell phone store…sure there are people who are deliberately choosing it but I’d guess that is a minority.”
The chart on the right shows how Smith’s apps were performing on the App Store, Amazon and Google markets last July. Note that his apps are actually ranked higher on Android than they are on iOS. This is a systemic problem and one that makes the additional headache of supporting hundreds of devices running aging versions of Android even less worthwhile for developers. Especially those with limited resources.
In a report today, Flurry Analytics paints a slightly more optimistic picture of the Amazon App Store, which it says generates $0.89 for every $1 that the App Store makes, but the Google Play market still comes in a dismal third at $0.23 .
I asked Smith if he thought that there was any practical solution to the problem of having to support so many versions of an app.
“The only way it would get better realistically is if there were one or two phones that had runaway success and stayed that way for a long time…where their sales would dwarf the previous install base.”
Due to its approach, Apple’s ecosystem offers many benefits for developers. There are only two screen sizes in the entire pantheon of Apple’s mobile products and as many as 75% of users are already upgraded to iOS 5, allowing developers to support newer features and phase out older versions of iOS quicker.
In the case of hardware, Apple’s path has been one of restraint and focus. The business model of Google is an antithesis to this kind of thinking, which is fine. It’s great to give consumers more options and to have a strong alternative to iOS. Android fills a necessary role in many embedded systems and unique devices. And Ice Cream Sandwich is a bold step in a very good direction, not compromising the original vision of Android as a more customizable and flexible OS, while injecting it with more polish and logic.
But a platform does not exist on first party apps and a polished OS alone. If it did, then Windows Phone would be destroying Android in adoption and not just in users satisfaction surveys. A platform needs developers and it needs them to be able to please their customers. Apps are the key to any successful platform and if Google doesn’t work to improve the very real fragmentation issues, it will continue to be a less attractive option for the very people Android needs to survive.