Skill Level Intermediate
- [David] If you're an Android developer, you've probably written a lot of boilerplate code to manage navigation between screens. The code always looks the same, creating what are known as intents and starting activities; and it always has the same verbosity and associated risks. Google's new Android Jetpack libraries offer a better way to manage navigation in your apps. The navigation architecture component: This component lets you predefine your apps' destinations, whether they're activities or fragments, and then trigger navigational moves with a tiny amount of code.
The goal is to make Android apps easier to develop, but also more stable and maintainable over time. My name is David Gassner, and I'm going to show you how to use the navigation component and its related tools, from architecting your app, to building your navigation map or graph, to navigating from screen to screen, and passing data around. I'll be working in Kotlin but you can easily translate the app to Java if that's your preference. Either way, your Android apps built with the navigation component should be easier to create and maintain than ever before.