FIGR / UI TEMPLATE

Live Ops Dashboard

Operate a live game with player activity, retention, monetization, incidents, experiments, events, segments, content rollouts, and real-time health.

This analytics reference covers gaming. Its sample screen includes Season event performance and Store conversion and the Launch event action. Adapt its workflow to your product and design system.

Live Ops Dashboard

BUILD ON THIS

Make it yours in Figr.

Explore this screen, then bring in your own product and design system to shape the next version.

Use this template ↗

At a glance

Screen

Analytics

Primary action

Launch event

Pattern

Live Ops Dashboard analytics

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps with

The live ops dashboard screen supports “Launch event” while keeping health and events in view. It should show the current state even when data is missing or access is restricted.

What to look for

  • Primary action: Launch event
  • Main area: Health brings the user to the relevant workflow
  • Related area: Events keeps nearby context accessible
  • DAU: 2.8M in the sample screen
  • D1 retention: 42% in the sample screen
  • Example 1: Season event performance
  • Example 2: Store conversion
  • Input: Environment

States to consider

  • Default: Show the main workflow and its available next step
  • Loading: Keep chart labels and time range visible while metrics refresh
  • Empty: Explain the chosen date range or filter has no data
  • Error: Identify missing or stale metric sources without implying zero activity
  • Access: Show which actions require a role or permission
  • Success: Confirm the result after Launch event and say what happens next

Where it fits

Health → Events → Launch event → Review result

Patterns in this screen

Live Ops Dashboard analytics, Health, Events, permission handling, error recovery

UX choices to review

Keep metric definitions, chart periods, and filter context visible together

In this example, Season event performance is one of the records worth checking. Keep the sample data clearly separate from a live system.

Show why numbers changed; distinguish delayed data from genuine zero values

Make a useful drill-down available before teams export or share findings

Try a similar screen in Figr

Design a live ops dashboard screen for an existing gaming product. Use our actual design system, components, and content rules. Cover Health and Events, include believable records such as Season event performance, and make "Launch event" easy to find. Map empty, loading, error, permission, and success states. Keep the result editable in Figma.

Open Figr

KEEP EXPLORING

More ways to approach your next screen.

Browse other product UI examples, compare patterns, and pick the direction that suits your product.

Explore all 500 templates ↗