Best Practices for Compose Navigation in Multi-Module Project
<p>This is the 2nd story in the series for Jetpack Compose Navigation. The first story shows how to implement Drawer Navigation using <code>Material3</code> Apis. The link of that story is below</p>
<ul>
<li><a href="https://medium.com/proandroiddev/drawer-navigation-using-material-3-in-jetpack-compose-1bfd5f3f7ed4" rel="noopener">Drawer Navigation using Material 3 in Jetpack Compose</a></li>
</ul>
<p>In this story we will take the same project, extend it to implement Best Practices, the story provides a quick recap in the end.</p>
<p>The project has Drawer navigation with Articles, Settings and About screens. The output of the project is shown below as gif.</p>
<p><img alt="" src="https://miro.medium.com/v2/resize:fit:320/1*TEGUewWMoSEa1RoOkz4qSw.gif" style="height:694px; width:320px" /></p>
<p>When you have a multi screen Project then at least every screen must have its own separate <code>module</code>. In our example I have created three separate <code>modules</code> for each screen and used them in <code>app</code> module to implement basic Navigation.</p>
<p><a href="https://proandroiddev.com/best-practices-for-compose-navigation-in-multi-module-project-eec79ddcef4d"><strong>Read More</strong></a></p>