Feature Flags

Manage rollout rules, environments, segments, owners, and stale flags with current exposure and risk easy to scan. The screen connects Flags and Segments so platform and engineering teams can find the “New flag” action while checking active flags and stale.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as new-onboarding · 80% and search-v2 · 25%, rather than an empty visual shell.

Feature Flags
Use this template in Figr

Template facts

Screen

Workspace

Primary action

New flag

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Platform and engineering teams need a clear “New flag” action without losing sight of active flags, stale and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: New flag is clearly available where the task happens.
  • Main view: Flags keeps the starting point obvious.
  • Connected view: Segments supplies nearby context.
  • Metric: Active flags is visible with a meaningful value.
  • Another signal: Stale helps people judge what to do next.
  • Representative record: new-onboarding · 80% makes the example specific.
  • Second record: search-v2 · 25% shows the pattern works beyond one item.

States worth designing

  • First-use workspace; show what people can do instead of leaving a blank panel.
  • Loading flags without changing the layout unexpectedly.
  • Unavailable or restricted panel; explain the problem and preserve work.
  • Permission denied for segments; clarify who can continue.
  • Success after choosing New flag; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Flags → Segments → New flag → Review outcome

Patterns used

Workspace, Flags, Segments, Environments, accessible states, contextual actions

Why these choices work

Keep the main job visible above supporting panels. Group related controls and surface exceptions where people act.

In this design, people should be able to compare new-onboarding · 80% with search-v2 · 25%. Make active flags clear, then use stale to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “New flag” action. The happy path alone is not enough.

Related UI examples: Logs Explorer, Model Playground, Deployment Console.

Start from this in Figr

Design a feature flags screen for our existing software product. Use our real design-system tokens, components and product language. Show Flags and Segments, include believable records such as new-onboarding · 80%, and make new flag easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr