Final Words

I think Google really hit the nail on the head with Android Lollipop. It evokes the same sort of feeling that the release of iOS 7 did, without some of the negative experiences that followed. Getting a brand new interface is always exciting, as it can dramatically change how it feels to use your phone. Moving from KitKat to Lollipop still provides you with a familiar Android experience, but it almost feels like getting a brand new phone in a way. There's a brand new UI, and big improvements to performance. But unlike the upgrade to iOS 7, Android Lollipop hasn't plagued my devices with application crashes and other bugs. 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. 

Material Design impresses me, and I think it's going to be around for many years to come. I find this feeling reassuring, as Google has a track record of redesigning large portions of Android with every major release. With the past designs, I never really felt like they were going to stick around for very long, and they never did. Material Design feels like Google has finally gotten Android to where they want it to be, with an interface that doesn't need any OEM overlays to be presentable. Of course, some OEMs will never change their policy of putting their own skin, but that's something Google isn't going to be able to fix. While we may see very iterative changes to Lollipop's interface in future updates, I don't think they're going to be anything beyond changes to the placement of buttons or the color of icons. Material Design also extends far beyond your Android device. It will eventually apply to all of Google's services on all platforms, so that your web browser, your tablet, your smartphone, and even your watch will all look and behave similarly. 

The performance increases are also greatly appreciated. Android hardware has advanced rapidly, and the move to a new application runtime is overdue, but warmly welcomed. The improvements it can bring to a device are actually amazing; it can feel like getting a brand new phone. The interface performance on Android still isn't quite perfect, but to be quite honest, it's not at all alone in this regard. I can name areas of every major smartphone OS that are susceptible to drops in frame rate, it's just not possible to write perfect software. I think what can be said is that overall, Android is pretty much at the same level as Windows Phone and iOS for animation smoothness and general performance. There is still the exception of certain poorly written applications which are up to developers to fix, and some of these even come from Google themselves, but I'm confident that we're moving toward a point where these remaining issues will be fixed simply because they aren't acceptable anymore.  

Of course, the last thing to discuss about an Android update is whether or not you're going to get it. Unfortunately, I still can't answer this question for most users. Android's nature means that Google doesn't have any influence over users receiving their updates, except the users that have Nexus and Google Play Edition devices. Although I can't guarantee you an update, I can say that the situation is looking good for more users than it has in the past. We've seen updates ship in record time from companies like LG, NVIDIA, and Motorola, and they should be commended for putting in the effort to get updates out to users in a reasonable time. Other companies like HTC have made promises to update their flagship devices from this year and last year to Lollipop within a 90 day time frame. While this doesn't cover every Android user in the world, it covers more users than we've ever seen in the past.

Going into the future, there are some improvements Google should make. Continuing to work on the performance of problematic applications is definitely necessary, as they stand out more than ever alongside a library of extremely well performing apps. I think it would be worth it to start creating special landscape layouts for applications, and to introduce more features that take advantage of larger displays. Google has entered the phablet market with the Nexus 6, and they need to create software that provides a reason for having such large devices. The only other thing they need to do is to continue innovating and improving, which they've been able to do time and time again. We haven't yet seen everything that Android Lollipop has to offer, as developers are only beginning to take advantage of the new APIs and features it brings. But with a great new interface, new applications, a new runtime, and new users adopting Android every day, the future of Android certainly looks bright.

Camera2, ART, and Performance
Comments Locked

126 Comments

View All Comments

  • Impulses - Tuesday, December 2, 2014 - link

    I actually prefer dragging twice to the top right button, but that's probably because I use my phone primarily with my left hand. Always thought the quick settings button was much too close to the clear all button tho, despite only hitting clear all by mistake once or twice over the last year or so. I do agree some of the other card stacking and UI choices are questionable tho.
  • toyotabedzrock - Monday, December 1, 2014 - link

    Oh and can Google explain why Chrome crashes when sharing to Google Plus via the mobile browser interface? Or why the plus app shate function causes every other app to crash from memory depletion? Also Google search inexplicably crashes on my Nexus 5.
  • Salty Wagyu - Monday, December 1, 2014 - link

    Tapatalk has the worst jank, even ART hasn't helped much in this case.
  • sonicmerlin - Monday, December 1, 2014 - link

    This talk in Google's 2014 I/O event is very relevant: https://www.youtube.com/watch?v=3TtVsy98ces

    The speaker talks about the issues of Android's render thread priority causing lag, and how google worked to fix it in lollipop. I think it starts about 19:30 in.

    My main question though is how browsers are affected. iOS and WP browsers scroll every webpage with pixel perfect smoothness, where Android has always lagged and stuttered on heavier web pages. Does Lollipop fix this, or will developers have to code their browsers to take advantage of Lollipop?
  • lukechip - Monday, December 1, 2014 - link

    Lollipop is OK, but I preferred KitKat on my Nexus 10. On Lollipop is seems to take longer / more steps to do the same things compared with KitKat. For example, switching users used to involve:
    1/ swipe down settings
    2/ click on my avatar
    3/ enter my PIN
    Now it invovles:
    1/ swipe down notification tray
    2/ click on user icon
    3/ select my avatar
    4/ drag up lock icon
    5/ enter my PIN

    The added steps add zero value to my experience. It's just plain poor.
  • Egg - Monday, December 1, 2014 - link

    Frankly, I've been disappointed with Lollipop on my Nexus 5. First thing I noticed was highly visible frame drops swiping between Google Now and the home screen. Dashclock no longer functions. I need to swipe twice to get to the quick shortcuts... why? Meanwhile I haven't seen any improvement in the camera, which is slow to focus even in well lit scenarios... wasn't Camera2 supposed to fix this?
  • Egg - Monday, December 1, 2014 - link

    Just tested with GPU profiling, I can routinely get spikes to appear. Yikes!

    (Also, Google Now's undo toast is not full caps like the updated Photos app undo toast.)
  • tuxRoller - Monday, December 1, 2014 - link

    I really, really wish art had delivered what was promised, but for my sample of three nexus devices (n4,n5,n7-2013) it has unambiguously made things worse. All of these devices were installed using the factory image, and two were fully wiped. It's just awful. Load times are longer. The interface is more janky than its ever been. Battery is pretty much unchanged, however.
    Google would've really benefited from an additional developer release so as to avoid these issues.
  • Lavkesh - Tuesday, December 2, 2014 - link

    I have infact experienced a drop in battery life. I used to have a screen on time of little over 3 hours on Kit Kat but I havent been able to touch 3 hours so far with Lollipop.
  • Lavkesh - Monday, December 1, 2014 - link

    There are still a few areas where the animations do not even do close to 30 fps, let alone 60. The new message application is one example when you tap a conversation and it opens up. That said I do not know why the animations on my iPhone 4s feel smoother. Are they rendering it higher than 60 fps or is it physics?

Log in

Don't have an account? Sign up now