One of the new Architecture Components announced at Google I/O 2018 was the Navigation Component which encapsulates principles of well-designed Android navigation. The Navigation Component consists of higher-level abstractions that allow us as developers to more clearly and cleanly define how we want navigation to flow within our apps. For those of us looking to adopt the Navigation Component into existing apps, there are plenty of questions: How do current navigation patterns translate to the Navigation Component? How do we handle multiple activities since the new navigation controller handles a single activity? How can we do improve our deep linking, how can we clean up our back/up logic? In what ways can we extend the Navigation Component? How does the Navigation editor work? In this session, we will look at the fundamentals of the Navigation Component and try to answer these questions, making navigating our apps smooth sailing for our users.
What is the Navigation Component and where does it fit into Android Jetpack and the Support Libraries?
What are the classes and abstractions contained in the Navigation Component?
How do you get started with the Navigation Component in a new app?
How can you convert existing Android navigation patterns to the Navigation Component?`