Android Honeycomb 3.1: A mixed bag of meh

Android Honeycomb 3.1: A mixed bag of meh

Summary: I am enjoying the Galaxy Tab 10.1 as it is a really nice tablet, easily the nicest Android tablet I have used to date. The problem is that perception is in spite of Honeycomb 3.1, not a result of it.

SHARE:

I was first exposed to the tablet version of Android with the Motorola XOOM earlier this year, and concluded that earlier versions of Android worked better on tablets than Honeycomb. Honeycomb is the version of Android that Google has specifically produced for larger devices like tablets, but I found it to be less productive than earlier versions designed for smartphones.

With great anticipation I received the Samsung Galaxy Tab 10.1 to test, as it packs the latest version of Honeycomb, Android 3.1, that addresses some of the stability problems I had with version 3.0. After using Honeycomb 3.1 for a while, my overall reaction to it is a mixed bag of 'meh'.

Don't get me wrong, I am enjoying the Galaxy Tab 10.1 as it is a really nice tablet, easily the nicest Android tablet I have used to date. The problem is that perception is in spite of Honeycomb 3.1, not a result of it.

Inconsistent experience

The biggest problem I have with Honeycomb is due to the design choice that Google made to handle the larger displays. Putting system controls in all four corners of the display invokes feelings of inconsistency while using the tablet. Notifications pop up all the time in the lower right corner. The clock is in the lower right corner too, along with access to common Android functions and settings.

Access to the installed applications is in the upper right corner of the display, an area in Honeycomb that the user never goes to on the home screen except to run apps not sitting in plain sight. Running a Google search at any time is just a tap away, but requires hitting an icon sitting in the upper left corner.

Then there are the main Honeycomb controls, the soft buttons for going Back, accessing the home screen, and displaying the running apps. Those controls sit in the lower left corner of the screen.

The four corner design choice by Google means that every time I want to do something in Honeycomb, I must stop and think where to go for it. Upper left, right, bottom of the screen? The end result is I often tap a corner control only to realize it wasn't the one I wanted. A lot of tapping takes place to get around erroneous taps, and that is the mark of poor design in my book.

Earlier versions of Android aren't optimized to take advantage of larger displays, but at least all of the controls are tightly integrated and always where you expect them to be. After just a short time with tablets running the older Froyo or Gingerbread, it is possible to operate the system with little thought, just instinct. That is the mark of good design.

It doesn't help Honeycomb that app developers can contribute to the four corner mess. Lots of Honeycomb optimized apps, and there are quite a few, put the icon to access the app settings in the upper right. This isn't intuitive due to the Honeycomb use of this corner to access My Apps on the home screen as described. But with consistent use of the corner for app settings, it's just a matter of practice to get used to it. At least that would be the case if all apps put the settings here.

Other app developers have a scheme of granting access to app settings via a soft button in the lower left corner, next to the official Honeycomb soft buttons. You have to look carefully to see it as the settings icon appears to be a system control, not an app control. It looks a lot like the running tasks icon, too, which makes it even harder to spot at first. The end result is there is not a consistent user experience in apps for common functions. It's not Google's fault that developers are using different methods in apps, but I would maintain that it is Google's fault for allowing it to happen.

Giving leeway to developers is a good thing overall, but not with common functions used in virtually all apps. Those should be defined to work the same way in all apps, and accessible in the same way. Unfortunately it's not always instinctive to reach for a control in an app to do something, instead it requires a good look around the four corners of the screen to see where to tap next.

Stability

Honeycomb 3.1 is much more stable than 3.0, which would crash on my all the time during a session. That's not the case with 3.1, as Google has improved the stability a great deal. It's not all the way there, however, as I have experienced a few crashes over the past two days. At least I call them crashes, there are no error messages involved, apps just close by themselves and I get kicked out to the home screen. Getting back into the app is a simple matter of running it again, which invokes a new copy of the running app.

Hopefully Google will figure out what causes these crashes, as they usually happen with official Android apps. The browser is a common app that closes and goes away while browsing the web. I suspect it is a system memory issue and these apps are being shut down by Android because there is not enough memory to run them.

There is a good way in Honeycomb 3.1 to manage running apps and keep track of the memory situation, but only through the system settings. You can't easily get to it while in a running app, and since there's no warning before an app crashes it's a moot point. You just keep doing your thing until an app crashes and then move on.

I have only experienced one impromptu system reboot once with Honeycomb 3.1, a vast improvement over 3.0 which would reboot all the time. It is telling however, that even one system reboot is considered a vast improvement.

The Samsung Galaxy Tab 10.1 has proven to me that Honeycomb is almost there to be a fun OS to use. I am hoping that Google gives the tablet interface an overhaul with Ice Cream Sandwich to address my concerns. I don't think I am alone in my take on using Honeycomb, although everyone is different. I am sure there are fans of the Honeycomb interface. How about it? Do you like Honeycomb or wish it was different? Sound off in the TalkBack below.

Image credit: Flickr user Rick Harris

See related coverage:

Topics: Mobility, Android, Google, Hardware, Laptops, Tablets

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

Talkback

