ui patterns
Notifications & badges
How should you use notifications and badges?
Notifications and badges are signals that something needs attention - a count on an icon, a dot, a banner, a push alert. Used honestly they inform: "you have 3 unread messages". Used cynically they manufacture urgency and pull people back for the company's benefit, and either way they only keep their power if they're meaningful, because people quickly learn to ignore signals that cry wolf.
Also known as: notifications and badges, notification badges, badges
Prefer to watch?
Watch the recap 1:07
The demo
Two apps, each with a notification badge. Tap to open each and see what's actually behind the badge - one earns your attention, the other just wants it. Same little red dot, opposite intent.
What this demo shows (text version)
An app icon with a notification badge is shown two ways. The honest badge shows a real count of unread messages; tapping it opens those actual messages, and it clears - it pointed to something true and useful, so it earned the glance. The manufactured badge is a red dot or "1" with nothing meaningful behind it - tapping reveals a marketing nudge dressed up as activity, a signal engineered purely to pull you back.
That's the line with notifications and badges: an accurate, clearable signal that genuinely informs helps people prioritise, while a fabricated one fakes urgency and, like nagging, exploits our discomfort with unread indicators. Either way badges spend attention - over-badging causes notification blindness and anxiety - so make each one meaningful, controllable and honest, or people learn to ignore you.
A badge is a promise that there's something worth your attention - so only show one when there genuinely is. Informative badges (real unread counts, a status that changed) help people prioritise. Manufactured ones (a red dot to lure you back, a "1" for a marketing message dressed as activity) are a dark pattern that exploits our discomfort with unread indicators. And every badge spends attention: over-badging causes notification blindness (people learn to ignore the dot) and anxiety. So earn each one - make it accurate, dismissible, and tied to something the user actually cares about; let people control and mute them; and never fake urgency. Respect the attention you're asking for, or you'll lose it.
The honest badge told you something true and useful - three real unread messages - so it earned the glance. The manufactured one was a red dot with nothing behind it, engineered to nag you back. Same pixel, opposite intent. That's the line with notifications and badges: a signal that genuinely informs is welcome; one that fakes urgency or cries wolf trains people to ignore you - and erodes trust.
Badges work because an unread indicator creates a small, naggy tension people want to resolve - which is useful when it points to something real (unread messages, a genuine status change, an action required) and lets people prioritise at a glance. The honest forms are accurate, specific, clearable, and proportionate to importance (a dot for minor, a count for things you track, a banner or push only for the genuinely timely).
The dark-pattern forms exploit that same tension: red dots and counts manufactured to pull people back with nothing meaningful behind them, marketing dressed as personal activity, fake "1" badges, and push notifications engineered for engagement rather than the user's benefit. These overlap with nagging and addictive design, and they trade short-term re-engagement for long-term trust.
Either way, attention is finite and badges spend it. Over-notifying causes habituation and notification blindness - people learn the badge means nothing and ignore it (so your important signals are lost too) - plus real anxiety and fatigue. Design them responsibly: make every badge meaningful and accurate, easy to clear, and proportionate; give granular controls to mute, batch or turn off categories; default to restraint; and never fabricate urgency. A signal is only worth sending if it respects the attention it asks for.