Google I/O may be over, but Google has left plenty of educational content from the event on the web for developers to learn from for the rest of eternity. Obviously, many of the sessions at Google I/O were specific to Android, so if you were unable to attend, you can find ten full-length Android sessions below for your viewing pleasure, courtesy of Google’s Developer YouTube channel.
First, here’s an hour of Google breaking down what’s new in Android Developer Tools:
This one introduces new APIs and capabilities in the Android Open Accessory Development Kit 2.0, and provides demos:
This one is about new low-level media APIs in Android:
The next one’s all about improving the navigation of apps. Here’s the description:
An app is useless if people can’t find their way around it. Android introduced big navigation-support changes in 3.0 and 4.0. The Action Bar offers a convenient control for Up navigation, the Back key’s behavior became more consistent within tasks, and the Recent Tasks UI got an overhaul. In this talk, we discuss how and why we got where we are today, how to think about navigation when designing your app’s user experience, and how to write apps that offer effortless navigation in multiple Android versions.
This one’s about the “sensitive side of Android”. The description says:
Android has a sensitive side. In this session, we will call out all the Android sensors: accelerometer, gyroscope, light, and more. We’ll cover best practices for handling sensor data, with special focus on balancing battery life and usability.
This one is about advanced topics for expert Android developers. These include coding tips, tricks, bandwith saving techniques, implementation patterns, exposure to some of the lesser-known API features, and tips for minimizing battery drain:
This one is about smoothing out performance in Android user interfaces:
This one is about multi-versioning Android UIs:
This one is about the Android Design Guide and other app design tips:
Finally, this one tackles security and privacy in apps. These, of course, are chief concerns among users: