Feature flags are one of those things where once they click, you see opportunities for them everywhere. From managing development or analytics tools across environments to things like protecting registration or contact forms, they come in handy in endless ways. While nobody ever wants to take a registration or contact…
Releasing code behind feature flags when much of the related functionality is incomplete can sometimes require creative solutions. For example, if some new functionality requires a new column with a default value, how can we handle the scenario where the database’s default value should be different after the future…
With Flipper's new telemetry, we can see when a flag hasn't been requested in production (or any environment for that matter) for a long enough window that it's safe to remove. That creates a lot of peace of mind when cleaning up stale flags.…
Flipper is sporting a snazzy new CLI and some testing improvements, among a handful of small improvements.…
While feature flags are great for managing the roll out of customer-facing features, they're capable of so much more. We use feature flags internally in conjunction with performance and analytics tools.…
Adding feature flags is easy but deleting them requires care and safety. We even mess it up. Before you delete a flag, you have to remove it from the code. If you don't remove it from the code, deleting a flag is the same as disabling it.…
Traditional web analytics aren't always the most useful for web apps, where a single controller with a dynamic route can serve an infinite number of different URLs. For example, /organization/fewer-and-faster and /organizations/boxout-sports are really the same page, but they show up in analytics as two separate…
We're working on a ton of exciting stuff at Flipper, and we've been releasing updates at a feverish pace. Now we're getting close to releasing a wholly underwhelming and truly boring feature that will play a key role in Flipper's overall user…