Iterative Mobile Development
summary
Argues that mobile teams can ship iteratively despite app store overhead by combining process and automation: use Kanban/lean, limit work‑in‑progress, run weekly retros, and line the whole team on one feature to get usable increments sooner. Concrete tools and practices include Fastlane for fully automated beta/prod releases, Firebase Remote Config to flip behavior for 10% of users, device runs on Test Lab, CI plus pre‑commit hooks that run iOS tests only when iOS code changes in a mono‑repo, and staged rollouts to catch regressions before full release.
AI-written summary · about
chapters (34)
- 0:00Intro
- 0:20Andreas Journey
- 1:42Question
- 2:04This isnt how teams are set up
- 2:40The goal of my talk today
- 3:25The circle diagram
- 4:41Getting to v1
- 5:12Its so far away from you
- 7:16Kanban Lean
- 11:20Parallelizable Features
- 12:22Tools
- 13:25Release Automation
- 13:50Fastlane
- 14:47Configuration
- 15:26Testing
- 15:37Running Tests
- 17:24Test Lab
- 18:16Robo Crawler
- 18:42Beta Testing
- 20:03Remote Config
- 20:34Remote Config Example
- 20:51Analytics
- 21:54Crash Reporting
- 22:24The Progress Principle
- 23:35The Power of Small Wins
- 24:16Milestones
- 25:14Customer
- 25:40Build Measure Learn Cycle
- 26:13Measure Quality
- 26:31Usability Beta Testing
- 26:44Metrics
- 27:06Minimum Viable Product
- 28:44Software Launches
- 29:38Conclusion
related talks
38mIterative Mobile Development
36mIterative Mobile Development
17mStreamlining Mobile Releases
31mTales of a Mobile DevOps
40mBuilding predictable and high performance workflows for mobile app development
51mDon't Kill Agility with Agile Processes
33mSoftware development practices for companies that want to make an impact
23mAchieving Weekly Releases: A Technical Deep Dive into Our Development Process