Android's "Extreme Fragmentation," Colorfully Visualized by TweetDeck's Team
engadget.com
Android's "Extreme Fragmentation," Colorfully Visualized by TweetDeck's Team
1–10 of 16 posts
Re: Android's "Extreme Fragmentation," Colorfully Visualized by TweetDeck's Team
#2Re: Android's "Extreme Fragmentation," Colorfully Visualized by TweetDeck's Team
#3Original source: http://blog.tweetdeck.com/android-ecosystem
Re: Android's "Extreme Fragmentation," Colorfully Visualized by TweetDeck's Team
#4Re: Android's "Extreme Fragmentation," Colorfully Visualized by TweetDeck's Team
#5Re: Android's "Extreme Fragmentation," Colorfully Visualized by TweetDeck's Team
#6Kind of like IBM compatibles? Or maybe Java-capable phones?
Diversity of hardware is not something to be afraid of. Yes, it can cause a few difficulties, but it also provides a much wider market to sell to at the same time.
Choice is good.
Re: Android's "Extreme Fragmentation," Colorfully Visualized by TweetDeck's Team
#7"extreme fragmentation." Kind of like IBM compatibles? Or maybe Java-capable phones? Diversity of hardware is not something to be afraid of. Yes, it can cause a few difficulties, but it also provides a much wider market to sell to at the same time. Choice is good.
I know several developers who frequently complain about Android fragmentation, but then again they might just be spoiled by iOS.
WP7 doesn't really allow for any oem/carrier skinning though...
Re: Android's "Extreme Fragmentation," Colorfully Visualized by TweetDeck's Team
#8"extreme fragmentation." Kind of like IBM compatibles? Or maybe Java-capable phones? Diversity of hardware is not something to be afraid of. Yes, it can cause a few difficulties, but it also provides a much wider market to sell to at the same time. Choice is good.
The second pie chart is split by OS ID strings. While it shows fragmentation, it hugely exaggerates it because it counts all builds of a given version, say of 2.2, as unique even though they are built from the same or similar (i.e. bugfixed) sources. Besides that, there a a lot of single digit builds that are unidentifiable based on the name - what version of Android are the two copies of "Interceptor V5", for instance?
As a thought exercise, imagine what that pie chart would look like for any phone OS other than iOS. Symbian http://en.wikipedia.org/wiki/Symbian_OS and Windows Mobile http://en.wikipedia.org/wiki/Windows_mobile (soon to become fragmented again as WP7) both have several major version (i.e. true fragmentation) and many, many different handset manufacturers and flavors within each major version.
Re: Android's "Extreme Fragmentation," Colorfully Visualized by TweetDeck's Team
#9"extreme fragmentation." Kind of like IBM compatibles? Or maybe Java-capable phones? Diversity of hardware is not something to be afraid of. Yes, it can cause a few difficulties, but it also provides a much wider market to sell to at the same time. Choice is good.
Well they do praise it, albeit it in an odd way. I know several developers who frequently complain about Android fragmentation, but then again they might just be spoiled by iOS. WP7 doesn't really allow for any oem/carrier skinning though...
Of course, it is hard to fragment 0. http://www.google.com/search?q=windows+phone+7+release+date
Re: Android's "Extreme Fragmentation," Colorfully Visualized by TweetDeck's Team
#10"extreme fragmentation." Kind of like IBM compatibles? Or maybe Java-capable phones? Diversity of hardware is not something to be afraid of. Yes, it can cause a few difficulties, but it also provides a much wider market to sell to at the same time. Choice is good.
It seems silly to me to say blankly that "Choice is good." Obviously there are upper limits on how true that can be. If Motorola were designing and shipping and selling thirty different android phones right now, that choice would not be good. The phones would suffer and customers wouldn't know where to begin thinking about which phone they wanted.
The hassles for a developer associated with testing and making apps compatible on such a wide variety of devices are not trivial. It's a tradeoff, and Google is making no effort to control how that tradeoff breaks. Microsoft is taking a different approach. We'll see how that plays into things.