How to ship apps better, faster, stronger
summary
Concrete practices and outcomes: adopt release trains with an ideal one‑week cadence so main is always shippable; put every feature behind feature flags and fetch flags on startup to avoid A/B synchronization errors; automate releases (Fastlane or equivalents) and CI so no human bottleneck; monitor staged rollouts and business metrics (Crashlytics or Sentry, Statsig/LaunchDarkly or open source Flagger) to catch regressions. Real-world results: teams hit weekly delivery, fewer hotfixes, and startups like Maven Clinic approach “release nirvana.”
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:08How to ship apps
- 4:11Ship when feature is ready
- 8:05A B Test
- 9:57What to do
- 10:55Continuous Delivery
- 15:26Benefits
- 18:02Examples
- 18:29Maven Clinic
- 19:23Branching
- 19:34Release Candidate
- 20:57Automate
- 22:40Monitoring
- 25:18Statsig
- 26:16Best practices
related talks
44mTales of a Mobile DevOps
38mBuilding a high quality product
44mRelease Early, Often, Stable
40mAvoiding release paralysis
38mFrom Development to Production: Tips to Optimise Android App Deployments
41mContinuous delivery in 10 easy mistakes
01h 28mThe fantastic four coding patterns of Continuous Delivery
54mGetting out of quicksand, with DevOps!