Multi-module Navigation with Architecture Components

Question

So I have this structure for my modules in my current app.

I haven\'t found any official documentation on multi-module navigation yet but I found this article r

Answer 1

One of the approaches that might be useful is to create a completely new independent module (e.g ":navigation" module) and move all navigation.xml files from all other modules to it. Then we depend on that new (":navigation") module in all other modules where navigation related stuff is needed, and we will be able to access its R.navigation or generated argument classes, etc.

Since the new (":navigation") module doesn't know about anything else in the project IDE will mark red any fragment, activity and other classes we use in navigation.xml files, that are defined outside in other modules but as long as we use full class names (com.exampel.MyFragment) it will compile and work.

    
        // com.exampel.MyFragment will be marked red since IDE can't link it
        // to the existing class because it is in the other module

This creates "hidden" dependency to all classes we want to navigate to in a way that we need to know class names and potentially arguments, and we have to maintain it manually but it allow us to easily separate navigation in independent module.