Android fragmentation is real

Android fragmentation is real

Summary: As much as Google's Dan Morrill, open source and compatibility program manager in the Android team, might want to argue that "fragmentation" of the Android platform is "bogeyman, a red herring, a story you tell to frighten junior developers," it's also very real.

SHARE:

As much as Google's Dan Morrill, open source and compatibility program manager in the Android team, might want to argue that "fragmentation" of the Android platform is "bogeyman, a red herring, a story you tell to frighten junior developers," it's also very real.

The problem with Android is two-fold. First, there have been six major releases of the platform in little more than a year and a half. No matter how you try to cut it, that's an awful lot of revisions for developers, OEMs and customers to deal with.

The second problem is that according to Google's own data, three of these revisions are still in wide use:

Android 2.1 is the dominant platform, but Android 1.5 and 1.6 makes up form more than half of those accessing the Android Marketplace, and this of itself means that there's already fragmentation of the platform.

But is this a problem? Well, I think that six major releases in the space of 19 months has been a problem. That pace of change speaks of Android's geeky origins. For Joe Average, this created an ultra-confusing marketplace where operating system versions changed every few months. It also meant that compatibility issues were inevitable.

But this rate of change is not sustainable. Android chief Andy Rubin outlines how the pace of change is slowing down:

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. I want developers to basically leverage the innovation. I don't want developers to have to predict the innovation.

While this will help in the long term, in the short term it's not going to make much of a difference. Fragmentation will always be an issue, but with careful management, new versions of the Android platform shouldn't make the earlier version immediately obsolete.

As Android becomes more mainstream, the platform will have to offer owners, developers and OEMs more certainty - something that geeks won't be happy with.

Topic: Software Development

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

