The greatest Android modularization mistake and how to undo it

One upon a time, there was a singularity named :app module. Then came the smaller monoliths, namely :persistence, :networking and :models

Photo by Clay Banks on Unsplash

Why layers monoliths is a mistake?

• They are still monoliths, albeit smaller than :app
• All the problem that applies to :app still applies to :networking , :persistence and :models while you get none of the benefits modularization brings

Benefits of modularization

• (Incremental) build time
• Small and focused module — more productivity while working on a particular feature/ product
• Features/ products are more self-sufficient and less inter-dependent so more flexibility in design, implementation and testing
• Dynamic delivery of modules

More details in Jeroen’s article 👇

Modularization - Why you should care

Why is it the greatest mistake?

• The Internet is filled with…