Iterative Mobile Development
summary
Argues teams ship mobile more often by cutting WIP and automating releases: use Fastlane to manage code signing, screenshots and uploads, run tests locally via a pre-commit hook when CI is missing, and run cloud device checks with Firebase Test Lab (Robo crawler) to catch crashes. Use remote config / phased rollouts (example 10% test) and feature flags to flip features without a store release. Cites a 12,000-entry study showing small wins boost team velocity and morale.
AI-written summary · about
chapters (16)
- 0:00Introduction and background
- 2:09One complete thing or three half done
- 4:35Launching the first version
- 7:47Kanban and lean processes
- 13:11Code reviews interrupt work
- 14:59Tools for faster mobile apps
- 21:02Testing and CI best practices
- 23:08Beta testing and phased rollouts
- 25:16Feature flags and remote config
- 27:25Monitoring user behavior
- 28:09The progress principle
- 31:46Small wins and milestones
- 33:11Build measure learn cycle
- 34:54Minimum Viable Product
- 36:38Date-driven vs feature-driven
- 37:41Summary and resources
