Hey, Google, take control of Android already, will ya?

android-lineup-of-phones

Google’s open approach to Android has certainly helped build the platform’s user base: Android powers more than half of the world’s smartphones. Whether you love Android or hate it, it’s difficult to argue that this level of adoption is anything less than a success. Android debuted as a clunky operating system with few apps in Oct. 2008, but since then it has improved and grown. But Google’s openness — allowing anyone to use the platform — might not be the best strategy for keeping its lead.

The latest example of Android’s mess: blame

Here’s a case in point: a recent public spat between AT&T and Google on software upgrades, one of the most annoying things about an open platform that essentially anyone can control. AT&T CEO Randall Stephenson first wagged a finger at Google, answering a question during an interview last week with this, as reported by 9to5Google:

Google determines what platform gets the newest releases and when. A lot of times, that’s a negotiated arrangement and that’s something we work at hard. We know that’s important to our customers. That’s kind of an ambiguous answer because I can’t give you a direct answer in this setting.

As a daily Android user since Jan. 2010, I’m flummoxed by Stephenson’s statement. Is he implying Google’s Android system isn’t really as open for use by anyone as they see fit? If so, that’s news to me and likely many others. Apparently, it’s news to Google too, as it released this statement:

Mr. Stephenson’s carefully worded quote caught our attention and frankly we don’t understand what he is referring to. Google does not have any agreements in place that require a negotiation before a handset launches. Google has always made the latest release of Android available as open source at source.android.com as soon as the first device based on it has launched. This way, we know the software runs error-free on hardware that has been accepted and approved by manufacturers, operators and regulatory agencies such as the FCC. We then release it to the world.

History appears to back up the official Google statement, as hardware manufacturers and carriers have held up prior updates — or simply chosen not to offer them at all — over the past three years. In fact, Stephenson’s statement makes even less sense when you realize that handset makers are the ones that first create Android builds for phones. Yes, carriers could have some say in the part of the process, but it’s likely very little. And the lone exceptions for Android updates — those that are pushed directly by Google — are the Nexus handsets, which AT&T has never even sold. (Note: AT&T did sell the Nexus S; thanks to Karen for catching that in the comments)

What’s the real problem here?

Regardless of who’s right and who’s wrong on this particular issue, it illustrates a bigger problem for Android. Instead of reducing version fragmentation, getting updates out faster, and having consumers expect a consistent experience across all phones, the situation is really no better now than it ever was. I had hopes Android 4.0 would help, but the reality is that 6 months after Android 4.0 launched, few phones are running the new software: only 4.9 percent today, based on Google’s own data. Compare that with the 10 months it took for 75 percent of Android phones to run Android 2.0 or 2.1.

Bear in mind that while I use Android every day, I also use iOS on a daily basis. I occasionally use Windows Phone as well. My point here isn’t to suggest that Android is crap and people shouldn’t use it. But the best Android experience, at least in my opinion, is only offered by Google’s own Nexus devices. Sure, there are some outstanding Android phones with faster processors, better cameras and customized software improvements that make them great handsets.

But at the end of the day, if you’re not using a Nexus, you’re at the mercy of your handset maker or your carrier for updates. And those won’t likely be timely; Motorola explains why in this blog post. Plus, your carrier can always determine which features you can or can’t use on your handset; Google Wallet works great on my Galaxy Nexus, but the Verizon LTE version doesn’t support the service. The problem Android faces today is the one it has always faced but has never been able to tame: a lack of control.

Google, you’ve got Motorola, now use it

It would be an audacious move, but for Google to rein in Android, it has to take back control of the platform. I’m not even sure it could, since it has open-sourced Android all of this time, but if it is possible, now’s the time. I hit on this last month in a GigaOM Pro report (subscription required), saying this:

For Google to truly address the problems Android faces, it will have to “own” Android. By licensing the platform as it currently does, Google has limited control over what hardware makers do with Android. That could be part of the reason Google decided to acquire Motorola Mobility: It could offer Android devices that have unique functions or features, even as it uses Motorola’s patents to protect Android at large. Patents or not, Motorola could be the key to Google’s taking Android back.

Using Motorola to begin taking control back of Android is fairly obvious, but the reasons to do so aren’t. Google has used its open approach to let Android proliferate like a virus, and that has led to hundreds of devices on networks all around the world. Think of these as little Google terminals where the company can gather information; Google keeps its finger on the pulse of mobile through these Android devices and sells mobile advertising based on that data. And for now, Google is recording the heartbeat of more than half of all smartphone owners. But that may not continue forever.

Why now is the right time for this move

Opinions will vary on this, but I think Android is at the top of its game right now — or at least it was recently; the exact timing isn’t important. What is important is to “go out on top” and take control now before Android loses any momentum. Right now carriers and consumers want or need Android to exist. Why? Because not everyone wants an iPhone, regardless of the benefits iOS may bring — namely consistency, control and stability, three words I wouldn’t equate with most Android phones.

If Google were to take control of Android now, it would be difficult for carriers and handset makers to rebel. Apple has no LTE handset yet, so operators are pushing Android devices over the iPhone in some cases. Hardware makers have few other choices to turn to as well. They could opt to embrace Microsoft’s Windows Phone, but the consumer demand isn’t there yet. LG recently suggested it wouldn’t be building any Windows Phones until consumer demand warranted it. Let’s face it: Google has carriers and hardware makers in a position where it could dictate Android’s future use, at least for a little while.

Such a move would surely give hardware makers pause to work with Google in the future. But for the mobile market, I see little viable option. Would Samsung, HTC, LG and others simply stop supporting Android? I don’t see how they could, given the slow uptake of Microsoft Windows Phone. Perhaps one could buy Research In Motion or license BlackBerry, but even that’s a risky proposition at best. Tizen, another mobile platform formed from the old MeeGo project, is another option, but it has the same open-source approach as Android, so little would be gained by using it.

Open worked up to this point. Can it continue to work?

Without a doubt, Google’s open approach has helped it build the Android user base. It gave consumers and software developers a viable choice as compared to Apple’s walled garden, and it provided dozens of hardware makers a chance to stay in the smartphone game. But as Android’s “Wild West show” continues — or even the perception of it — consumers are likely to turn their back on Android over time. For that reason, Google should consider a change and control its mobile destiny directly. And the longer it waits, the less likely it is that such a move will pay off.

loading

Comments have been disabled for this post