Hidden mysteries behind big mobile codebases
summary
Codebase growth causes concrete problems at scale: SoundCloud runs ~150 microservices, two mobile APIs, and Android had ~80M users when a forgotten config pointed traffic to two Mac minis and broke playback. The repo reports ~300 UI, ~1,000 integration and ~5,000 unit tests with flaky UI tests handled by a rotating test sheriff. Teams enforce small PRs, pair 80% of the time, run a 15‑day release train, wrap third‑party libs, use baby‑step refactors and CI so changes are incremental and verifiable.
AI-written summary · about
chapters (10)
- 0:00Start
- 18:10The Test Sheriff
- 24:16Consistency
- 33:53Call Readability
- 37:29Propeller
- 38:03Automation
- 38:53Lessons Learned
- 41:41Core Team
- 49:54Recap
- 53:08Conclusion
related talks
21mSucceed by Failing – A Game Dev’s Journey Into a Mobile Dev Ops Tool Chain
08mAdaptation of the E2E Tests for a Big Project
33mFewer, Smarter, Faster: Scaling Testing @Spotify
38mScaling Automated Testing & Architecture from Startup to Enterprise
52mA Monolith for Hundreds of Client Versions: How We Write and Maintain Tests
21mTEST FOR THE FUTURE
28mManaging App Complexity
52mTesting Microservices