Google Android 3.0 - Honeycomb Previewby Saumitra Bhagwat on February 21, 2011 7:07 AM EST
- Posted in
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.
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.
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.
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.
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.
Post Your CommentPlease log in or sign up to comment.
View All Comments
jrs77 - Monday, February 21, 2011 - linkI'm the typical nerd using a plethora of different devices and software. My desktop is running Windows 7, my HTPC is running Ubuntu+XBMC, my MacBookPro is MacOS X and my Nokia is running Symbian.
If I would use all Apple products there, then my experience would be consistent throughout all the devices. Hardware and software being developed to work flawlessly etc.
If I'm going to use Android x86 for my PCs and Android 2.3 for my phone and Android 3.0 for my tablet etc, then it simply wouldn't be anymore consistent then the plethora of different OS and devices I'm using currently, so it actually doesn't offer anything I'd desire.
If the manufacturers now start to tweak Android for their devices then the devices get even more differentiated then what I allready have today.
Imho, the Android OS should be allways the same, so that I can switch from one Android-tablet to another and then to my smartphone without problems because of a different UI etc and the hardware for all those devices should be the way, that the experience is aswell the same, e.g. apps loading as fast as on the other devices etc.
Apple achieves this consistency and it's the reason for their success.
bplewis24 - Monday, February 21, 2011 - linkThen go with Apple, if that's what you want. You may not be able to conceive the concept that other people may not want what you want, but that doesn't mean it's not possible.
And if you really believe that is the reason for Apple's success, I feel sorry for you.
strikeback03 - Tuesday, February 22, 2011 - linkI disagree, IMO there need to be substantial differences in the interface design based on the usage model. An interface that works well on a <4" touchscreen is likely not the best option for a desktop using a 24" screen with keyboard and mouse.
bplewis24 - Monday, February 21, 2011 - linkAll what devices? Apple makes one device per generational year. This "fragmentation" argument is bunk.
Would you be happier if blu-ray manufacturers only sold one type of blu-ray machine per year, or do you appreciate the fact that they "fragment" themselves with several models of players at different price points, hardware features and functionality each release cycle?
Yet when phone manufacturers offer cheaper phones with cheaper hardware and lesser features, it's "fragmentation" that is going to kill off the brand? Hardly. The only thing it does it ruin brand-awareness for mainstream consumers who know nothing about technology and believe that an OS manufacturer is the same as a hardware manufacturer.
These people thus believe an Android 1.6 device made by Archos is representative of a Android 3.0 device made by HTC with an Nvidia T20 SoC. For those people, maybe Apple is best, as with their ecosystem it's very easy to live in that sheltered bubble.
spambonk - Tuesday, February 22, 2011 - linkYou overlook that the whole point is to be different on different devices. Android are for people who can make up their own mind, and not have others do it for them.
TareX - Monday, February 21, 2011 - linkWhile I think it's "nice" Google is waiting till the end of May to announce Ice Cream, I think there are two features of Honeycomb Android needs to get pronto:
1) UI HW Acceleration
2) Multi-language support in the browser
I mean I can't believe in 2011, Android's browser can't recognize Arabic text, for example.
TareX - Monday, February 21, 2011 - linkHow smooth did Flash run in Honeycomb's browser? I realize it hasn't been released for Honeycomb yet (ver 10.2) but you can download it from the market. Doe sit make use of Tegra 2's GPU acceleration?
Jumangi - Monday, February 21, 2011 - linkApparently the Xoom won't ship with Flash support....but get it 'sometime in the Spring'.
Pjotr - Monday, February 21, 2011 - link"This is a huge addition as it Again, the UI is extremely clean and should work well on tablets."?
Saumitra - Monday, February 21, 2011 - linkFixed!