What they don’t tell you about feature toggles
summary
Defines three practical flag types — client, product, and technical — and gives concrete rules: use client flags only during development, swap them for technical flags for rollouts, then delete; product flags live long and are shared across clients. Recommends Firebase remote config for technical rollouts, warns of a default 12 hours cache TTL that can keep bad configs active, notes unseen complexity as permutations grow (2^n), and cites a 60-person mobile team (60 mobile engineers) as the scale where stale flags and large responses become real problems.
AI-written summary · about
chapters (6)
- 0:00Introduction and speaker intro
- 1:05What are feature flags
- 3:50Three types of feature flags
- 7:40Common pitfalls with flags
- 10:31Best practices for managing flags
- 12:37Implementation tips and summary
related talks
59mMastering Feature Flags: Best Practices with Firebase Remote Config
44mFeature Toggles: The Good, The Bad, and The Ugly
27mFeature Toggles
27mFlag Management Techniques That Support Development of Massive Apps
50mThe Story of One Feature Flag
15mFeature Flags
05m5 Life Hacks Using Feature Management
25mTell Me Quando - Implementing Feature Flags