FlagFix
Feature management

Feature flag best practices

Short-lived gates, server keys, and explicit exposures.

Cette page n’a pas encore de traduction française. Le texte anglais fait foi.

Last updated on

  • Keep one key per behavior. Do not overload a boolean with several meanings.
  • Evaluate server-only decisions with @flagfix/node and a SERVER_SDK key.
  • Ship the CLIENT_SDK key only if the flag values are safe to expose.
  • Call trackExposure at the point of display, not inside hasFeature.
  • Publish the kill switch before you need it. A draft does nothing for SDKs.
  • Roll out with a salt you can rotate if a bucket looks skewed. Rotation reassigns users.
  • Remove the flag from code after the rollout is finished. The platform will not delete the call sites for you.

Cette page vous a-t-elle été utile ?

Offline behavior

Last snapshot for flags. Durable queue for events.

Events

Send product events from your applications and keep their names consistent.