CI Recipes and Release Flow Strategies for Medium and Larger Apps
summary
Team develops medium-to-large Android apps with a 3–5 engineer cadence and biweekly releases using GitFlow branches (master/develop/feature/release/hotfix) and PR-based CI to reduce human error. CI is run on Bitrise with workflows to build, sign, deploy to staging, and tag releases; tags trigger production uploads. An internal Ktor service calls the Google Play Developer API to automate staged rollouts (gradually increasing user fraction to 100%) and posts Slack notifications, while Crashlytics-driven automated rollback is avoided due to API limits.
AI-written summary · about
chapters (6)
related talks
38mFrom Development to Production: Tips to Optimise Android App Deployments
57mThe Road to Mobile DevOps for Android
41mHow Are Other Teams Doing It? Lessons in CI/CD from 3500 Android Teams
24mLessons in CI_CD from 3500 Android Teams
40mAutomate The Small Things
43mSecret Sauce of Cross-platform Mobile App Continuous Delivery
32mBuilding Quality Android Apps for the Future with Continuous Integration
31mDude, Where's My Build? Android CI/CD