Google: Android fragmentation 'is a boogeyman, a red herring'
By Chris Ziegler 
posted June 1st 2010 5:17PM
posted June 1st 2010 5:17PM
Sure, as Android goes, the term "fragmentation" has meant moderately different things in different contexts over the past couple years -- fair enough. But the fact remains that releasing six major revisions of any platform within the span of 19 months (four of which are in heavy user circulation) is unprecedented and potentially unsettling to manufacturers and consumers alike. Your average Joe isn't going to understand why, for example, his HTC Hero that he bought a few months back can't use the Buzz widget or some of the cooler features in Google Maps, and Google hasn't done a very good job of explaining or justifying it, other than by blocking incompatible apps and updates from being visible in the Market."Because it means everything, it actually means nothing, so the term is useless. Stories on 'fragmentation' are dramatic and they drive traffic to pundits' blogs, but they have little to do with reality. 'Fragmentation' is a bogeyman, a red herring, a story you tell to frighten junior developers. Yawn."
Morrill's point is that "fragmentation" -- however you define it -- isn't to be feared. He writes that developers control their own destiny thanks to a combination of tools that allow apps to be targeted to specific Android versions, tight restrictions by Google over use of the "Android" name only on hardware that meets stringent spec requirements (which manufacturers are "motivated" to adhere to), and an assurance that every app is forward compatible with future builds.
Ultimately, we'd argue that Morrill is simply changing the subject here, but we think the conversation will become moot over time anyway. Speaking with the San Jose Mercury News, Android chief Andy Rubin talks about slowing things down -- something we'd said would happen not long ago:
Rubin goes on to say what we've all been seeing from the outside: Android is maturing from a very feature-incomplete platform into a fully-featured one, and as such, Google will start to have the luxury of taking on a less maniacal release schedule. It's not often we're against fast, frequent product releases -- but we think we could all use a little breather from AOAD (Android Obsolescence Anxiety Disorder) right now."Our product cycle is now, basically twice a year, and it will probably end up being once a year when things start settling down, because a platform that's moving -- it's hard for developers to keep up."
fragmentation does not exist
@N900androidOS So why is it happening to Andriod right now?
@N900androidOS
Google playing damage control.
If things weren't fragmented, they would have pushed for more unified updates across all devices and across ALL carriers. Leaving it up to the handset distributors to update the software, and playing a game of favoritism towards certain hardware specs -- while completely ignoring others -- sure sounds like a heavy case of fragmentation to me.
Can you believe there are still people out there running versions of Android > 1.6? I certainly find that a bit ridiculous.
@MoonWalkerCTE
....What? It's not that much. Handsets are simply going out of date faster than usual. It's like the computer gigahertz race x1000.
And the phones that are prevented from being updated due to manufacturer issues can still be updated, albeit without the nice skins.
Very little fragmentation. Just a super speed of development, which will eventually level off.
@r34p3r Android 1.6 came out in September of '09, so it's been a bit less than 10 months. On the other hand, every single person with an iPhone is running at best an 11 month year old version of the software.
@r34p3r
Sorry, I meant < 1.6
@MoonWalkerCTE
the only reason u may THINK android is fragmented is because manufacturers dont take the time to update them after they launch. all phones are capable of running the latest version of android, even the g1/dream.
@r34p3r Ah, 1.5, that makes a bit more sense. Of course, those phones with 1.5 are closer to feature phones, and the consumers who buy them likely don't know of or expect software updates.
@MarcusMaximus
Agreed. If someone doesn't realize that they're playing with 1.5, they most likely will love their new featurephone.
However, if they say, "Ehhh, this is pretty basic" and then go on to another phone with, say 2.1, and say "Perfect," it really won't matter, will it?
@MarcusMaximus
Yeah, my mistake on the typo. It's situations like that where I really wish Engadget would implement an "edit" feature for its comment system, to avoid situations of possible confusion.
Maybe in the next iteration? A guy can dream, can't he?
Fragmentation on Adroid exists, if you deny it you have a bigger problem.
@r34p3r
An edit button? Thou asketh too much!!! Away with thee! lol
Maybe a website that doesn't crash mobile safari and make my netbook's fans start up just to load?
@MarcusMaximus Not really. iPhone OS 3.1.3 was released this february. That's not 11 months.
@Mike10010100
lol, yeah the code isn't very stable in Opera mobile either. A few times I've tried to load the comments, only to have the browser lock up and then crash.
On a more related note, just because I have this opinion on Google's software business mentality does not mean that I am not still stoked to pick up my Evo 4G in a few weeks. It softens the fragmentation aspect a bit to know that they'll at least support the hardware with a 2.2 update some time down the road. I just hope the hardware remains relevant over the next couple years, so we don't run into another G1 debacle.
@Dusse and it was entirely comprised of bug fixes. We're talking actual feature releases here, not simple bug fixes. Otherwise the cycle for even those phones that take the longest in Android are much faster than my stated value.
@N900androidOS "Fragmentation does not exist"
Yes, just like Sith can't be rearranged to spell Shit
...Oh Wait
@r34p3r
Except it's really not the hardware's fault. Most of the hardware can support 2.2. In fact, some of the older hardware that couldn't support 2.1 can support 2.2 due to the speed increases and less memory usage.
It's really the manufacturer's fault. More manufacturers should switch their phones to Google Experience phones. That should be the standard that most manufacturers strive towards in order to keep the updates coming quickly and easily.
@Mike10010100
Oh yeah, I forgot about how much more efficient Froyo is in regards to memory and system resource usage. All the more reason that these hardware manufacturers need to get their shit together and actually take Android seriously as a mobile platform -- not just a selling point for their half-baked handset designs.
"Look at us! We have Android! You buy NAO!*"
*except we'll take our sweet ass time getting you the proper software support you as a paying customer should be entitled to.
So in reality, it's only partially Google's fault. The two entities (Google and each respective manufacturer / carrier) need to work together better to push these updates out the door at a more efficient pace, IMO.
@N900androidOS Fragmentation would not be an issue if it wasn't for lazy manufacturers like Samsung, LG, and Motorola, still putting out 1.5 devices out with no promise of future updates..
@Lord Vader You should take care of the trolls aka Adroid fragmentation apologists
@r34p3r
Less Google's fault, more manufacturer's. But I agree with every other point.
My logic? Google's done an awesome job taking a hands off approach to the implementation of Android. They deserve a medal for furthering open source and causing greater competition in the marketplace.
Google cares that people have a good Android experience. Manufacturers just want to get their product out the door and milk it for all the money it's worth. Some, like HTC, eventually roll out the updates.....but it's a little bit slower. Not that bad, but slower.
@N900androidOS
If you buy a computer... and 6 months later a new version of Windows comes out... you can upgrade to the newer version of Windows.
The problem is... someone could buy an Android phone now... and 6 months later a new version of the Android OS comes out... and it won't work on that device.
That's the fear of Android's fragmentation.
@Drago
Here's the problem: what do you actually mean by "fragmentation"? That is the main issue. And what you mean determines how much it affects consumers/developers and if it actually matters that much in the grand scheme of things.
You can argue that fragmentation exists in every single platform out there today (even the iPhone OS). But what is the actual impact?
Today it is mostly thrown out there as FUD word against Android.
@Drago. I will do what I must (Prepares Force Choke hand)
@Mike10010100
Glad we see eye-to-eye on this and can maintain a civilized discussion on the matter. Up-rank to you, good sir :)
@Drago
We get it, Drago. You think there's tons of fragmentation and that it's a huge issue. Please stop repeating yourself so that we can actually have a real conversation without resorting to calling people trolls.
Duh fragmentation exists. As long as you have any product with multiple versions of software that don't require the user to update to continue functioning there's going to be fragmentation. There are still people using Windows XP for crying out loud!
@Drago
We get it, Drago. You think there's tons of fragmentation and that it's a huge issue. Please stop repeating yourself so that we can actually have a real conversation without resorting to calling people trolls.
Duh fragmentation exists. As long as you have any product with multiple versions of software that don't require the user to update to continue functioning there's going to be fragmentation. There are still people using Windows XP for crying out loud!
@r34p3r
And to you, good sir. We don't have to call each other trolls. We recognize that fragmentation exists and say that it really isn't that big of a deal due to XDA and other hacker forums. It's the manufacturer's fault.
However, that in no way means that I'm for more control by Google. They don't need to be another Apple. They simply need to stay the course, and try to get manufacturers on the boat of "Google Experience Phones". Users should look for this branding like they do the "Vista Capable" sticker on computers and such. The manufacturers that don't should be branded as outsiders.
@r34p3r I get the point of this article as I wouldn't even want to get the EVO without 2.2 and sense. The OS 2.1 isn't very good for my business needs and sense makes far more practical as the OS is rather clumsy without it.
I envy you the new hardware, I think the EVO is everything I've been wanting on Sprint for ages - large screen, slim design, fast processor, flash for the camera...
I think Unverified, account5, marcusmaximus & Mike10010100 are the same troll. Here's a -1 for you all
@jakey Two words: Asphalt 5.
Google it.
This popular Android game runs smoothly on the Droid yet it lags on the Nexus One.
Fragmentation ∎
Denying that Android fragmentation exists and refusing to acknowledge its impact on the consumer smartphone market is a bogeyman, a red herring. Yawn.
@Mike10010100 FWIW, I've noticed that if you hit the red X to stop MobileSafari from loading Engadget after it's been spinning for 15-20 seconds the entire page loads and it won't crash the browser. You have to do this when opening articles too, basically any time an Engadget page is loading.
@MarcusMaximus Android 1.6 came out last year at Google I.O
2.0 came out in the September time frame
@r34p3r
the problem as i see it is that you have two options - having control over your OS (like apple) and thus creating a very smooth and homogeneous platform available to only one company. or to have a dynamic and open platform open to everyone thus creating the various versions (fragmentation).
my opinion? i'll take the open platform any day. if it means that my cheaper hardware ends up being behind, so be it. innovation is my co-pilot.
@HotFuzz got any tangiblee evidence of said impact?
@Mike10010100 Can you point me to where I can dowload fray so I can install it on a computer? It's open source so I am assuming I should be able to dowload the source code...
@Mike10010100
"Agreed. If someone doesn't realize that they're playing with 1.5, they most likely will love their new featurephone.
However, if they say, "Ehhh, this is pretty basic" and then go on to another phone with, say 2.1, and say "Perfect," it really won't matter, will it?"
It will matter to the manufacturer of the 1.5 phone - a LOT
@Mike10010100 Bing...fu##in...go
"Google cares that people have a good Android experience. Manufacturers just want to get their product out the door and milk it for all the money it's worth."
Once the release cycles settle down, i think we'll see more reasonably timed updates and less "fragmentation" / "legacy" issues. We all expect a little too much for our cash sometimes.... You can't have killer hardware, regular updates and a low price (outright purchase based... not the price on a plan you guys have in the states).
@smitty5569 http://en.wikipedia.org/wiki/Android_(operating_system). 1.6 came out in september, 2.0 came out in October.
@Drago Troll? Name one comment there that was in any way trolling. Every single comment of mine cited a known fact except the one acknowledging a typo. But then, from your comments, I'd guess that anyone who disagrees with you = troll.
@Michael Scrip
Perfectly Worded...Upranked..
I got a dell laptop from 2006 that runs Windows 7 just fine.
Why are these cell phone manufacturers so friggen LAZY when it comes to product support and updates? Samsung is the WORST of them all, especially considering the whole Galaxy fiasco -- can't believe they actually promised an OTA update in a video nonetheless, and then pulled the video and changed their minds. That to me is one of the scummiest things a company can do...
But what people don't realize is -- this isn't Google's fault...what are they supposed to do, force Samsung \ LG \ etc to provide updates?
Not going to happen.
@mogua
If you use that example you are describing hardware fragmentation. The iPhone which Asphalt 5 was originally made for uses the same PowerVR graphics chip that the Moto Droid used later. Gameloft is just to damn lazy to optimize the code for Android and they are using their own store instead of the Android Market to screw Android owners over.
@MarcusMaximus,
Still, advanced custom ROM (like Cyanogen) could be installed even on earliest Android devices.
@MarcusMaximus "Android 1.6 came out in September of '09, so it's been a bit less than 10 months. On the other hand, every single person with an iPhone is running at best an 11 month year old version of the software."
Yes, but they are all running the *same* 11 month old version. You know, the one targeted by all developers. Many android developers target 1.6 or 2.0 (or even 2.1). Four major version behind in only a few months sounds pretty fragmented to me.
@ai4281 Motorola really is actually one of the few that are. They've already shown their plans on when their phones will get 2.1, which is all of them. But I just hope they stick to that, finally starting to respect Motorola again. =/
@Mike10010100
It sure doesn't feel lie Google wants people to have a happy Android experience. What it feels like is that Google wanted to play catchup and pass Apple as fast as possible, so they fast tracked the OS upgrades from their side, and didn't really care what the handset manufacturers did.
As long as the latest and greatest handset came with the latest (or almost latest) version of Android when it launched, that was a good deal for Google. However, when you have handsets launching with Android 1.6 at the same time that 2.2 is out, that's not anything close to a good Android experience.
I look forward to them finally slowing down the OS cycle and concentrating on making sure their partners are covered.
@Mike10010100 Safari on my iPod crashes all the damn time. I hate it!
@ai4281 I thought Samsung promised future updates
@r34p3r
Well nice try from Google but no cigar. I really expected Google to put forth some solid solutions on how to deal with this fragmentation instead of trying to pull wool over consumers' eyes. They think they can simply "persuade" hardware companies to follow their diktat. Well good luck! - just look at Nokia which was a single hardware manufacturer with gazillions of product lines and even there fragmentation occurred. Now consider what will happen when those gazillions of product lines are in control of gazillions of different manufacturers. Google really needs to learn from the harsh lessons Nokia suffered instead of pretending that the problem does not exist!