Scaling with LaunchDarkly: A feature toggle story!
summary
Product starts with 6–8 week release cycles, repeated hotfixes and two production incidents (one crash on iOS, one huge merge conflict) that force a change. Team builds a local debug toggle to hide risky code, migrates toggles to a server, and adopts LaunchDarkly for feature flags. Implementation supports targeted cohort rollouts and progressive exposure across mobile, web and backend; the flag system replaces big-bang releases and enables global scaling of product and teams.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:29Agenda
- 0:48Introductions
- 1:11About me
- 2:12What is Tide
- 3:52Why Tide
- 4:31Release schedule
- 5:03Incidents
- 6:43Conclusion
related talks
02mA Message From LaunchDarkly
59mFaster & less risky releases with feature flags
25mGo Faster, Be Safer
54mFeature Flags Separate Deployment from Feature Release
18mKeynote: Safe at any Speed - How Progressive Delivery Eliminates Risk
01h 09mFeature flags: the toggle, the A/B test and the canary
30mChoose Your Own Deployment: Interactive Feature Flag Adventure
27mScaling your mobile app release process