Material Design

A good place to begin before discussing the operating system itself is to explain what exactly "Material Design" is. The term comes up a lot throughout the course of the review, which makes sense given how the biggest changes that users will see when moving from KitKat to Lollipop will be because of Material Design. Material Design is a set of design principles, and contained within them is something of a mission statement about Google's approach to services across multiple platforms. Material Design is definitely not Google's first big change to the Android interface, but this time I'm actually very confident that it will be the last we see for a very long time. I'm very impressed by the work Google has done to create an interface that looks and feels modern, simple, and beautiful. Before getting into what Material Design looks and acts like, I'd like to address and give my thoughts about Google's previous style of interface design which was called Holo.

To me, Holo always seemed like a transitional type of interface. Google had just brought on Matías Duarte, but as someone whose first smartphone was a Palm Pre, I didn't feel his influence anywhere at all. I think that Holo was a definite improvement over the previous Android interface, but that isn't really saying much. In my opinion, it still didn't feel coherent or look visually appealing. For example, if you showed me the two screens above without the status bar and navigation buttons, I would be hard pressed to tell you that they're from the same operating system. They don't share a single common interface element. The lack of color and use of grey was also questionable. While some users protest the heavy use of white in many modern interfaces, to me the grey that was commonly used in Holo Light applications was analogous to a dirty white cloth. The lacking color also made applications feel rather dull and lifeless, and I almost wondered if it was an effort to try and mask the fact that phones were shipping with either under-saturated or over-saturated displays by just having almost no color at all. 

With my disappointment in Google's new interface, I was worried that it would just be something I would have to deal with for many years. Fortunately, less than one year after Android Ice Cream Sandwich was released, we were given a glimpse of the beginnings of a new type of design that was distinctly not Holo. It was in a feature called Google Now which launched with Android 4.1, and that many people now use everyday. This application used bright white cards to display relevant information, and had a much heavier use of color than any other applications that shipped along with Android. While at the time this could have been dismissed as the most obvious way to make an application that is constantly displaying and updating information for the user, in hindsight it was clearly the beginning of a new type of design being practiced at Google. It was still immature, lacking the animations, drop shadows, and dynamic nature of Material Design, but it began the dissolution of the Holo interface that had just been introduced.

Finally with the end of Holo, comes the beginning of Material. When Google gave a sneak peek of the new interface for Lollipop at Google IO I was very excited by what I saw seeing. The basic idea of the cards in Google Now had been applied to the entire operating system, and expanded upon in ways that I hadn't expected but have been pleasantly surprised by. As you can see above, both applications display the sections of the interface on white cards that float above the background and cast slight shadows. There's also a much greater use of color, and a better use of screen real estate by dividing the application into multiple sections which can be seen in the new Calendar application. The Settings application is actually a bad example in this regard, as the increased spacing means the main page fits less on screen than before, but this is an exception and I included it primarily to show the contrast between new and old.

Material Design is based upon the ideas of paper, lighting, shadows, depth, and color. While this sounds a lot like the skeuomorphic interface of previous versions of iOS, Material Design doesn't limit itself based on the actual limits of physical items like paper, and it doesn't go to the point where applications are merely digital recreations of real world objects. There's also a heavy use of animations. Everything you touch seems to respond with an elegant animation, and the different cards in the interface can expand, contract, and stack atop one another to create an extremely dynamic feel. It is truly hard to explain, and it's really something that needs to be used to be fully understood.

The last thing to say about Material Design is how it represents more than just a way to design applications. Like I said earlier, within Material Design is a mission statement about Google's approach to services across multiple platforms. Although I've discussed it within the context of the Android platform, Material Design is going to be what you see in Google's applications across every platform. From web apps, to Android, to Chrome, to iOS applications, you will see a consistent style of design that adapts to different display sizes, use models, and methods of input. Overall this is a great step forward in making Google's services consistent across all devices, but I think in the context of iOS applications Google may be going a bit too far by ignoring the design guidelines of that platform in favor of their own.

Introduction Lock Screen, Launcher, Keyboard, and Navigation Buttons
Comments Locked

126 Comments

View All Comments

  • simboss - Monday, December 1, 2014 - link

    "In fact, I haven't really noticed any significant bugs at all after upgrading to Lollipop, which says a great deal about the work Google has put into testing to make sure things are stable. "

    really?
    Both my Nexus 5 and 10 have been more unstable with Lollipop, crashing and even getting in a rebooting loop.

    What devices have you used to do this testing?
  • simboss - Monday, December 1, 2014 - link

    Adding to that that the default unlocking on the nexus 10 and the notifications are less efficient than they were.
    Ars had a pretty good summary of it:
    http://arstechnica.com/gadgets/2014/11/the-nexus-1...
  • Brandon Chester - Monday, December 1, 2014 - link

    Nexus 5 and Nexus 6. I've had no issues with the former, and I was just speaking from my experience on the matter. I haven't seen any major complaints elsewhere though.
  • JarredWalton - Monday, December 1, 2014 - link

    I've had a SHIELD Tablet and Nexus 5 both lock up and require a reboot more often than with 4.4. Might be more of a factor of playing games (PvZ 2, AC Unity Companion), and I don't mind the change in general, but I think we'll see a few updates and maybe 5.0.2 or whatever will be needed before we really clear up the remaining glitches.
  • blzd - Monday, December 1, 2014 - link

    Same here with my Nexus 5. It would seem (quite a few others have noticed this as well) that if you don't reboot the phone eventually just dies. It's happened to me twice only to work perfectly again after the reboot, and hasn't happened since I started rebooting nightly.

    The theory is a memory management/leak bug but it's tough to tell.
  • Impulses - Tuesday, December 2, 2014 - link

    That happened with Kit Kat too tho, if you pummeled Chrome with enough tabs or generally just kept enough things open it'd eventually get weird... Keyboard would act up, my 3G or GPS would occasionally work intermittently, etc. Reboot always fixed it... On face value it sounds less stable than my older Android phones but I never did quite as much on them as on the Nexus 5 either (and/or I'd end up rebooting to flash stuff for features I don't really need anymore).
  • errorr - Monday, December 1, 2014 - link

    My Nexus 5 has been great and jank only shows up when it gets hot... Otherwise it has been awesome for me.

    Unfortunately not so for the wife. She has a memory leak somewhere since the update and her Nexus 5 is almost unusable as everything grinds to a halt.
  • Jon Tseng - Monday, December 1, 2014 - link

    One cool thing I just noticed today - apps can now change colour of status bar to match their UI.

    Websites can also do this (thought not many are doing it at the moment) e.g. BBC News turns status bar red.
  • bensulli - Monday, December 1, 2014 - link

    Hang on, why no battery life tests? One of Lollipop's biggest draws is Project Volt which claimed an increase of up to 30% in battery life. Anandtech does the most comprehensive battery life evaluations on the internet, why not here?

    Great article otherwise though! Thanks!
  • Brandon Chester - Monday, December 1, 2014 - link

    I really would have liked to, but Volta has more to do with increasing battery life through better coalescing of CPU and network usage. When you do a battery life test which is just a web browsing or video playback test, none of those improvements have much of an impact. With the current state of mobile and how sandboxing works, it's very hard to build a battery benchmarks that can string together multiple applications being used to simulate a workflow that would get better battery life on Lollipop compared to KitKat.

Log in

Don't have an account? Sign up now