Note to Readers: Saumitra is one of the newest members of our smartphone team. He has contributed to articles in the past but we'd like to formally welcome him to the AnandTech team. Saumitra will be focusing on everything Android and iOS. Welcome Saumitra!

The tablet market today is a far more interesting place than it was just over a year ago. Since the launch of the iPad, there hasn’t been a real competitor to iOS in the tablet space. We’ve seen customized versions of Android for larger devices like the Galaxy Tab, but they’ve all had their fair share of limitations. In fact, Android releases up to Gingerbread were never really designed to be used on larger screens. But Honeycomb has the potential to change all that and it could be just the catalyst manufacturers need to come up with the next iPad-killer.

It’s been public knowledge that Honeycomb (v3.0) was going to be the next major release of Android after Gingerbread (v2.3). It all started when Andy Rubin showed up at the D: Dive Into Mobile event with a mysterious looking tablet that was later revealed to be the Motorola Xoom running Honeycomb. CES gave us a sneak peek at Xoom and a host of other tablets that would run Honeycomb. At the Honeycomb launch event a few weeks back, Google gave us a full-blown preview of the OS. Now, with the Xoom releasing this month, the time has come for Google's official answer to the iPad.

Honeycomb has been designed ground-up for use on tablets. Google also confirmed that Honeycomb is a tablet-only OS for the time being and that some of the new features would eventually transition over to phone versions of the OS. That’s where the next release of Android codenamed Ice Cream comes into picture; more on that later. Honeycomb represents Google’s first effort to be a serious contender in the tablet market. Make no mistake here Honeycomb is an absolutely massive release with a smorgasbord of new user and developer features; some of which are so well implemented that they could give iOS a run for it’s money. Without further ado, let us dive into the juicy bits.

Home Screen

First up, you’re immediately greeted by new home screen. It’s slick, futuristic and predictably neon. Google calls this the holographic UI design based on a content focused interaction model. The new home screen has a very clean layout; there’s the new notifications bar on the bottom right, and three buttons on the left that let you go back, go home and use the new multitasking UI. On the top we have the Google search bar, applications drawer and the add button for adding shortcuts, widgets and other stuff to the home screen.

There are five home screens that you can swipe between; clicking the Add button displays a side-scrollable list of available widgets, applications and wallpapers in the lower half of the screen, and a preview of the five home screens in the upper half. The applications drawer shows a similar preview, but in the bottom half of the screen. Overall, the home screen in Honeycomb is laid out nicely and makes good use of the added real estate offered by tablet-sized screens. Its informative, unobtrusive and yet offers ample space for widgets and other items.

Notification Bar

Honeycomb moves the beloved Android notification bar into relative obscurity; tucked away in the bottom right corner of the screen. It displays only the bare essentials; the time, network connections and battery life when not actively in use. Once you click on the notifications bar, it pops out to show you a detailed system status and lets you access things like brightness, screen orientation, notifications and so on; much like the Power Control widget on Android phones. With Honeycomb, Google has overhauled the notification system by leaps and bounds. Notifications are now much more detailed and are very Growl-like. Notifications from apps like the Music Player show album art and let you control music right from the notification. The Google Talk app for example, shows display pictures and message previews. Notifications can therefore leverage the new UI framework in Honeycomb to include images and other elements to offer users more granular control over apps directly from the home screen.

Rich Widgets

Honeycomb adds support for new interactive widgets that display more than just static information. The new widgets UI is completely redesigned to take advantage of larger tablet screens. Apps like Gmail, YouTube or the Music Player can now use new widget forms like stacks, lists and grids and update them with real-time data. For example, the Gmail widget allows users to scroll through their mailbox and the YouTube widget shows previews of videos arranged in a continuously scrollable stack. The new widgets looked stunning with smooth UI animations and transition effects. Of course, that can be partly accredited to the fact that the Xoom runs some pretty solid hardware; lets just hope Google managed to deliver this performance even on lower-end devices.

Action Bar

Google defines the Action Bar as a widget that replaces the title bar at the top of any activity within an app. It displays contextual options and settings depending on the activity being performed in an app. For example, in the Gmail app, if you’ve selected message, the action bar changes to display options like mark as unread, trash, report spam, change labels or mark as starred. The action bar is tightly integrated into the OS for activities like cut-copy-paste; where pressing and holding initiates the “select” feature and options like cut, copy, paste or share can be accessed via the action bar.

For example, in the image below, the action bar shows the app icon and the activity title on the left and useful items from the options menu as icons on the right. Any other options can be accessed via the Overflow Menu on the extreme right.

Each element that appears in the Action Bar is called an action item and has its own logo. The app icon can be used to navigate home or move up through the activity. The Overflow Menu can also be customized with icons for items not appearing on the Action Bar. The Action Bar also allows moving back and forth through fragments with action tabs. Action tabs, for example, are used extensively in the Mail app and are very useful to navigate directly to specific parts of an app. Action tabs greatly simplify navigation in Honeycomb as compared to iOS, where in most cases, you must sequentially move up the hierarchy of screens to get to the first screen.


