Can Google Fix Android's Fragmentation Problem?
One of the most common knocks on Google 's Android platform is its "fragmented" nature.
The Android OS has to support hundreds of hardware models from dozens of manufacturers, most of whom like to put their personal stamp on their handsets and tablets by introducing their own unique wrinkles. And then, the network operators join the customer experience party: The same Samsung phone will look and feel very different depending on where you bought it. And not for technical reasons, either: The same hardware will work just fine with the AT&T and T-Mobile US networks, but each carrier wants to make sure you know who you're sending that monthly check to.
Compare and contrast this to Apple , where the iPhone maker largely sets its rules in stone, and even the major carriers must comply if they want to sell Cupertino's refined hardware. Instead of hundreds of models and plenty of handset makers, Apple only supports its own in-house designs, and just a couple of models, at that. The result is a highly predictable experience that contrasts sharply with the variegated Android landscape.
Well, Google has started doing something about this. The company hasn't presented a brand new Android version in 2013, as it often does in the spring and fall of every year. Instead, some of the details that set the latest version apart from older variants have been broken out and can be installed on older handsets. You don't have to wait for Ma Bell or T-Mob to send out wholesale Android upgrades to your aging handset, if all you wanted was that nifty Jelly Bean keyboard, or the Google Now instant search tool.
This move won't erase the handset builder's and carrier's custom apps from your screen, but it does make the Android platform more consistent across major versions. It's certainly a step in the right direction if you care about consistency on a variety of hardware.
But why stop there? The rumor mill suggests that this fall's major Android release will require less memory and system resources than the last few generations. According to VR Zone, this October will see Android 5.0, aka Key Lime Pie, stepping up with low-key hardware requirements that would fit handsets made in 2010. Google is optimizing the living daylights out of its software, giving its many partners the option to update some positively ancient hardware to the latest and greatest software.
If the Key Lime Pie requirements turn out to be as low as VRE Zone suggests,you can expect users with older handsets to demand support for a modern software platform. It's getting harder and harder to blame Google for unpredictable Android upgrades, shifting the potential blame squarely on the shoulders of its hardware and service partners.
As one of the most dominant and innovative Internet companies ever, Google has made a habit of driving strong returns for its shareholders. However, like many other web companies, it's also struggling to adapt to an increasingly mobile world. Despite gaining an enviable lead with its Android operating system, the market isn't sold. That's why it's more important than ever to understand each piece of Google's sprawling empire. In The Motley Fool's new premium research report on Google, we break down the risks and potential rewards for Google investors. Simply click here now to unlock your copy of this invaluable resource.
The article Can Google Fix Android's Fragmentation Problem? originally appeared on Fool.com.Fool contributor Anders Bylund owns shares of Google, but he holds no other position in any company mentioned. Check out Anders' bio and holdings or follow him on Twitter and Google+. The Motley Fool recommends Apple and Google. The Motley Fool owns shares of Apple and Google. Try any of our Foolish newsletter services free for 30 days. We Fools may not all hold the same opinions, but we all believe that considering a diverse range of insights makes us better investors. The Motley Fool has a disclosure policy.
Copyright © 1995 - 2013 The Motley Fool, LLC. All rights reserved. The Motley Fool has a disclosure policy.