In a recent blog post, we took a look at how we can use Compose Navigation in a modularized application. With this approach we saw many benefits — allowing us to centralise our navigation logic in a single place, while also decoupling navigation dependencies from the rest of our application.

When building out the navigation for Minimise, every Composable destination was placed into a root graph. While this works, it isn’t very practical — it means that the entire navigation of our app is structured as a single graph. Instead, it would make more sense to group composable destinations into…

Joe Birch

Android Engineering Lead at Buffer, Google Developer Expert for Android & Flutter - Passionate about mobile development and learning.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store