Every notification an app sends is a small interruption of someone’s life, justified by a promise: this was worth your attention. Send a few that keep the promise and people come to trust the buzz in their pocket. Send a stream that breaks it — the nudge to “come back,” the manufactured urgency, the third reminder about nothing — and you teach them, quickly and permanently, to ignore you. Notifications are a relationship, and most apps treat them like a megaphone.
Attention is a borrowed thing
When someone allows your notifications, they are extending you credit against their attention. It is one of the most generous things a user can do, and one of the most fragile. Every alert draws down that credit. A genuinely useful one pays it back with interest; a pointless one is a straight loss. The mistake almost everyone makes is treating the account as bottomless, spending freely because each individual notification feels harmless. It is the pattern that bankrupts you, not the single message.
The overdraft is one-way
Here is what makes it unforgiving. The moment your notifications become noise, people do not carefully recalibrate. They mute you — or worse, they keep you on but stop seeing you, your alerts sliding past unread forever. And that decision almost never gets reversed. Nobody re-enables notifications for an app that annoyed them. So the genuinely important message you send later, the one that actually mattered, arrives into a channel you have already poisoned. You spent the relationship on growth-team busywork, and it was not refundable.
What restraint looks like
- Default to silence. A notification should have to earn its place. The question is not “could we notify them?” but “would they thank us for this?”
- Send once, when it resets. One alert for a thing that happened, not a drip of reminders until they act.
- Cap it. A hard ceiling on how often any one person can be interrupted, no matter how many “opportunities” the system finds.
- Separate the urgent from the nice-to-know. Let people keep the alerts that matter and shed the rest, instead of forcing all-or-nothing.
When we built notifications into a platform that musicians actually depend on, the guardrails came first, not last: a kill switch, a per-person daily cap, and a rule that nothing fired twice for the same thing. Not because the rules were exciting, but because the alternative — an automated system quietly spamming someone overnight — is exactly how you lose a user’s trust in a single bad night.
The test before you send
There is a simple gut-check for any notification: imagine the person reading it at the worst possible moment — mid-meeting, half-asleep, on a hard day. Would they feel looked after, or intruded upon? If you cannot honestly say the former, do not send it. A notification you withhold costs you nothing. A notification that breaks the promise can cost you the channel for good.
Treat the buzz in someone’s pocket as the privilege it is. Spend it carefully, and it keeps paying you back. Spend it like it is free, and you will find out exactly how expensive free was.