Fragments is another addition to Honeycomb’s API to let developers create more flexible UI designs for tablet-sized screens. The larger screens make it easier to combine or interchangeably use UI components. Fragments lets developers decompose an activity into multiple fragments. For example, imagine using the Pulse app on a phone and a tablet. On the phone, owing to the limited screen size, viewing a list of articles is one activity, and reading an article is another activity. With fragments, you can combine this into one activity where one fragment shows the list of articles, and the other fragment shows the selected article. Thereafter, each fragment has its own set of callback methods and user input events. A fragment is basically a modular, reusable component with its own layout and behavior that lets it adapt to different screen sizes. In cases where this is not possible, developers can launch separate activities with independent fragments.


Honeycomb builds on Android’s existing multitasking support with a fresh new UI. The multitasking interface slides in from the left of the screen and populates itself as a list that shows recently used and currently running apps with the app icon and a static image of the app’s last saved state. Again, the UI is extremely clean and should work well on tablets.

Application & Under the Hood Updates
Comments Locked


View All Comments

  • chomlee - Monday, February 21, 2011 - link

    "Price is another issue if Honeycomb tablets need to stay competitive in the market. While more expensive tablet price points are tempting, a major strength of Android has been its ability to hit lower price points. For Honeycomb to be successful we need to see tablets priced at an iPad-competitive $499 in addition to the more expensive options we've been hearing about"

    I agree exactly. I would rather get a gingerbread tablet but if they are going to charge more than the IPAD, why would I risk "Trying" a different device when I know the IPAD runs great. I also think the 3G carriers need to be more flexible with the plans. There are alot of customers like myself that would like to enable the 3G one month here, and one month there (for vacations), but most carriers won't allow you to do that. Apparently, you can do that with the IPAD which is a huge plus (and it is relatively inexpensive).
  • medi01 - Monday, February 21, 2011 - link

    Why? Let me guess:

    1) SD card slot
    2) Folder support
    3) Being able to read from / write to your tablet instead of syncing it with only one PC?
  • michael2k - Tuesday, February 22, 2011 - link

    That costs $100?
  • Shadowself - Monday, February 21, 2011 - link

    "just the catalyst manufacturers need to come up with the next iPad-killer."

    The "next iPad-killer"? Has there been a first one *yet*?
  • NCM - Monday, February 21, 2011 - link

    Just couldn't resist the "xxx-killer" cliché, could we?
  • B3an - Monday, February 21, 2011 - link

    @ Saumitra, nice first article.

    Regarding the next Android version 'icecream' you mention "we can be reasonably sure that many of the under-the-hood enhancements like an updated Dalvik VM, support for multi-core SoCs, 2D/3D hardware acceleration ... should make the cut."

    But doesn't Android 2.3 not have this stuff already? It must atleast have some kind of multi-core support... whats the difference between support in 2.3 and 3.0?

    I'm sure 2.3 also FINALLY now has UI GPU acceleration. Which has been one of the biggest problems with Android - laggy scrolling / animations. I hope to see a super smooth UI when i get the Galaxy S2.
  • Saumitra - Monday, February 21, 2011 - link

    Glad you liked the article!

    1. Gingerbread might be able to see and recognize multi-core processors, but that's where the story ends. The Dalvik VM in Honeycomb actually divides tasks between cores, which Gingerbread doesn't support.

    2. Gingerbread's UI only had partial hardware acceleration. That is, not all parts of the OS were being hardware accelerated.
  • jalexoid - Monday, February 21, 2011 - link

    "Gingerbread might be able to see and recognize multi-core processors, but that's where the story ends. The Dalvik VM in Honeycomb actually divides tasks between cores, which Gingerbread doesn't support."

    That is incorrect. The major Dalvik VM improvement in 3.0 is that the VM can run the garbage collector in another thread. Ever since beta version Dalvik VM has supported SMP, if the kernel had that module enabled.
    (Dalvik VM threads are directly mapped to pthreads. pthreads have supported multicore on ARM ever since the first ARM with multiple cores rolled down the manufacturing line and on other architectures since last century)
  • jrs77 - Monday, February 21, 2011 - link

    Having seen the last weeks MWC there's no doubt that Google did alot of work with Honeycomb and it looks like it could actually give iOS a run for it's money.

    However, as you noticed there yourself, platform fragmentation will be yet again a killer for Android-based tablets as the experience simply will differ too much between all the devices.
    That's the strong point of Apple and iOS, as they don't have to deal with this issue and have a consistent experience throughout all their devices.
  • mantrik00 - Monday, February 21, 2011 - link

    There seems to be a confusion between differentiated UI (user experience) and platform fragmentation. For all the doomsayers like you, Android has been growing precisely because of this differentiated experience, which people who are hooked to Apple's ecosystem will never be able to fathom.

Log in

Don't have an account? Sign up now