Modular Android Development
summary
Claim: migrating a monolithic Android app into Gradle modules at Babbel reduces team coupling but costs configuration and initial slow builds. Implementation: single Git repo with centralized Gradle config, modules as Android/Java libraries, Dagger 2 components exposed via module interfaces and a command pattern for cross‑module calls, JaCoCo + Codecov enforcing coverage thresholds on CI (Bitrise), FindBugs and Android lint templates. Results: migration takes months, build+test used to be 12–14 minutes and drops to seconds with Instant Run, yields team ownership, sandbox demos and easy feature removal.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:30What Is Modular Why Modular
- 3:47Overview
- 5:23Application Build Gradle File
- 7:55Applying the Command Pattern
- 13:37Code Coverage
- 15:54Retire Jenkins
- 19:10The Build Times
- 19:36Configuration Overhead
- 21:32Sandbox Environments
- 24:59Dynamic Code Loading
- 26:49How Do You Deal with Pull Requests
