Designing Notifications People Keep Enabled
By Maksym Bardakh · Co-founder & President
In short
A notification system succeeds when people keep it enabled, not when it sends the most. That requires earning the first permission with a clear reason, giving granular control so users silence categories instead of everything, and maintaining relevance so each notification justifies the interruption. Over-sending trains people to disable the channel, after which even important messages never arrive.
The metric is retention of the channel
It is easy to measure notifications by how many are sent or opened, but the metric that captures long-term health is how many people leave the notification permission on. A channel that is overused gets disabled, and once disabled it carries nothing, including the genuinely important messages. The objective is to remain a channel worth keeping, which is a constraint on volume and quality rather than a target for reach.
This reframes notification design as a relationship to maintain rather than a resource to spend. Each notification either strengthens or weakens the user’s willingness to keep listening.
Earn the permission, then keep it
The first notification permission request is a moment of high consequence and is often wasted by asking at launch, before the user understands what notifications would be for. Asking at a point where the value is clear, and explaining what the person will receive, earns permission honestly. After that, every notification is a test of whether keeping it on was a good decision.
- Request permission when the value is evident, not on first launch.
- Tell the user what they will receive before asking them to allow it.
- Treat each notification as evidence for or against keeping the channel on.
Granular control prevents the all-or-nothing exit
When a user is annoyed by one kind of notification but cannot turn off just that kind, their only recourse is to disable everything. Granular control, the ability to silence a category while keeping others, gives people a way to reduce noise without abandoning the channel entirely. The product keeps the notifications the person still values instead of losing all of them to a single irritation.
Relevance is the ongoing work
Keeping notifications enabled is not a one-time achievement but continuous maintenance. Relevance decays as a person’s situation changes, and a notification that was useful can become noise. Periodically reconsidering what is sent, removing categories that no longer earn their interruption, and resisting the temptation to add notifications for engagement’s sake are what keep the channel valuable over the long term.
Key takeaways
- The health metric for notifications is how many people keep them enabled, not volume sent.
- A disabled channel carries nothing, including important messages.
- Request permission when value is clear, and explain what will be sent.
- Offer granular control so users mute a category instead of everything.
- Maintain relevance continuously and resist adding notifications for engagement.
Frequently asked questions
- What is the right success metric for a notification system?
- How many people keep the notification permission enabled over time, because a disabled channel delivers nothing, including the messages that matter.
- When should an app request notification permission?
- At a point where the value is evident and after explaining what the user will receive, not at first launch before they understand the purpose.
- Why does granular notification control matter?
- Without it, a single unwanted notification forces users to disable everything. Per-category control lets them mute noise while keeping the notifications they value.
References
About the author
Maksym Bardakh
Co-founder & President
Maksym is a software engineer and product strategist focused on executive-function and behavioral system design. At BBMM he leads product direction across Flowo, TextPack, and Pillow, working at the intersection of human cognition and durable interface design.