53 comments
Log in or register to join the discussion
  • 1st gen phones were too underpowered

    The G1 particularly was very limited in ROM memory to store the OS. Rooted phones that are on 2.1 have to install an alternate system loader that increases the system partition at the expense of application partition (meaning that apps need to be stored on the SD card, which involves another tweak).

    Smart phone OEMs need to be forward thinking in that they need to anticipate that the phones will be in service at least 2 years and phones will need to be able to run the latest OS 2 years from now. And carriers need to be forward thinking enough to know they need to push the updates out.
    Michael Kelly
    • Google causes deliberate fragmentation

      Deliberate fragmentation is G's attempt to lock people in their cloud platform. Most of these vendors in that Open Alliance league like the openness but hate the tight coupling with Google's own cloud service so they take a copy of Android code and then strip the cloud service part out. In other words, the first thing they do is to Android source code is to de-Google it to escape G's tyranny.

      Google, despite all the rhetoric on supporting choice and freedom, certainly cannot stand actions like that against their agenda to lock people in their cloud platform so they release constant upgrades or simply tweak a few APIs here and there to make the vendors branching off from Google dictated version suffer.

      Delicate and evil.
      LBiege
      • RE: Android fragmentation is real

        @LBiege, you have a wild fantasy and really excel in conspiracy theory.
        vkelman@...
      • @vkelman

        I have access to these vendors so I know the real relationship b/t them and G, alright.
        LBiege
  • Not A Problem for Consumers

    While the releases may be a headache for developers and OEMs, most consumers don't know or care about which version of Android their handset is running. If it works, it works. Most consumers are compelled to purchase due to the hardware and general software features. Only the tech geeks care about incremental OS updates.
    Mwendo
    • RE: Android fragmentation is real

      @Mwendo

      I can see this as a valid point, to a certain degree.

      With many different versions of an OS out in the wild, with differing versions of the API, developers might decide to try to get the largest user base by developing to the lowest widely used version. This would be a negative thing for Google's push for newer Android versions, as well as users getting newer versions of the OS with features that not many apps might take advantage of.

      On the other side, when developers do take advantage of the new features what happens when a new Droid phone comes out on Verizons network running Android 2.3, and sports a fancy new software feature thats not bound to the hardware. Someone with a Moto Droid on 2.1 might have a friend with the Droid SuperTerrific on 2.3 with a fancy new feature that they can't get on their version.

      Now this might not happen often, but it does have the potential to, and thats when consumers might notice.
      tk_77
      • RE: Android fragmentation is real

        @tk_77 Now this might not happen often, but it does have the potential to, and thats when consu<a href="http://vb.maas1.com">m</a>ers might notice.
        maascom
  • Then Linux is fragged too. This is 'much ado about nothing'.

    nt
    Dietrich T. Schmitz, ~ Your Linux Advocate
    • Illogical comparison

      I have a friend who has an HTC Dream and he is on Android 1.5. Many of the Android 2.1 applications will not run on it and he's not thrilled about that. The Linux Kernel doesn't have this kind of fragmentation. The more this topic is discussed the more likely Google will attempt to address it and solve the problem permanently.
      DonRupertBitByte
      • Hello!

        @DonRupertBitByte

        Most Windows 98 stuff won't run on Windows Vista or Windows 7 so what's your point? This happens with major releases and new APIs being added!
        slickjim
      • @Peter Lights are on, but nobody is home...

        @Peter Perry On Windows, your talking unsupported backwards compatibility after nearly a decade. On Android you're talking about 8 months! There's a big difference there-- and if you can't see that, you really belong in the Linux camp.
        ericesque
    • RE: Android fragmentation is real

      @Dietrich T. Schmitz, Your Linux Advocate : Linux is fragged (said as someone who does a great deal of Linux development, for example, Time Drive: http://blog.oak-tree.us/index.php/science-and-technology/time-drive).

      The rate at which new software is released is extremely demanding and the only real way to keep on top of it is to pick one distribution's release schedule and try to follow it religiously. For Time Drive, I try and follow Ubuntu.

      And, things become fragmented. Whenever I want to release a new version of Time Drive that takes advantage of new platform features (such as notifications, to cite a trivial example), I have to think long and hard about backwards compatibility/fragmentation. Will it still work on older versions (such as the previous LTS, that is still supported and in wide use)? Does it require people to upgrade other packages? Will it be stable?

      That's a lot of QA for a guy who develops a program in his spare time; and is a really big problem.
      Rob Oakes
      • RE: Android fragmentation is real

        @Rob Oakes,
        I'm sure that a necessity to "think long an hard" about backward compatibility and a way to implement new features makes your programs better, modular and loosens coupling between its subsystems.
        There is no other way of developing for fast-evolving systems.
        vkelman@...
      • RE: Android fragmentation is real

        @vkelman: I certainly agree, but it also requires a significant investment in time. As does supporting multiple operating systems. And please consider that such support (which I don't really enjoy) cuts away from other activities that I do enjoy. (But being inaccessible makes me a dick.)

        Which brings me back to my main point: fragmentation is a problem for Linux and it's a problem for Android. It makes things more difficult than they need to be, and whenever a system is more complex than necessary, it results in problems with its adoption.

        One of the major reasons that Linux isn't more widely adopted is due to poor professional application support. And there are few professional applications because of too many flavors of Linux.

        Android risks going the same direction.
        Rob Oakes
  • Fragmentation limits a platform

    A platfrom becomes limited by too many variations. Why does Apple make everything uniform? For the customer experience.

    Why did MS have such an unroar with the "Ribbon" in Office? Because people like predictability and fragmentation leads to different groups getting a different experience.

    Linux... too many different experiences.

    Android: So far the argument has been different variations for different handsets. But at some point they will become incompatible enough that either developers get tired making their apps run everywhere, or the customers will get fed up than Version XXXX of the OS doesn't work with a particular app.
    croberts
    • Not true

      @croberts Developers will pick a platform they'll support and be very specific about which version of the OS they will support... Then the real issue will fall on the vendors who are too lazy to upgrade their handsets with newer versions of the OS.
      slickjim
    • RE: Android fragmentation is real

      @croberts,
      Apple innovate at a slower rate.
      Ribbon is just ugly and very inconvenient, very hard to find what you need. In an apartment building I live in, floor numbers in elevators are laid out into several rows. A result? Everyone has trouble trying to pick a floor. That's what MS did to a regular top menu.
      Finally, Android "fragmentation" is going to be less, not more. System becomes to mature, it's getting more modular, decoupled, easier to upgrade.
      vkelman@...
    • RE: Android fragmentation is real

      @croberts Here we go again with Apple. This is not an Apple article, so just STFU?
      MSFTWorshipper
  • RE: Android fragmentation is real

    There is an even bigger problem for the debs, particularly for low level apps. Without having a set screen resolution and OEMs dictating specs, it's very difficult to put out apps for the platform. WinMo suffered from that problem for a while, and Android surely will as well. It is difficult without a set hardware spec. That's why the Windows Phone route is actually a reasonable alternative. Or it's the Apple way of tight hardware / software control.
    ibarskiy@...
    • RE: Android fragmentation is real

      @ibarskiy@... This is why they should be moving toward resolution independence, which most desktop toolkits now support (and, correct me if I'm wrong, so does WebOS). For most of the development I do, it's been a very long time since I've worried about absolute dimensions.
      Rob Oakes