Notifications
Tell people about things that need them, in the right channel and at the right volume, without burying what matters.
7 states5 edge casesDesktop + Mobile
01The problem
Collaborative products generate events constantly: comments, mentions, assignments, approvals, status changes. Send all of them and users mute everything, including the approval that's blocking a deal. Send too few and work stalls. The problem is deciding which events deserve interruption, which can wait, and which are just history.
02When to use
Use when
- Collaborative products where people depend on each other's actions
- Workflows with assignments, approvals or mentions
- Events users must act on outside the product: failed payments, expiring access
Avoid when
- Events nobody needs to act on — record them in activity history instead.
- Marketing messages — these belong in a separately consented channel.
03Recommended UX
Statecraft recommendation
Classify every event as action required, informational or history, and route only action-required events to interrupting channels.
04Desktop behaviour
On desktop, the inbox is a panel opened from the header bell, with grouped items and inline actions for the most common responses.
Desktop rules
- Badge shows the count of action-required items only, not every unread event.
- Tabs: For you (mentions, assignments, approvals) and All activity.
- Inline actions for common responses: Approve, Reply, Mark done.
- Each item links to the exact place — the comment, not just the record.
05Mobile behaviour
On mobile, push is the most interrupting channel. Use it sparingly and make each push land on the exact item.
Mobile rules
4 mobile rules are included in Pro.
Statecraft Pro
Unlock the full pattern
Get the complete interaction flow, states, edge cases, mobile rules and implementation prompt.
- Interaction flow · 6 steps
- 4 mobile rules
- 7 states
- 5 edge cases with recommendations
- 4 microcopy comparisons
- Accessibility notes
- Developer notes
- Claude Code / Codex implementation prompt
Edge cases covered in this pattern
- Already handled elsewhere
- Burst of events
- Email and in-app duplicates
- Notifications for deleted items
- Muted everything