Release Android apps globally with no headache and minimum stress
summary
Company ships Android every 1.5–2 weeks, handles ~25% of transactions on mobile, and runs Firebase Test Lab + espresso UI tests on three physical devices before merge; QA team moves from manual clicks to writing and owning those tests. Deployment uses staged percentages (5,10,20,50,100) and remote stage rollout + feature flags (compile-time and runtime, per country/percentage) so broken features can be turned off instantly. Real incident: a sync-loop from mobile caused a massive backend overload until a backend throttling workaround dropped 9 of 10 calls.
AI-written summary · about
chapters (9)
- 0:00Start
- 9:50Automation
- 10:19Firebase Desktop
- 12:52The Firebase Tesla
- 18:24Mock Environment
- 20:36Staged Rollout
- 25:54How Much Time Does It Take To Ship a Feature
- 26:48Long-Running Feature Branches
- 33:45Conclusions
related talks
38mFrom Development to Production: Tips to Optimise Android App Deployments
41mBuilding Mobile Apps At Scale
24mFuture-proofing your Android release process
41mMobile DevOps
21mStreamlining Android app development and release processes
33mReleasing and monitoring your Android app with Firebase
37mTackling Android Development at Scale
22mFrom Chaos to Control: Future-Proofing Your Android Release Process