January 29th, 2011
Ever since 2009, I’ve been hearing a lot in tech blog posts and the media about “Android fragmentation.” No actual Android user I know in real life has complained about it, though. I’ve also noticed that criticisms about so-called Android fragmentation tend to be quite vague.
For Joe Average, this created an ultra-confusing marketplace where operating system versions changed every few months. It also meant that compatibility issues were inevitable.
What compatibility issues? Examples?
But one of the problems that Android has is that it’s very fragmented. Even at the smartphone level, different devices run different versions of the Android OS and that means that not every app runs every device.
What apps? Examples?
On my MyTouch 3G (the original), I’ve used just about every version of Android there is. 1.5, 1.6, 2.0, 2.1, 2.2. Some rooted. Some OTA from T-Mobile. I’ve experienced no problems as an end user in terms of applications having compatibility issues. Some of the more graphics-intensive apps don’t run well on my 528 MHz processor with 192 MB of RAM, but that’s regardless of what version of Android I have—my phone just isn’t that powerful, so Angry Birds will just not run well on it. That has nothing to do with “fragmentation.”
Some people who want to make a big deal about Android fragmentation will point to an interview with one of the Angry Birds makers (Peter Veterbacka) in which he says
Android is growing, but it’s also growing complexity at the same time. Device fragmentation not the issue, but rather the fragmentation of the ecosystem. So many different shops, so many different models. The carriers messing with the experience again. Open but not really open, a very Google centric ecosystem.
but they seem to ignore that when asked directly about Android fragmentation being an issue, he says
Fragmentation on the device side is not a huge problem, but Steve is absolutely right when he says that there are more challenges for developers when working with Android. But that’s fine, developers will figure out how to work any given ecosystem and as long as it doesn’t cause physical pain, it’s ok;-) Nobody else will be able to build what Apple has built, there just isn’t that kind of market power out there.
That doesn’t mean that model is superior, it’s just important to understand that Apple is Apple and Google is Google. Different. And developers need to understand that. Different business models for different ecosystems. And wouldn’t forget about Nokia and MeeGo either, new leadership always tends to shake things up and create opportunity. And HP-Palm. And RIM. And even Microsoft. It’s a fragmented world.
If you actually own and use an Android device as your primary phone, how (with specific examples) have you found so-called “fragmentation” affecting you? Which applications do not work on your version of Android that would work on another version? Why do you think people don’t make as big a deal about “Windows fragmentation” (Windows 98, 2000, XP, Vista, 7) or “Mac fragmentation” (Panther, Tiger, Leopard, Snow Leopard)? Am I crazy for thinking Android fragmentation is a non-issue?