Tell Me Quando - Implementing Feature Flags
summary
Shows a concrete pattern: keep a single codebase and put boolean flags in separate source folders per Gradle build variants (debug/qa/release), implemented as a small FeatureFlags class in each variant. Demonstrates on a simple mood logger app by toggling a new persistence layer using the Realm SDK — Realm code is enabled only in debug, QA/release remain off, and switching variants visibly toggles “new stuff.” Covers Compose/UI routing, testing both flag paths, and cleanup after release.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:00Agenda
- 4:51Put the logic in the code
- 5:28Requirements for the Flag Variables
- 6:59Gradle Trickery
- 7:55Different Variables
- 9:15Different Files
- 10:21Three Common Scenarios
- 19:55Major UI Change
- 22:21What about the tests?
- 22:47Summary
related talks
27mFlag Management Techniques That Support Development of Massive Apps
05m5 Life Hacks Using Feature Management
27mJust Enough Feature Flagging
59mMastering Feature Flags: Best Practices with Firebase Remote Config
15mFeature Flags
26mBuild Progressive Delivery and Safety Into Your Apps with Feature Flags
26mMove Fast and (Don't) Break Things
41mFeature Flags: A Boon or a Brake for a Team