Android’s Acne Problem: Or Why You Should Stick To The Google Phone

HTC’s Evo might be the last phone running custom software on top of Android that you should even consider buying. Because the whole trend of skinning Android has become a horrible, dividing mess.

The problem and Android phone running a phone manufacturer’s homebrew software, like HTC’s Sense or Sony’s TimeScape, is well known: You’re going to wait a lot longer to get the freshest version of Android. That wait wasn’t a big deal in the past. But as of Android 2.2, you should think a bit more deeply about which Android path you’re going to walk down.

The Problem with Custom Skins

They’re awful. HTC’s Sense interface was widely regarded for making Android better when it showed up on the Hero a year ago. Well, Sense is the exception, not the rule. Some truly hideous atrocities have been committed in the name of Android, like Samsung’s Behold II. Not every skin is quite that offensive, but even what I’d consider the average, like Sony’s interface for the Xperia X10, is cloying and confusing; with the Evo, even Sense started to feel a bit tacky. The point should be to make Android sexier and easier to use. They don’t.

Android’s caught up. As of Android 2.2 Froyo, there is basically nothing any of the custom interfaces do that Android doesn’t. A year ago, Android lacked a great many things, from social networking powers to decent Exchange support to remotely accessible settings. HTC’s Sense filled in those massive gaps, once upon a time. But now Android juggles multiple calendars, smoothly integrates Facebook and Twitter into contacts (more seamlessly than any of the custom skins), lets you quickly access settings from the home screen, and even has built-in Wi-Fi hotspot powers. At this point, none of the custom software builds add killer features anymore.

They’re too slow. A corollary of the above point: Not so long ago Android was behind the best of the custom interfaces. But now Android is evolving so quickly, it not only caught up, it’s zooming past those meddling with its software. Frankly the custom interfaces need to innovate faster to make themselves worthwhile – as it is it seems pretty likely that the next stock version of Android build will be superior to anything phone makers can offer (in fact I would argue that 2.2 is already). But think about it: How likely is it that hardware companies are going to be able to keep up with Google, who finally seems to have hit its stride with Android?

The reasons to buy an Android phone with customised software have effectively dissolved. They don’t look better; they don’t work better; and they’ll hold you back from getting the latest and greatest updates from Google, possibly by many months. Most people don’t care or even know that their phone really is a computer, meaning it can actually get better via the magic of software updates. But if you’re reading this you probably care. Android 2.2 is a markedly more excellent experience than 2.1. The best stuff at this point seems like it’ll come from Google, so riding the bleeding edge of Android is the place to be, more now than ever.

Maybe that’ll change in another year, if Google slows down their release cycle as drastically as Android chief Andy Rubin says, to just once or twice a year. Which will be kind of a sad moment when it arrives – the thrill of Android, at least for geeks, is how fast it’s moving. But that’s when it’ll be safe to jump on the slow road. Until then, I’ll be sticking with the official, (probably) annually released Google phones.

Discuss

(11 Comments)
  • [–]

    Rod

    Wednesday, June 9, 2010 at 8:44 AM

    This is a problem that will continue to be an issue in the Android world. The manufacturers are looking for ways to differentiate their Android phones from other Android phones. It’s about competition after all.
    This has happened on a smaller scale in the Windows PC world as well. Companies often include all kinds of add-on shovelware to “add value” to their own offering.

  • [–]

    matt

    Wednesday, June 9, 2010 at 9:14 AM

    wtf is the problem here? Android, Phone manufactures: harden the **** up! WHY can’t all their customizations just be ‘apps’? or ‘pluggins’? that allows you to update to the latest os, while still keeping the same skin!!?!?!

    have a desktop app, a dialler app, ect ect (which is the way I thought it worked anyway) and then it should just be able to update! you don’t loose all your market place apps when you update? so why should this be any different.

    best case though, it will get to the point where its just like the bloatware that comes preloaded on any retail laptop you buy.

    • [–]

      boc

      Wednesday, June 9, 2010 at 3:31 PM

      That’s the direction it is heading, but unfortunately not the state that we’re currently in.

      Some of the customisation is easily removable because it’s done properly. Other customisations directly modify Android code (bad).

      A lot of app devs have done it the right way. Have a look at alternative apps for home screens, sms, contacts, etc. All separate and self-contained, sitting on top of and hooking into Android underneath.

  • [–]

    berko

    Wednesday, June 9, 2010 at 9:43 AM

    Windows Phone 7 is ahead of the game on this one. They have already announced that there will be no UI customisations allowed from the hardware manufacturers.

    Makes sense to me. Leave the hardware to the hardware guys and the software to the software guys.

    I guess Google aren’t in a position to be so dictatorial given the open source-ish nature of Android.

    • [–]

      Rod

      Wednesday, June 9, 2010 at 5:00 PM

      The problem that MS will have is convincing the handset makers that they all have to sell the same UI.
      It’s hard to stand out in the crowd if your phone looks and feels just like the next brand…

  • [–]

    Ben Phillipps

    Wednesday, June 9, 2010 at 12:23 PM

    I just wish Android would allow proxies for wireless networks – no point for an Enterprise user to have one right now.

  • [–]

    boc

    Wednesday, June 9, 2010 at 3:34 PM

    Gizmodo, please do an Android 2.2 stock vs HTC Sense UI comparison.

    I’d love to know what the difference between Android Facebook integration is like compared to HTC Facebook integration. As well as a whole slew of other features.

    Even now, I’m not sure what parts of my phone are Android and what parts are HTC Sense UI.

  • [–]

    Chris Lowery

    Wednesday, June 9, 2010 at 5:11 PM

    This is exactly why I didn’t end up getting an Android phone, and will stick with iPhones. I can’t trust telco’s and a hundred different hardware manufacturers not to fracture the market. Consistency is what I am after.

  • [–]

    Adin Knight

    Thursday, June 10, 2010 at 8:58 AM

    Sorry Matt, but this is a pretty lame article, essentially boiling down to ‘FROYO GOOD YAY WILL SOLVE EVERYTHING BECAUSE THERE MUST BE PROBLEMS SOMEONE TOLD ME ON THE INTERNET’. Have you actually used an Android device for a good while? Ever touch 1.1? 1.5?
    How about an actual article showing how the base UI has evolved and changed THEN compare it to both the OEM UIs AND those available on the Market?

  • [–]

    khg1978

    Wednesday, September 22, 2010 at 7:19 PM

    Just get a NOKIA.Period.

    Qt will combine symbian 3^ and4^ with MEEGO platform which will make fragmentation impossible.

    Coupled with NOKIA’s entire dominance in the smartphone and handphone world…this is the way to go.

  • [–]

    Chuck

    Tuesday, October 19, 2010 at 3:50 PM

    could you just hack you branded android phone to have the latest Android Google offers?

Join The Discussion