You know what they say... there are 2 hard things in computer science: cache invalidation, naming things and off-by-1 errors. That's true for feature flags...
A few weeks ago I switched Box Out and Flipper Cloud to AppSignal. I've been loving it so far! The only snag I hit was cost for Cloud (not for Box Out)....
Releasing code behind feature flags when much of the related functionality is incomplete can sometimes require creative solutions. For example, if some new...
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.
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.
The use of feature flags for development and release process can provide multiple benefits that reduce risk related to new functionality or large releases.
Despite carefully planning for some recent feature flag removals and triple-checking that the relevant flags were no longer present on our main branch, I still screwed it up.
Did you know you can use Flipper to create and manage feature flags for your client-side app, even though Flipper is a Ruby gem and doesn't have client...
We recently had some healthy debate about a potential new view in Flipper Cloud. The debate's not fully settled, but thanks to feature flags, we were all...
