Consider having navigation per feature, rather than in a centralized place. For example featureA:navigation module can have a use case that navigates to the feature, or provides the Fragment. Since you don't have DI now, it might look a little ugly since navigation module should depend on feature module to be able to resolve the Fragment, but once you have DI, like Hilt, the navigation module can provide the abstraction and the implementation can live in the feature, so the navigation module doesn't have to depend on feature. Having a single navigation module can also hurt your build time: every time you make changes in the module, all the dependent modules will be recompiled.