Gradle Modularisation
programminghard.dev
As a project grows in size and complexity, and build times start becoming a source of frustration, the topic of modularisation invariably arises. In this post, we’ll explore how to choose the right modularisation strategy for your project and the pitfalls to avoid. We'll delve into the benefits of
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/androiddev by /u/timusus on 2024-10-29 12:43:25+00:00.

This is an article I wrote a while ago, but never got around to publishing. It talks about whether modularisation is really right for your project, and the different ways you can divide up a project.

I’m someone who learns really heavily into clean architecture, and lots of modules. But, I’ve had to learn the hard way that my preference doesn’t always align with what’s best for the team or product I’m working on.

This post aims to assist in making the decision on whether you even need to modularise, and if so, how to slice it.