76 comments
Log in or register to join the discussion
  • RE: Android Honeycomb 3.1: A mixed bag of meh

    Wow! Really?! Ill give you the point for the few crashes here and there with Honeycomb, but the criticism of the layout is ridiculous. You say you've been using mobile technology for a long time, but if that were true, this layout wouldn't be causing you such a headache. Its simple and intuitive. In easy reach of your thumbs. Would you prefer everything at the bottom? No, you wouldn't. Know why? Because you have no idea where these software buttons should go. No where in your article did you make a suggestion. If its that difficult for you to use your 10.1, give it to me so I can use it along side my Xoom. I love Android, but I love technology more. I can appreciate what all companies do. You almost give me the impression that you need to be using a device with only one button. In which case that's fine. But don't sit and complain like so many other bloggers without even the slightest hint as to how to make improvements. Makes you look like a Apple fanboy which I'm sure you don't want to be referred to as. Thanks.
    wingzero0
    • RE: Android Honeycomb 3.1: A mixed bag of meh

      @wingzero0
      XOOM?! seriously?
      Hasam1991
      • RE: Android Honeycomb 3.1: A mixed bag of meh

        @Hasam1991 Yeah. Wanted to support the launch of Honeycomb. Plus, it will receive updates before other tablets unless a 'Nexus' tablet is developed in the near future.
        wingzero0
      • RE: Android Honeycomb 3.1: A mixed bag of meh

        @Hasam1991 The <a href="http://www.android-tablet.org">Amazon fire tablet</a> is coming out soon and will be pretty sweet, running a customized Honeycomb built
        Jeffrey1980
    • RE: Android Honeycomb 3.1: A mixed bag of meh

      @wingzero0 User experience is a very personal thing. You may like the one in Honeycomb, but that doesn't invalidate my opinion. I've used a dozen tablets with Froyo or Gingerbread, and prefer them to Honeycomb. YMMV.
      JamesKendrick
      • RE: Android Honeycomb 3.1: A mixed bag of meh

        @JamesKendrick True. But why not at least make a suggestion for how to fix it? You never know who's reading your blog. You may have the idea that revolutionizes Honeycomb, yet you dont offer a better alternative.
        wingzero0
      • RE: Android Honeycomb 3.1: A mixed bag of meh

        @JamesKendrick "It?s not Google?s fault that developers are using different methods in apps, but I would maintain that it is Google?s fault for allowing it to happen."
        I think that should be...
        "It's not developers fault that they are using different methods in apps, it is Google's fault for letting it happen."
        Unless of course, Google do give guidelines for all this stuff, and the Developers just ignore them...
        I do like the idea of self closing apps, how do they know when you've finished with them?...
        Transporter25
      • RE: Android Honeycomb 3.1: A mixed bag of meh

        @JamesKendrick
        Agree.
        I have not experienced the crashes and issues you have encountered (ASUS Transformer) - mayhap it is more device or OS addon specific?
        rhonin
      • RE: Android Honeycomb 3.1: A mixed bag of meh

        @JamesKendrick -- Like they say "opinions are like a**holes, everyone has one". Your blog isn't worth the time to read such shallow analysis...
        simul8guy
      • RE: Android Honeycomb 3.1: A mixed bag of meh

        @JamesKendrick He appears to simply be a fandroid that can't accept that somebody doesn't like something about an Android device or would choose another platform so he has to attack. Glad that he likes Android but that doesn't invalidate your opinion or anybody else's choices. Something that fanboys of any side just can't seem to understand.
        non-biased
      • RE: Android Honeycomb 3.1: A mixed bag of meh

        @JamesKendrick so can I call iFad a mixed bag of other companies components under the name of innovation?
        MenaRefaat
    • RE: Android Honeycomb 3.1: A mixed bag of meh

      @wingzero0 I am with you, ZDNET Writers just Write and never seem to have a clue! Well at least two of tthem don't... Watch, this will get deleted because they can unjustly critique the XOOM but don't ever call them on it.

      As for your writing, you're right, he got a cup of Jobs Special Juice awhile back and has been living in the Reality Distortion Field Ever Since!

      As for Honeycomb, the only issue I have seen is the Browser but Opera solves that problem and everything else just works! It doesn't matter though because the platform is growing in spite of these guys and their Bias.
      slickjim
      • RE: Android Honeycomb 3.1: A mixed bag of meh

        @Peter Perry - How dare JK criticise Android or our Great God Google! Get your pitchforks and lets burn the heretic.
        Midgeslayer
      • &quot;... in spite of these guys and their Bias&quot;

        @Peter Perry

        Speaketh one of the most (pro-Google/Android) biased posters here.

        Irony or hypocrisy... or both :-)
        MacCanuck
      • RE: Android Honeycomb 3.1: A mixed bag of meh

        @Peter Perry I hate to say it but this is a case of the pot calling the kettle black...
        athynz
      • RE: Android Honeycomb 3.1: A mixed bag of meh

        @Peter Perry I don't really think it's unjust. I think he came up with valid and pointed criticism... I'm not an apple fan boy, I'm an android developer, and I agree with him.

        ZDNet sometimes spouts crap, but this time, for once it's pointed and he says exactly what he doesn't like.
        snoop0x7b
      • RE: Android Honeycomb 3.1: A mixed bag of meh

        @Peter Perry
        Unlike any bias that you may have, eh Mr. Perry. We all know where you stand, given your post history...
        T-Wrench
      • RE: Android Honeycomb 3.1: A mixed bag of meh

        @Peter Perry You are correct...[i]Peter Perry just posts and never seems to have a clue![/i]
        non-biased
      • RE: Android Honeycomb 3.1: A mixed bag of meh

        @Peter Perry
        I agree with @snoop0x7b
        This article is pointed and James Kendrick says gives his opinion. Other opinions may vary.
        virthddman
    • RE: Android Honeycomb 3.1: A mixed bag of meh

      @wingzero0

      You know who are just as annoying as "Apple Fanboys"? Android Fanboys! Take a look in the mirror for sanity's sake. Why are you so emotionally invested in being pro-Android and anti-Apple? Please don't go on a rant about why one is better than the other. I want to know what it is that makes you so zealous. Are you a large shareholder in Google? Are you a Google employee? Seriously, what is your and every other Apple, Google, et al Fanboy's deal?
      scitamehtam