More info: http://androidmakers.fr/schedule/?ses… Navigating between screens is pretty simple right? No it’s not. Actually not all the time. Last year Google introduced Navigation Component tool helping us standardise the design and the implementation of how screens can pass in front of the Android users. We started to use it with my team last summer and we learned a lot about its benefits, and its pitfalls. In this presentation, I’ll try to give a feedback about what we learned, what hope you can put in it and what’s not to expect from it. Here is an outline of the talk: - The Navigation Component tool and API - Testing your navigation - Specific use cases - Handling multi start points - Handling custom transitions and Shared Elements - How to handle other entities than Fragments - Handling the back navigation - Implementing the navigation logic - 3 examples of implementation patterns we found - Alternative example to Navigation Components - The lib is in alpha, what is it implied by this, for real - Single or Multiple activities what to choose? - Integrate nav controller in an existing app - Conclusion - What can it bring to your app? - Should we use it?

Navigation Component, feedback from the trench