Flag Management Techniques That Support Development of Massive Apps
summary
Describes using feature flags instead of long-lived branches to reduce merge conflicts, allow merging to main independent of release timing, and enable rollbacks by toggling flags. Presents a Gradle plugin that reads properties to generate BuildConfig boolean flags (with a map for build-variant/version values), handles ProGuard/static finals, and can generate runtime-writable debug getters/setters; notes flags are unsuitable for API/SDK changes and still require small PRs and strict review to track flags.
AI-written summary · about
chapters (13)
- 0:00Feature flag management
- 1:04Merge conflicts in branches
- 5:10Flags solve conflicts
- 7:26Release vs dev schedules
- 9:40Incremental feature sharing
- 10:54Gradle flag plugins
- 13:56ProGuard with flags
- 15:26Build variants control
- 18:04Runtime flag modification
- 22:04Flag limitations
- 24:49Testing flagged features
- 25:34Summary
- 27:06Q&A
related talks
25mTell Me Quando - Implementing Feature Flags
50mFunctional Feature Flags
41mFeature Flags: A Boon or a Brake for a Team
05m5 Life Hacks Using Feature Management
15mFeature Flags
41mFeature Flags: Separate Deployment from Feature Release
59mMastering Feature Flags: Best Practices with Firebase Remote Config
26mBuild Progressive Delivery and Safety Into Your Apps with Feature Flags