Ensuring quality throughout the application lifecycle
summary
Large Flutter apps avoid rollbacks so quality combines heavy dev-side checks and measured production validation: use flutter_lints and lint package plus custom_lint and analyzer plugins, run unit/widget/golden tests and maestro for end-to-end flows, automate uploads for 30+ store artifacts, require manual PR previewing plus CI and AI review, deploy staged rollouts at 1% then 2% increments, gate risky features behind flags and A/B tests, target 99% crash-free sessions and enforce a six-version rolling window with force updates.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:26Defining quality
- 2:50Shift left vs shift right
- 3:55Mobile QA challenges
- 4:36Benefits of shift left
- 5:38Linting and code metrics
- 7:05Mobile automated testing
- 7:47Code review and AI checks
- 8:50Automating app store uploads
- 9:53Release strategies
- 10:57Feature flags and A/B testing
- 12:49Analytics and error monitoring
- 13:31Hotfixes with Sherbet
- 14:12Rolling release windows
- 15:40Conclusion
related talks
20mCode Quality Gates for Large-Scale Flutter Apps
41mThe art of Flutter testing
36mSecuring Flutter Apps
45mFlutter: A journey of productivity and happiness
36mObservation-based product development using Flutter 1
30mCat-like Development: Flutter for Efficiency
51mAll About Testing Flutter
42mOur Journey to Flutter