Product analytics: Signal Pro
Signal is ink-coloured so the charts carry the colour. It's built like a product people pay for:
- Workspace switcher at the top of the sidebar (Northwind on Pro, Acme Labs on Business, a free sandbox), Favorites for starred reports, a count on the board, a dot on Reports and a New tag on Copilot.
- ⌘K command palette: every screen with its G then letter shortcut, actions (New report, Ask Copilot, Invite teammates, Export), Switch workspace… as a page, and reports and people from a simulated server as you type, with a spinner and skeletons while it answers.
- Notification inbox in the top bar: mentions, invites with Accept and Decline, AI findings, billing and incident notices over the past week, grouped by day; swipe or hover to read, snooze or archive. A new mention arrives a few seconds in, so you see the count pop.
- Usage card above the user: 8.4M of 10M events, amber past 80%, with Upgrade going to Billing.
- A resizable sidebar on the web, a rail with a full drawer on tablets, and tabs with More (or
phoneNav="drawer") on phones.
Use the whole app
import { SaasApp } from '@patine-ui/pro';
<SaasApp />;
| Prop | Type | Default |
|---|---|---|
initialRoute | 'overview' | 'funnels' | 'audience' | 'reports' | 'copilot' | 'roadmap' | 'board' | 'status' | 'billing' | 'overview' |
demo | 'ready' | 'loading' | 'empty' | 'error' | 'ready' |
insets | { top, bottom } | None |
platform | 'ios' | 'android' | 'web' | Platform.OS |
phoneNav | 'tabs' | 'drawer' | 'tabs' |
onColorSchemeChange | (scheme: 'light' | 'dark' | 'system') => void: adds Change theme… to the palette | |
liveNotifications | boolean: a notification arrives a few seconds in | true |
Screens move the platform's way: on iOS a pushed screen slides in from the trailing edge, on Android they fade through, on the web and between tabs they fade in. Reduce motion turns it off.
Screens
| Screen | What it does |
|---|---|
AnalyticsOverviewScreen | StatsRow, a ComboChart with a second axis, a FunnelChart and the ActivityFeed |
FunnelsScreen | A FunnelChart by step, the biggest drop called out, channels in a sortable Table |
AudienceScreen | A bubble ScatterChart with a trend, a PieChart, a RadarChart and a HeatmapChart |
ReportsScreen | Pro's TreeView of folders, Breadcrumbs, a DataTable that becomes cards on phones, Pagination |
CopilotScreen | Pro's Chat with tool calls and reasoning, AgentActivity and AIUsageMeter |
RoadmapScreen | Pro's Gantt with dependencies and a milestone |
BoardScreen | Pro's Kanban with a WIP limit and Move to… |
StatusScreen | StatusTracker per service, a latency GaugeChart, incidents on a Timeline |
SaasBillingScreen | Usage by source, PricingTable with monthly and yearly, invoices |
Every screen is exported on its own, takes its data as props, and has sample data as defaults. biggestDrop(stages) finds the funnel step that loses the most; pageOf and filterReports drive the reports table.
Built with
The free components, from patine-ui:
Avatar · Badge · Breadcrumbs · Button · Card · EmptyState · Heading, Text · Pagination · SearchField · SegmentedControl · Separator · Table
And from Patine Pro:
- AI chat PRO
- Activity feed PRO
- Agent activity PRO
- Ai usage meter PRO
- App shell and layout PRO
- Brand logos PRO
- Combo chart PRO
- Command palette PRO
- Funnel chart PRO
- Gantt PRO
- Gauge chart PRO
- Heatmap PRO
- Kanban PRO
- Notification center PRO
- Pie chart PRO
- Pricing table PRO
- Radar chart PRO
- Scatter chart PRO
- Stats row PRO
- Status tracker PRO
- Timeline PRO
- Tree view PRO
Files
saas/
├── hooks/
│ └── useSaas.ts
├── AnalyticsOverviewScreen.tsx
├── AudienceScreen.tsx
├── CopilotScreen.tsx
├── FunnelsScreen.tsx
├── index.ts
├── ReportsScreen.tsx
├── RoadmapScreen.tsx
├── saas.constants.ts
├── saas.utils.ts
├── SaasApp.tsx
├── SaasBillingScreen.tsx
├── SprintBoardScreen.tsx
└── StatusScreen.tsx
It also uses shared/, the theme, money formatting and screen transitions every Pro app shares.
A look at the code
The funnel’s step rates and its biggest drop, from saas.utils.ts:
/** Each funnel step's share of the one before, as a rounded percent: the biggest drop is where to look first. */
export const stepRates = (stages: readonly { stage: string; users: number }[]) =>
stages.map((s, i) => ({
...s,
rate: i === 0 ? 1 : s.users / (stages[i - 1]?.users || 1),
}));
/** The step that loses the most people. */
export const biggestDrop = (stages: readonly { stage: string; users: number }[]) =>
stepRates(stages)
.slice(1)
.reduce((worst, s) => (s.rate < worst.rate ? s : worst), { stage: '', users: 0, rate: 1 });