The UI: Holo Evolved

When I first met Holo, Google's Honeycomb theme, I wasn't convinced that it was something that would last. It was different, which earned Google points for sure, but it wasn't exactly comfortable. I was surprised to see an evolution of Holo used in ICS, but the theme has grown on me.

Ice Cream Sandwich feels a lot like Android meets Windows Phone. Part of that surely has to do with the very contrasty nature of the theme, but it's also the choice of font (Android 4.0 replaces Droid Sans with Roboto) and hard edges sprinkled throughout the UI. Holo is still distinctly Android in that there are still multiple home screens with support for widgets, but it's also different. Ice Cream Sandwich is Android maturing, it's the second implementation of Holo allowing us to finally plot a trajectory for where Google sees this thing going in the near term. It's different as I mentioned before. Holo and ICS aren't iOS nor does it look like they ever will be. The UI is either going to pull you in or turn you off. I like it. It's different, it's clearly a play on the whole Android theme; it's the type of UI you'd expect from an OS named after a robot.


Droid Sans v. Roboto (ICS)

At the same time it's no longer awkward. Elements of the design and many of the first party apps are just clean. It's truly a first class citizen. Different than both iOS and Windows Phone, but with a design that's just as credible.

The core of Android remains unchanged. You get multiple home screens (five by default) that you can populate with shortcuts, widgets or folders. Widgets are resizable just as they were in Honeycomb. Shortcuts work the same way they always have, while Folders get a nice update in ICS. Drag any icon on top of another one and they'll create a folder. Folders are quick to open and easy to rename, just tap on the name of any open folder and type away.

The app launcher gets a bit of a facelift. Instead of an endless scrolling cube, you get pages of apps that you flip through. Once you've reached the end of your pages of apps you'll start flipping through widgets. All of this is smoother than it has ever been on Android.

Gingerbread vs. Ice Cream Sandwich
  Gingerbread Ice Cream Sandwich
Lock
Home
Launcher

 

The New Contextual Menu Button

Play around with ICS for a little bit and you'll quickly pick up on a new UI element that appears inspired by Windows Phone:

These vertically oriented ellipses will appear at either the top or bottom of an app and reveal additional menu options.

In Gingerbread you had the fixed Android menu button, but with that gone you have to rely on these contextual menu buttons to bring up additional actions. I'm honestly pleased with the move because all too often I'd forget to tap the menu button to see whether or not there were additional options in Gingerbread. ICS makes it very obvious when there's more you can do.

The Task Switcher

A cornerstone of any good operating system is a good task switcher. I still believe that webOS dealt with the concept of individual apps and switching between them better than any other mobile OS, but it looks like that platform is pretty much dead with little chance of making it into the top three mobile OSes.

Google and iOS haven't traditionally focused much on task switching, although both have provided support for it. In Gingerbread, you'd switch between apps by holding down the home button, which brought up a list of up to eight of your most recently used apps. Ice Cream Sandwich implements a drawer-style app switcher menu, first introduced in Honeycomb, activated by hitting the dedicated task switcher button:

Gingerbread vs. Ice Cream Sandwich
  Gingerbread Ice Cream Sandwich
Task Switcher

The Gingerbread method of switching may be quicker, but it's definitely not as useful as what ICS offers. For starters you can switch between more than just six apps in ICS. The most recent apps are located at the bottom of the list, the oldest at the top. You can also quit apps using the switcher by sliding them to the left or right. Doing so immediately frees up any memory the app was using, even if it was suspended.

Scrolling through the list of recent apps, like scrolling pretty much anywhere in ICS, is extremely smooth. The only real complaint I have here is that the task switcher takes far too long to draw initially. As I alluded to before, this is something that may get better with a faster SoC, particularly one with a faster GPU.

The Shade & Notifications

Notifications in ICS are still handled via the status bar at the very top of the screen and a pull down notification shade. The shade in ICS is partially transparent by default and once again, very smoothly animated. The network carrier string is included at the bottom of the shade rather than in the status bar at the top. You can clear notifications individually or hit the X to clear all of them.

I am surprised Google didn't borrow the quick settings options its partners usually like to stick in the shade, but there is a link to the system settings panel at the top.

Screenshots

Android 4.x also finally enables the ability to take screenshots from within the OS. There's no necessity for OEMs to bake-in their own screenshot functionality and key press combination, no need to connect using USB and fire up ddms, and no need to root and install some application to make it work. Traditionally, those three have been the exclusive way to get screenshots taken on Android.

To take a screenshot in Android 4.x, simply hold volume down and the power/lock button at the same time. An animation plays, you get a notification, and the screenshot is saved (with a timestamped name in PNG format) in /pictures/screenshots as shown above.

I can't emphasize enough how important being able to take screenshots is for a platform in general. Without screenshots, users can only vicariously share a given OS when they're in direct contact with someone else. Being able to take screenshots without all the nonsense I've outlined above is part of what has made iOS so ubiquitous online - browse Reddit and count how many screenshots of SMS conversations (trite as they all are) are clearly from iOS versus Android. It's clear to me that Matias Duarte understands this, since webOS and even the Danger Hiptop since day 1 had the ability to take screenshots. Now Android 4.x finally joins the fray. 

OS-Wide OpenGL ES Rendering The Keyboard & Facial Recognition
Comments Locked

