Building Scalable Mobile Projects: Fast Builds, High Reusability and Clear Ownership
summary
Targets concrete limits: sub 10s local builds, <100s internal and <1,000s production, achieved by modularization into API/lib/bindings modules, aggressive compilation avoidance and caching, and sizing compilation units to reduce critical path. A monorepo groups foundation/platform/components/apps so libs depend only on stable APIs, enabling easy feature reuse by a single dependency line. Ownership lives in an executable monorepo owners file that generates GitHub CODEOWNERS and survives refactors, not vague layer-by-layer promises.
AI-written summary · about
chapters (12)
- 0:00Intro
- 3:36Why Mobile
- 5:22Prioritization
- 13:30Build System
- 14:16Modern Build System
- 23:43Code locality principle
- 24:52Categories
- 26:49Modules
- 28:36Platform
- 34:30Reusability
- 36:18GitHub
- 40:56Conclusion
related talks
48mMobile Developer Productivity at Scale
24mBuilding your ideal codebase: monorepos & multirepos living in harmony
33mTools of the Trade
49mScalable Best Practices for Your Development Team
24mMobile Development
11mPerformant Bazel Builds for Web Monorepos at Scale
20mBuilding with Monorepos
29mModularity and Monorepositories