Automate Flutter app releases using Fastlane and Bitrise
summary
Seven-engineer team ships a Flutter merchant app every two weeks, using a numbered version scheme like 23.13 and an eight-step release process (code freeze, UAT, production rollout, tag/merge). CI/CD runs on Bitrise with a stored bitrise.yml per branch so teams can test different Flutter versions; distribution and signing use Fastlane sync certificates and Play/App Store lanes. Automation covers roughly 50-70% automation, with manual QA, Sentry monitoring, and staged rollouts still required.
AI-written summary · about
chapters (9)
- 0:00Introduction and welcome
- 2:53Audience experience with tools
- 4:38Team structure and releases
- 8:31Release process overview
- 13:26What is Bitrise
- 16:55Fastlane for code signing
- 20:26Fastlane community benefits
- 21:10Automation limits and team size
- 22:14Conclusion and team recognition
related talks
46mAutomating with fastlane Tips, Tricks, and Best Practices
24mAutomate your React Native world with fastlane
57mThe Road to Mobile DevOps for Android
21mFastlane: Automate Deployment of Your Mobile Apps to the St…
46mAutomatic Deployment of iOS and/or Android Apps
30mScale-up iOS Automated UI Tests
24mMobile development process automation
21mDo more faster - Taking your Mobile DevOps setup to the next level