Dashboard Overview
The screen an app opens on: shell, header, KPI row, chart and activity feed — numbers first, shape second, changes last.
The saved view and the comparison window first, because every figure below depends on both — then six charts, none of which load a charting library.
app/analytics-page.tsxnpx hoverlab add analytics-page
Or over MCP, from your editor's agent — no account needed.
Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.
The window and the comparison first, because every figure below them depends on both.
One filter has been added to this view: Enterprise only
All open is shared with your team. Saving changes what everyone sees, including tomorrow's scheduled digest.
Every percentage on this dashboard is measured against the comparison window below.
Both windows are inclusive of their end dates and computed in UTC, so a change of clocks never produces a week of six days and 23 hours.
This month
Every figure names what it is being compared against. A delta with no stated period is the most common way a dashboard misleads the people who built it.
+7.2% on the previous 30 days, not on last calendar month.
Trailing twelve months, expansion minus churn and contraction.
Same period, all regions. p50 is 96 ms and hides this.
Degraded, not down. Public status page has the detail.
Requests
Trend over the last 12 periods, rising 18.2 percent.
Error rate
Trend over the last 12 periods, falling 34.5 percent.
p95 latency
Trend over the last 12 periods, falling 8.1 percent.
Compared with the same month last year.
| Month | This year | Last year |
|---|---|---|
| Jan | 3,120 | 2,980 |
| Feb | 3,260 | 3,010 |
| Mar | 3,180 | 3,090 |
| Apr | 3,540 | 3,120 |
| May | 3,720 | 3,050 |
| Jun | 3,610 | 3,210 |
| Jul | 3,880 | 3,180 |
| Aug | 4,020 | 3,340 |
| Sep | 3,960 | 3,290 |
| Oct | 4,180 | 3,410 |
| Nov | 4,320 | 3,380 |
| Dec | 4,410 | 3,520 |
Billing period to date, across every project in the workspace.
Last 30 days
End to end 5.5%
100.0% of the funnel
12,205 did not continue · 33.7% of everyone who started
1,227 did not continue · 27.1% of everyone who started · Link expires after 24 hours
3,886 did not continue · 6.0% of everyone who started
Biggest drop in the funnel — 77.9% of the previous step stops here
88 did not continue · 5.5% of everyone who started
Counted as a cohort: every person here entered at the first step inside the window and is followed through in order. Someone who signed up last month and paid this month is not in these numbers, so this reads lower than a per-step total over the same period — and it is the one that answers “what happens to the people we get”.
1,453 deploys across 306 active days in the last year
| Month | deploys |
|---|---|
| Sep 2025 | 72 |
| Oct 2025 | 90 |
| Nov 2025 | 87 |
| Dec 2025 | 109 |
| Jan 2026 | 111 |
| Feb 2026 | 69 |
| Mar 2026 | 132 |
| Apr 2026 | 146 |
| May 2026 | 148 |
| Jun 2026 | 157 |
| Jul 2026 | 170 |
| Aug 2026 | 162 |
The real page, rendered in your current theme — every section below is a live block, not a screenshot.
Only want one section? Open it and copy that block instead — browse Dashboards.
/**
* The analytics screen, arranged so the controls that change every number
* on it come before the numbers.
*
* `dashboard-overview` is the glanceable version — cards, a feed, a header.
* This is the one someone actually works in, and the difference is entirely
* about the two controls at the top.
*
* <DashboardSavedViews> and <DashboardComparisonPeriod> are first because
* every chart below them is meaningless without knowing which window is
* being shown and what it is being compared against. A dashboard that puts
* its date picker in a corner produces a specific, repeatable mistake:
* someone reads a 40% rise, screenshots it, and finds out later they were
* comparing four weeks against three.
*
* Then the numbers, in decreasing altitude:
*
* kpi band the four figures the meeting is about
* sparklines the same figures with their direction
* line chart one metric over a year, with the axis printed
* donut where a single total went
* funnel where people fell out, led by the step-to-step rate
* heatmap a year of days, so seasonality is visible at all
*
* The funnel is deliberately after the donut even though both are
* breakdowns. A donut answers "of the whole, how much"; a funnel answers
* "between two steps, how many survived", and the second question only
* makes sense once someone has the total in their head.
*
* Nothing here loads a charting library. Every chart on this page is inline
* SVG or a conic gradient, which is the reason a page with six of them is
* still a page and not a bundle.
*/
import * as React from 'react'
import { DashboardSavedViews } from '@/components/dashboard-saved-views'
import { DashboardComparisonPeriod } from '@/components/dashboard-comparison-period'
import { KpiSummaryBand } from '@/components/kpi-summary-band'
import { MetricSparklineCards } from '@/components/metric-sparkline-cards'
import { LineChartPanel } from '@/components/line-chart-panel'
import { DonutBreakdown } from '@/components/donut-breakdown'
import { FunnelConversionPanel } from '@/components/funnel-conversion-panel'
import { ActivityHeatmap } from '@/components/activity-heatmap'
export default function AnalyticsPage() {
return (
<main className="min-h-screen bg-background text-foreground">
<section className="mx-auto w-full max-w-6xl px-6 pb-2 pt-12">
<h1 className="text-2xl font-bold tracking-tight">Analytics</h1>
<p className="mt-1 text-sm text-muted-foreground">
The window and the comparison first, because every figure below
them depends on both.
</p>
</section>
<DashboardSavedViews />
<DashboardComparisonPeriod />
<KpiSummaryBand />
<MetricSparklineCards />
<LineChartPanel />
<DonutBreakdown />
<FunnelConversionPanel />
<ActivityHeatmap />
</main>
)
}
components/ — each block page has its own copy button.app/analytics-page.tsx. The imports already point at @/components/…, so they resolve with no edits.The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.
The screen an app opens on: shell, header, KPI row, chart and activity feed — numbers first, shape second, changes last.
An agent working inside a real app: a transcript down the middle — reasoning, answer, then the one card that can act — with what it may read and what it noticed demoted to a rail.
A kanban board inside the app shell, with tabs that admit the board is one view among several and a header whose primary action is creating work.
The canonical CRUD list — header, toolbar, sortable table and pagination framed as one panel instead of three stacked cards.
A wizard for the session someone finishes and a checklist for the one they do not, with the only genuinely blocking step in front of both.
Built around the state a search page is in most of the time — empty — so recent queries lead and the facets sit in a sidebar that survives growing to twelve.
One run opened up in the order you would debug it — intent, actions, the retries that are invisible in both, then cost.
The queue, the same queue sorted by how long things have waited, and the policy that decided both — with the policy last so it is not scrolled past forever.
The blank thread answered with real starter prompts, the model picker with the three numbers the choice turns on, and the four surfaces a session grows into — attachments, branches, canvas, threads.
The three states an agent screen usually omits: the wait before the first token, the trace after something broke with retries costed in the open, and the diff it wants a person to accept.
Why the answer said what it said: what is connected, how stale it is, what the query was allowed to see, what fitted in the window and what fell out — plus the failed-search state a debugging tool is most needed in.
Five ways to reach a model without the cursor leaving the sentence — slash menu, inline completion, selection toolbar, action menu, property inspector — and the two surfaces that say where the answer came from.
A table after real people have used it — columns reordered from the keyboard, a selection bar that asks page-or-all, subtotals that survive collapsing, cells edited in place, and the empty state its own filters produced.
Thresholds with how often each has actually fired, what that produced, where it went — and the digest settings that exist because of the answer.
The flow between an empty product and a useful one, in the order it goes wrong: sample data offered with equal weight, a file, a URL, the column mapping everything stalls on, and an upload that survives the connection dropping.
A profile form where the role options state what they actually change, the avatar crop works from the keyboard, and a navigation guard names the fields it is about to throw away.
The furniture that is on every screen and belongs to none — navbar, mobile drawer, command palette, shortcut sheet, header search, scope switcher, and the two shapes a detail view takes without losing the list.
Backwards from now and forwards from it on one screen — a day-grouped timeline, a month grid where a busy Tuesday never changes the row height, and the state both are in on day one.
What the product looks like while onboarding happens: a tour step anchored to the control it explains, the skeletons of the slowest load it will ever do, and the checklist that outlives both.