From a gradle point of view my project structure l...

# android-architecture

[Lilly]

From a gradle point of view my project structure looks like:
Project A (android app) -> Project B (android library) <- Project C (android library)
So instead of having a multi module project I have a bunch of standalone projects that are published separately. I ran into some problems and was overthinking this approach and I don't know why I went this path in the past (I guess I didn't know how to publish modules in a mm project).
Since we can publish modules in a multi module project (so they can be shared with other projects) wouldn't it be better to got with a multi module project. I can't see any benefit with having a lot of single projects. Are there any advantages disadvantages between these approaches?

[Javier]

working with published modules are hard and tedious, it has sense if you are going to share them among libraries/apps, but if they belong to a specific project, any time you change it you have to republish and update the version in the app...

[Javier]

and it can be slow, if you are publishing to mavenCentral you can lose 5-15 min only waiting until the lib is published (plus the time of the release process)

[Daniel]

Modules in their own repo enable the fllowing scenario: Module A is integrated in two different apps B and C. You will find this in large corporations with multiple teams & apps.

For a single app it's way overkill. Except you have like 50+ modules which starts to task the build system and Android Studio.

[Lilly]

Thanks @Javier, @Daniel