The Road to Mobile DevOps for Android
summary
Argues that moving from manual, bimonthly releases to a weekly or biweekly mobile release train requires a gated CI/CD pipeline, test automation as a hard gate, and continuous monitoring. Shows a concrete Bitrise workflow that builds APKs, runs Espresso tests on Firebase Test Lab, uploads artifacts to App Center, signs and deploys with Fastlane, and blocks rollout on failed steps; recommends feature flags, staged rollouts, and a tracing SDK for crash/metric monitoring. Bitrise is used as the CI platform.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:13Problems
- 6:20Mobile DevOps
- 10:57Mobile DevOps Adoption
- 14:03Advantages of Mobile DevOps
- 15:31Mobile Release Terrain
- 18:13Mobile Release Train
- 20:46Implementation Guide
- 23:23Bitrise
- 29:14The workflow
- 32:55Fastlane
- 33:19What is Fastlane
- 34:23Fastlane steps
- 34:47Fastlane example
- 36:32Monitoring
- 37:51Lesson Learned
- 40:05Demo
- 43:31Triggers
- 49:20QA
related talks
38mFrom Development to Production: Tips to Optimise Android App Deployments
25mMobile DevOps - How CI/CD can change your development world
21mDo more faster - Taking your Mobile DevOps setup to the next level
31mTales of a Mobile DevOps
28mFrom Ooops to Mobile DevOps: 7 Steps for Successful Mobile DevOps Transformation
32mBuilding Quality Android Apps for the Future with Continuous Integration
47mMobile DevOps - Deliver great apps continuously
26mContinuous Everything in Mobile