Fathom — Analytics dashboard

Analytics DashboardSee it liveapp.usefathom.com

A dark metric strip anchors a light analytics dashboard with a broad purple trend chart and paired breakdown tables.

Fathom — Analytics dashboard — captured interface — Viewport capture · opening screen

Public demo · 2026-09-05Open full image ↗

Dashboards

Why this pattern works

Web analytics dashboards that need an immediate summary and a clear path into supporting dimensions.

Design notes

Surface: Fathom public Hilarious Platypus analytics demo.
Navigation: Site name and options at the top; date range and comparison controls above the data.
Layout: Summary strip, full-width time series, then side-by-side breakdown tables.
Density: Moderate to high in tables, spacious around headline metrics.
Color: Black metric band, white surface, purple chart and highlights.
Type: Large numeric summaries above compact descriptive labels.
Pattern: Arrange summary, time trend, and breakdowns in the order a reader asks questions.
States: Populated public demo; displayed metrics are example data, not Swipe analytics.
Don't: Do not present demo metrics as evidence of actual business performance.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Fathom — Analytics dashboard
Source: https://app.usefathom.com/demo
Swipefile reference: https://swipefile.design/ref/saas-ui-fathom-analytics-dashboard/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Fathom public Hilarious Platypus analytics demo.
- nav: Site name and options at the top; date range and comparison controls above the data.
- layout: Summary strip, full-width time series, then side-by-side breakdown tables.
- density: Moderate to high in tables, spacious around headline metrics.
- color: Black metric band, white surface, purple chart and highlights.
- typography: Large numeric summaries above compact descriptive labels.
- pattern: Arrange summary, time trend, and breakdowns in the order a reader asks questions.
- states: Populated public demo; displayed metrics are example data, not Swipe analytics.
- dont: Do not present demo metrics as evidence of actual business performance.

Useful for: Web analytics dashboards that need an immediate summary and a clear path into supporting dimensions.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Web analytics dashboards that need an immediate summary and a clear path into supporting dimensions.

Fathom — Analytics dashboard

Make it your own

Keep exploring