Commentary

Ed Hansberry
 

Google Has Lost Control Of Android Fragmentation

Fragmentation allows variety among device makers, but can cause frustration for developers and lower satisfaction among end users.

If there's one complaint you hear about Google's Android platform, it is about fragmentation. It happens at the device level, the OS level, with the UI, and even with specific apps and services some carriers or manufacturers use. There are plusses and minuses to all of these, and it looks like Google has lost control, ceding the problems to the licensees.

Microsoft went through this with Windows Mobile starting in about 2005, and it created serious problems as the platform aged. Palm also had fragmentation in the later years of PalmOS, and it caused enough issues that some developers quit developing for the platform. The economics of developing apps has changed radically in the last two years, though, so fragmentation is no longer something that can be avoided. Instead, it must be dealt with.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

As Charlie Kindel's article explains, fragmentation causes problems--but it won't be the death knell for Android.

Let's start with the UI. Users moving from one phone to another may have a very different experience because each manufacturer has customized the interface. Consumers are generally used to a consistent experience across different machines if the platform is the same. Windows computers are built by many manufactures, for example, but the desktop is the same overall. If you have an Android phone and move to another one, it can be a jarring experience to see that new screen for the first time and figure out how to do things with the new phone that were second nature with the old one.

Google is at least trying to alleviate some of the pain here. Manufacturers can put their custom UI on a device, but they are now required to also support the stock Holo theme so the user can revert to that if desired.

Another big issue is that carriers and manufacturers too often fail to provide updates for phones, even though the vast majority of phones are capable of running one, two, or more OS revisions beyond the one it shipped with. Today there are eleven major versions of Android in use on phones and tablets, and probably dozens of sub-versions. Fully 30% run Froyo, which is nearly two years old.

You cannot argue with the success Android has had in the market. But you have to wonder if Android's satisfaction rate, which is around 50%, would be higher if its fragmentation was more tightly controlled.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links