From Development to Production: Tips to Optimise Android App Deployments
summary
Claims a team shrinks release cadence from two months to two weeks by building a mobile CI/CD pipeline on Bitrise CI/CD, caching dependencies (push/pull S3 cache) to cut build time, running UI tests on Firebase Test Lab to catch flakiness, and automating Play Store uploads with Fastlane to publish to Google Play Store. The pipeline signs APKs, stages rollouts behind feature flags, and succeeds at catching regressions earlier so releases ship faster and with fewer live crashes.
AI-written summary · about
chapters (21)
- 0:00Start
- 0:11MAIN SPONSOR
- 1:22The Problems
- 6:35Optimization?
- 10:43Mobile DevOps as a Service
- 17:51The advantages of Mobile DevOps
- 19:58Cache app dependencies
- 21:09UI Automated Testing
- 23:44Automate Deployment
- 24:29Automated Tasks
- 25:42Deploy features under Feature Flags/Toggles
- 26:49The Mobile Release Train
- 29:27Implementation Guide
- 30:32Firebase Crashlytics
- 31:05Move to Cloud & Mobile-focused CI/CD
- 31:54No hardware to maintain
- 32:59Release Lifecycle
- 33:21Android CI/CD Pipeline
- 35:50Run builds in parallel on multiple VMs
- 36:18Build Platform Team
- 37:12Lessons learned
related talks
57mThe Road to Mobile DevOps for Android
42mFrom Development to Production
21mDo more faster - Taking your Mobile DevOps setup to the next level
25mMobile DevOps - How CI/CD can change your development world
21mStreamlining Android app development and release processes
30mCI Recipes and Release Flow Strategies for Medium and Larger Apps
41mHow Are Other Teams Doing It? Lessons in CI/CD from 3500 Android Teams
32mBuilding Quality Android Apps for the Future with Continuous Integration