Google Finally Fights Back Against Android Fragmentation

Openness has always been Android’s beauty and its curse. Google’s mobile operating system is available to any manufacturer that wants a slice, meaning you see it everywhere! It’s also historically been a place for hardware specialists and carriers to flex their software muscles, leading to custom alterations – skins – that often leave an elegant smartphone solution ugly, unusable, or both.

Finally, that’s about to change. Thank goodness.

According to Bloomberg, Google has spent the last several months tightening the reigns on its Android partners. They’re having licensees sign “non-fragmentation clauses” that give Mountain View final say over the platform tweaks that can cripple a perfectly good phone. The OEMs are up in arms, obviously, but they shouldn’t be. Because what Google’s doing is making sure consumers know exactly what they’re getting. They’re making “Android” mean something again.

The biggest problem often isn’t the skins themselves. Many people find HTC Sense to be a welcome improvement over stock Android, while others – someone out there, I’m sure – may dig Motorola’s social-savvy Motoblur. But the more aggressively companies manipulate Android, the longer their customers have to wait for firmware updates that bring crucial services. Some handsets end up never being updated at all. No, really… it’s bad out there.

Even worse, handset manufacturers continuously release products with outdated versions of Android, either because of internal foot-dragging or carrier demands. Anyone who bought the Dell Aero last August may have technically been buying an Android phone, but at the time it was a three-generations old version of Android.

So if Google wants to keep its partners in line to guarantee a consistent user experience, so be it. It’s their platform, and their right to institute some much-needed quality control. It’s the firmware version of the conundrum Microsoft faced with Windows Mobile, when an absence of hardware requirements resulted in an ecosystem so messy they had to scrap the whole thing and start over with WP7.

Yes, there are some concerns that Google could overplay its hand, as with reports that they’re pressuring Verizon to drop Bing from some phones. But the core issue – that consumers deserve an Android label that means something – is one that Google’s long overdue in addressing. Better late than never. [Bloomberg]

Discuss

(12 Comments)
  • [–]

    Ben

    Friday, April 1, 2011 at 8:22 AM

    You’re kidding aren’t you Brian?! I hope you’ve never written an article praising the virtues of Android’s “openess”.. Which was always a load of convenient horse *uhum* anyway. Doesn’t this sound an awful lot like what another company does with their operating system? Can’t wait to see the Android supporters (note I deliberately didn’t use the term fanboy) twist on this.

    • [–]

      Bryce Fraser

      Friday, April 1, 2011 at 8:55 AM

      I think it’s a great idea though. It’s not like Google is making each manufacturer make every phone the same. They just want (and need) tighter reigns on it. Look what happened to Windows Mobile, how many people did you see carrying a windows mobile phone around? I for one, will be happy to finally be able to buy an android phone that isn’t loaded with the carrier’s crap. My htc desire from Telstra has about 20 apps that do not work, are cluttering my app page and that i cannot install.

      Good on you Google.

    • [–]

      Stormblazer

      Friday, April 1, 2011 at 11:48 AM

      Good and bad – I think OEMs should be allowed to customize as much as they want, as long as it’s *optional*. If you just force one thing on everyone, then it would be just like Apple – and a lot of us avoid Apple products precisely because we hate that.

  • [–]

    Marcus

    Friday, April 1, 2011 at 9:14 AM

    “It’s their platform, and their right to institute some much-needed quality control.” Umm, no. It is open source, (subject to open source license conditions) and as such legally bound to the certain conditions: “The freedom to study how the program works, and change it to make it do what you wish. Access to the source code is a precondition for this.”

    The release of honeybomb to ‘approved partners’ whilts not publically releasing the source code is a violation of the license that linux and all of it’s child projects that have been built upon and subject to since it’s inception.

    Google do have the power to restrict access to services such as the market. Thay can even restrict access to google search (extremely unlikely). However, they have no rights to impose a removal of Bing services. Denial of access to the marketplace is probably enough leverage to get what they want tho.

    • [–]

      Matthew P

      Friday, April 1, 2011 at 11:50 AM

      Your wrong, you are allowed to sell your own Linux versions that you have changed.

      • [–]

        Chris

        Saturday, April 2, 2011 at 4:23 AM

        Correct. As long as you disclose the source before the modifications, your own coding is still your IP.

  • [–]

    DF

    Friday, April 1, 2011 at 10:37 AM

    I think it is a step in the right direction and it would be interesting to see what these clauses are. But I reckon Google instead forcing a company to build phones according to their specs, they should come up with a certification system. The OS should be open to use by any manufacturer, but if the phone is certified by Google, then consumer would know they will get update and upgrades on a timely manner.

  • [–]

    Abraham

    Friday, April 1, 2011 at 11:46 AM

    Totally agree. My Motorola backflip is still stuck on Android 1.5.My phone came out After Android 2.1 was released and still Motorola loads 1.5!! Motorola promised Android 2.1 but never delivered. Anyway im using custom rom 2.2.

  • [–]

    Rossco

    Friday, April 1, 2011 at 11:46 AM

    I think Google will need to open the source back up for legal reasons and more importantly to keep the community involved and engaged in the project. I hope that this is just a hiccup while they tighten the rules for use of the OS and the Android trademark. I think that Google certification of devices and roms going onto devices and enforcing the Android trademark and brand (like Red Hat(tm) have with RHEL) is the right way to go IMO. If the Android brand is valuable enough, the big manufacturers will follow the rules to use the trademark and it will end up being a better result for consumers. Hopefully in the future, manufacturers will have to package their skins as launcher replacements and all launchers and apps from the telcos and manufacturers must be uninstallable.

  • [–]

    David Anderton

    Friday, April 1, 2011 at 1:59 PM

    Rossco you have hit the nail on the head!

Join The Discussion