Learn Kotlin, lifecycles, navigation management, and other Android architecture recommendations to build high-quality Android applications.
- [David] There's an old joke about the weather. If you don't like it, just wait a few minutes. The same thing can be said of Google's recommended best practices for Android app architecture and development. It's a constantly-evolving subject, and the most consistent thing about it is change. The recent introduction of the Kotlin programming language and of Google's architecture components for Android have made it faster and easier than ever before to create and maintain Android apps. In my own Android development work, I've had to keep on learning how to adapt my app to new form factors, such as Chromebooks, how to use a brand new programming language, and how to keep to up with ever-evolving and ever-improving development techniques. I'm David Gassner and in this course I'll share some of what I've learned, including how to build an Android app that uses Kotlin instead of Java, how to add simple navigation functionality, and UI components to an app, and how to use some of Google's most useful architecture components, such as LifecycleObserver, ViewModel, and LiveData to create apps that are robust and easy to maintain over time.
- Handling lifecycle events
- Handling view events
- Updating display from new data
- Adding ViewModels to activities
- Subscribing to changes in LiveData values
- Adding a new launcher activity
- Starting activities with explicit intents
- Sharing data with implicit intents
- Adding a navigation drawer
- Adding a header to a navigation drawer
- Handling navigating drawer menu events