Push Notifications That People Don't Hate: A Practical Guide

The default push notification experience is hostile. A new site asks for push permission three seconds after you arrive, before you've read anything, before you have any reason to trust it. You decline by reflex. Everyone declines by reflex.

Push notifications can be incredibly powerful — when they're done right. Here's the playbook we used to build push for IslaTodo and Island Happenings, where opt-in rates run 5-10x what the average web app sees.

Rule one: never ask on first visit

The default browser permission prompt is unforgiving. A "no" is permanent — the user has to dig into settings to reverse it. Asking on first visit, before they've read anything, guarantees a "no" 95% of the time.

Wait. Let them use the site. Let them get value. Ask only after they've taken an action that signals interest — finished an article, returned for a second visit, bookmarked something.

Rule two: pre-prompt before the real prompt

Before triggering the browser's permission prompt, show your own custom UI: "Want to know when [specific valuable thing] happens? We'll send you a push notification. Tap below to enable."

Two reasons this works. First, the visitor mentally commits before the browser dialog appears, so the dialog is just a confirmation. Second, if they say no to your custom UI, you can ask again later — versus the browser-level "no" which kills you forever.

Rule three: be specific about what you'll send

"Get notifications" is too vague to opt into. "Get a daily push when the morning Island Happenings issue drops" is specific, valuable, and easy to opt into. Specificity is permission. Vagueness is suspicion.

Rule four: deliver the value you promised, then stop

If you said "daily morning push," send a daily morning push. Don't add a "weekly newsletter" push without asking. Don't slip in a marketing push three weeks in. Every notification that wasn't what they signed up for is a betrayal — and they'll either disable push or, worse, abandon the site.

Rule five: timing matters

A push at 7am Eastern is fine. A push at 3am Eastern is hostile. Timezone-aware delivery is non-negotiable for any global audience. We use the user's local timezone for all scheduled pushes, with a "do not disturb" window from 10pm to 7am unless it's truly urgent.

Rule six: clear escape hatches

Every push notification should be 1-tap to disable. Not "go to settings → privacy → notifications" — a literal "Mute these" button right in the notification or the next page they land on.

This sounds counter-productive. It isn't. Visible escape hatches give users confidence to opt in, because they know they can opt out instantly if it gets annoying. Sites with prominent unsubscribe options have higher opt-in rates than sites that bury the off-switch.

The numbers from the field

Our IslaTodo PWA opt-in rate hovers around 18-22% of weekly active users. The web average is 1-3%. The difference isn't technical — it's behavioral. We don't ask early. We pre-prompt. We're specific. We deliver exactly what we promised. We make opt-out easy.

Every one of those users gets a push when something they care about happens, and our reactivation rates are 3-4x higher than email alone would deliver. Push, done right, is one of the highest-leverage retention tools in a small business stack. Done wrong, it's just another way to lose your audience.