185 Comments

View All Comments

  • CoryS - Thursday, January 19, 2012 - link

    Guys, this is a NEXUS it is a dev device. That primary reason I got it was because of this...better hardware will be right around the corner...but we won't see another Nexus..especially on Verizon for some time.

    It is refreshing to have a community to fix issues OEMS ignore (yes even Apple) for a change. This is my first unlocked device, and i can't see myself ever going back to anything else.
  • medi01 - Friday, January 20, 2012 - link

    Wake up, Smartphone market (worldwide):
    1. Samsung 24%
    2. Apple 18%

    Android vs Apple = 3 vs 1 and gap is raising.

    Most people turn to apple due to FUD, like this article. Google "steppit out of the shade of its competitor" having three times Apple's market share and much more usable interface (try to quickly access settings like wlan/bluetooth/gps on ios)
  • steven75 - Friday, February 10, 2012 - link

    LOL dont you get it? You don't *need* to fiddle with those settings on iOS necause the battery life is so dramatically better.

    Also, funny reading this comment after Apple's Q4 report where they dominated.
  • Omid.M - Wednesday, January 18, 2012 - link

    I hope Samsung puts out this phone based on GN aesthetics but Exynos 5250 (plus MDM9xxx multi-mode/LTE modem) and blows away the competition.

    @moids
  • Chumster - Wednesday, January 18, 2012 - link

    Could someone clarify on what GPU/CPU he was talking about coming in Q2 devices? Cray? Crate? It was hard to pick up on my headphones.
  • mmp121 - Wednesday, January 18, 2012 - link

    Krait

    Read below:

    http://www.anandtech.com/show/4170/qualcomms-annou...

    Enjoy!
  • Conficio - Wednesday, January 18, 2012 - link

    Really, Google can't survive once Walled Garden platforms like iOS gain traction.

    While it is nice to control the OS (Chrome OS) on PC like devices and nice to stick it to Microsoft, it is essential in the world of smart phones. Google clearly saw that Apple did the unthinkable, wrestle control of the phone's apps away from the networks. That is an existential thread for Google. If there is a billion PC users world wide, there is a multitude of smart phone users, sooner or later.

    If a hardware manufacturer and OS provider like Apple (or Microsoft) controls the apps that can be provided to the phone and features, move from browser to apps on phones, then this is the end of (a profitable) google sooner or later.

    From anther point of view, Google is a huge data center that provides you with data services on their computing power (and you pay for it with advertisement somehow). Apple is a hardware manufacturer that sees it necessary to control the software to deliver a good user experience. Sure, two different approaches to a smart phone OS.
  • hackbod - Tuesday, January 24, 2012 - link

    "Google clearly saw that Apple did the unthinkable, wrestle control of the phone's apps away from the networks."

    There is this weird thing I see expressed a lot, as if Android is a reaction to the iPhone.

    It is not.

    In this particular case, it is obvious: Android's SDK was made available a few months after the original iPhone was on sale, well before there was *any* native SDK for the iPhone. At that time Apple's very clear official policy was that web-based apps was the One True Way to create applications for their phone. There was no concept of an App Store, no phone apps except what Apple shipped built in to the iPhone, nothing wrestled away from the networks in that department.

    If Android was a reaction to anything, it was to the current situation on desktop PCs, with one company controlling that platform, and being able to quite strongly dictate and control its ecosystem and thus large parts of the computer industry.

    One of the goals of Android was to try to keep that from happening in the upcoming mobile industry, by creating an open platform so that everybody in the industry can compete as equally as possible.

    (And an aside -- this also makes it funny to see the recent stuff going around about Google "losing control" of Android. Android was very much set up so that no one company, not even Google, could have anything like the control that Microsoft does over Windows. This should be pretty obvious to anyone who wants to actually write thoughtful articles on the topic and not just link bait.)
  • bjacobson - Wednesday, January 18, 2012 - link

    Can you talk more about this? From Diane Hackborne's post here (https://plus.google.com/u/0/105051985738280261832/... it sounds like the "limitation" is memory bandwidth in that hardwares that are "laggy" are laggy because they can't render to the entire screen 2 and 3x per frame for all the overlays. Which wouldn't seem like so much of a Tegra2 limitation in my opinion considering it has the power to play games like Quake 3 at 1600x1200 @ 60fps (I think...right?). What are your thoughts?
  • hackbod - Tuesday, January 24, 2012 - link

    I don't know about the performance of Tegra 2 playing Quake, but you need to be very careful when comparing the traditional 3d workload that GPUs are highly optimized to support (as exemplified by Quake) vs. the performance rendering 2d graphics.

    Traditional 3d games tend to rely, for example, on triangle rendering as much if not more than raw pixel fill rate, and GPUs are designed to be able to do that fast. When drawing 2d scenes, there are very few triangles but those triangles cover very large parts of the screen and are rendered as overlapping layers.

    On all of the hardware I have seen, for 2d rendering raw memory bandwidth (determining the number of times every pixel can be touched per frame) is the #1 impact on performance.

    Look back at that post -- for a typical scroll of all apps in launcher, without using overlay tricks (which aren't available on Tegra when the screen is rotated), you are looking at touching every pixels about 4 times to render all the layers and composite them to the screen. This is just not a typical 3D game workload.

Log in

Don't have an account? Sign up now