Data Explorer

Explore raw product data with filters, saved views, dimensions, and enough context to move from question to evidence quickly. The screen connects Explore and Sources so product analysts can find the “Run query” action while checking rows scanned and queries.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as workspace_id · 98% filled and plan_type · 100% filled, rather than an empty visual shell.

Data Explorer
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Run query

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product analysts need a clear “Run query” action without losing sight of rows scanned, queries and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Run query is clearly available where the task happens.
  • Main view: Explore keeps the starting point obvious.
  • Connected view: Sources supplies nearby context.
  • Metric: Rows scanned is visible with a meaningful value.
  • Another signal: Queries helps people judge what to do next.
  • Representative record: workspace_id · 98% filled makes the example specific.
  • Second record: plan_type · 100% filled shows the pattern works beyond one item.

States worth designing

  • No data for the chosen period; show what people can do instead of leaving a blank panel.
  • Loading explore without changing the layout unexpectedly.
  • Partial or delayed metrics; explain the problem and preserve work.
  • Permission denied for sources; clarify who can continue.
  • Success after choosing Run query; 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

Explore → Sources → Run query → Review outcome

Patterns used

Analytics, Explore, Sources, Queries, accessible states, contextual actions

Why these choices work

Make time ranges, filters and metric units clear. Show the data behind each trend so readers can test what changed.

In this design, people should be able to compare workspace_id · 98% filled with plan_type · 100% filled. Make rows scanned clear, then use queries 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 “Run query” action. The happy path alone is not enough.

Related UI examples: Reporting Builder, Metrics Catalog, Experimentation.

Start from this in Figr

Design a data explorer screen for our existing software product. Use our real design-system tokens, components and product language. Show Explore and Sources, include believable records such as workspace_id · 98% filled, and make run query easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr