Background

Currently, our feature flag creation UI has different interfaces for boolean flags versus multivariate flags, despite boolean flags essentially being a special case of multivariate flags (with true/false variants). This inconsistency creates unnecessary cognitive load for users who work with both types of flags.

Current Behavior

• Boolean flags have a distinct UI layout
• Multivariate flags have a separate interface for defining variants
• The two interfaces feel disconnected despite serving similar purposes

Proposed Solution

Unify the flag creation interface to treat all flags consistently:

• Present boolean flags as a special case of multivariate flags (with true/false variants)
• Use a consistent layout and interaction pattern for all flag types
• Maintain the simplicity of boolean flag creation while fitting into the multivariate paradigm

Technical Considerations

• May require updates to flag payload/serializer logic to properly detect flag type
• Need to ensure backwards compatibility with existing flag configurations
• Should maintain current functionality while improving UX

Previous Work

• A design proposal was created ~2 years ago addressing this issue (see attached mockup)
• Previous implementation was deprioritized due to resource constraints

Reference

Original discussion