Speakers: Chet Haase, Dan Sandler
As part of the Google I/O 2014 talk sessions, Speakers Chet Haase and Dan Sandler discuss the latest developments in Android technologies and APIs and cover everything that’s new and improved in the Android platform…
Chet Haase – Senior Software Engineer at Google
Good afternoon, and welcome to the first session, right?
What’s New In Android? The session that I like to think of as the Android keynote for the people that couldn’t actually wake up that early. So congratulations for actually waking up this early. We’ll see how it goes.
Yes, well done. Give yourselves a hand. Absolutely. This is a talk that traditionally has been done by me and Romain Guy, who could not make it this year because we didn’t ask him to. Though we did get an appropriate stand-in for Romain. We found someone that can fake a decent French accent.
Dan Sandler – Software engineer Google (Android)
[Speaking French] Eiffel Tower.
Chet Haase: So with that, let’s introduce ourselves, because obviously you have no idea who we are. I am Chet Haase. I am on the UI Toolkit team in Android.
Dan Sandler: I’m Dan Sandler. I’m on the Android System UI team.
Chet Haase: That accent didn’t last very long.
Dan Sandler: It didn’t. I couldn’t.
Chet Haase: All right, so one of the questions that comes up — it just came up at lunchtime, actually, down in the cafeteria — is okay, so there’s an L release. What does L stand for? And I’m here to tell you — can we have like, a drum roll, or something? L if I know.
But for today, we are calling this the L Developer Preview release. We heard about this in the keynote, and we can see by the graphics on the screen that aren’t quite professionally done that it is not a final release. It is instead a preview release where things work pretty well, but it’s not done yet.
We’re hard at work finishing the L release. And in the meantime, we’re exposing it to you to actually use in the meantime, get your apps running and happy on it, and most importantly, to send us feedback about what’s not working exactly perfectly so that we can actually nail that down by the time we ship it.
So in the meantime today, we wanted to give a session talking about all the bits that are new in this preview release that you can get your hands on and play with, and there’s a lot of material in here. We’ll see how fast–
Dan Sandler: We have about six hours of material to cover in 45 minutes, so you’re going to have to hang on.
Chet Haase: So first of all, let’s start with graphics and UI, because I like to start with graphics and UI, and I usually like to end with that as well.
So we heard about the material design stuff in the keynote, and we wanted to touch on a couple of those elements in here. I also want to point out, I’ll give you references at the end of this section, about where to go for more information during the conference. In fact, one of the whole points of this session is to give you just a little bit more detailed info on all of the feature areas that we find interesting to talk about, and also the references to what other sessions and what other videos you should check out, or sandboxes that have further information, or where you can simply find Diane on the show floor if you want to ask her directly.
So in the material area, we have a new theme, we have some new widgets for you, and we also have some new APIs, which you can use at your option. The theme exposes new colors. There’s an idea in material design that all the assets are by default grayscale, and then they can be tinted. So it’s very easy to brand your application, or your application state, with colors, as opposed to baking the colors directly into the assets. So that’s much easier now.
There’s new icons out there. Some of them are animated, part of the rich interactive experience that we have. With material design, we have touch feedback ripples. We’ll see a little bit more about — give the user a sense of interacting with the UI and knowing exactly what’s going on in the UI at all times. And also, activity transitions with shared hero elements. We’ll see a little bit more about that.
In the widget space, we have a couple of widgets that are very important. One of them is minor. It’s CardView. There’s not a lot there. It’s basically a container with rounded corners, and it’s raised up off the view hierarchy plane a little bit to give a shadowed look to it. This is not something that’s too hard to do in your own code, but having CardView there allows you to have this look and feel in a consistent way that other applications are using it as well.