Modularizing Android Applications
summary
Argues that splitting a monolithic app into focused libraries improves architecture and incremental compile times but warns about a dependency rabbit hole and higher maintenance. Describes concrete moves: extract an API client into a library, convert app to a small base module wrapper, keep everything in a mono‑repo, and use Gradle 4.7 features and API vs implementation visibility to hide internals. Shows sample apps, per‑module tests, and Dagger wiring across modules, and reports that parallel compilation and smaller incremental builds often speed iteration.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:53Motivations
- 3:38Disclaimer
- 4:20File Hierarchy
- 5:11Application Module
- 5:30Single Module Application
- 5:44Single Project
- 5:58Monolith
- 7:04Microservices
- 8:05Book Stack
- 8:28Modular Approach
- 11:36Gradle File
- 12:31Module
- 13:45File Structure
- 16:03Java Library
- 18:12Login
- 19:39User Classes
- 20:19Be Cautious
- 21:21A Different Approach
- 27:07Gradle Updates
- 37:18Navigation
- 37:29Content
- 38:11Wrap Up
