Toggle your app
summary
Large classifieds Android app with 20+ Android developers adopts feature toggles to avoid big long-lived branches, letting teams merge working code disabled by default and flip features later. Built a toggle system with metadata, a debug UI for testers, Jira integration and automation that marks features in builds; backend reads active flags via headers. Testing covers on/off cases and unit/isolation strategies; result is fewer blocking regressions and a goal to cut release cycles from months toward 1–2 weeks.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 5:49Big team challenges
- 7:56Feature toggles concept
- 9:25Implementing and disabling toggles
- 12:39Toggle management
- 14:51Toggle deployment methods
- 17:50User-facing feature enablement
- 22:52Testing with toggles
- 30:32Continuous delivery and flexibility
- 33:45Jira integration
- 40:24Feature release timing
- 44:53Removing toggles
- 47:05Gradual feature rollout
- 48:56Testing phases
- 50:19Risks and outcomes
related talks
30mFeature toggles: ask us anything
44mFeature Toggles: The Good, The Bad, and The Ugly
07mScaling with LaunchDarkly: A feature toggle story!
27mFlag Management Techniques That Support Development of Massive Apps
25mReleasing apps faster with feature flags
30mChoose Your Own Deployment: Interactive Feature Flag Adventure
50mFunctional Feature Flags
40mScaling Android Apps