App Modularisation at Scale

Summary

Grab transitioned its monolithic mobile application into a modular architecture to resolve increasing code conflicts, slow releases, and difficult team collaboration. The team decomposed the single module by establishing base infrastructure modules, shared UI and utility libraries, discrete feature modules, and bridge kit modules for inter-module communication. Dependency injection using Dagger ties these components together in the main app module while preventing feature modules from directly depending on one another. The architecture spans over 1,000 modules across the app, with more than 200 modules in the Grab Financial Group payments domain where over 95% of modules build in under 15 seconds. This approach accelerated Gradle CI and local builds through parallel compilation and caching, though it increased Gradle sync times, IDE memory usage, and configuration maintenance overhead.

Takeaways

1. 1

   Preventing feature modules from directly depending on each other enables Gradle to build independent modules in parallel across CPU cores.

2. 2

   The modular architecture reduced build times in the Grab Financial Group payments domain so that more than 95% of its 200+ modules build in less than 15 seconds.

3. 3

   Modularisation trade-offs include higher IDE memory usage, increased Gradle sync times, and the ongoing maintenance of separate configuration files per module.