Context — Android 13 moved the ground
For a news app whose readers arrive through breaking-news alerts, notifications aren't a feature — they're the front door. Then Android 13 changed the rules: notification permission became opt-in, requested through a cold system dialog, with harsh limits on re-asking after a refusal. Our primary traffic channel now depended on winning a yes, often in a single attempt, from users who reflexively dismiss permission dialogs.
Onboarding: rehearse the yes
Through trials and user study sessions, one approach kept winning — and it wasn't persuasion, it was rehearsal. The onboarding screen I designed shows an exact replica of the Android permission dialog before the real one appears: same layout, same buttons, with "Allow" visually highlighted and a pointer resting on it, under a plain-language value line — don't miss breaking news from your city and beyond. By the time the real system dialog appears, the user has already seen it, understood it, and mentally tapped the right button. Nothing unfamiliar, nothing to fear, no decision being made cold.
It also had to sit smoothly in an onboarding that asks for location too (for local news) — sequencing the asks so each one arrives with its reason attached. Result: 70% of new users grant notification permission at onboarding.
Existing users: news as leverage
Onboarding only reaches new users. Millions of existing readers — and everyone who declined — needed a different path, and Android's re-ask limits meant each attempt had to count. The principle, carried over from my discovery work: don't manufacture intent, borrow it. The moment a reader most wants notifications is when a big story is unfolding — so that's when we ask, and that's what we ask with.
The system: a popup triggered during major trending stories, framed around that story — "turn on notifications for important updates on the Air India crash" — plus permanent entry points woven through my discovery surfaces: an "अलर्ट पाएं" ring in the story bar, a native-format card in the feed, and further prompts placed through the app. The trending-news popup and the native-format card performed strongest, pushing permission grants up significantly among existing users.
Decisions & tradeoffs
Rehearsal over persuasion
Most permission flows argue: benefits, badges, urgency. User sessions pointed elsewhere — the enemy wasn't disagreement, it was unfamiliarity. People dismiss dialogs they don't recognize. Showing the exact dialog in advance converts a startling interruption into a expected step. The design does less convincing and more preparing — and preparing won.
Contextual asks over generic ones
"Enable notifications" is an app asking for something. "Get updates on this crash investigation" is a reader being offered something. Anchoring the ask to a live story the reader is visibly following flips who the permission serves — and with Android limiting re-asks, spending attempts only at moments of peak intent was strategy, not style.
Infrastructure pays twice
The re-permission campaign needed reach, and reach already existed: the story rings and native-format widgets from my discovery work became its channels. Surfaces built to move readers toward content turned out to be equally good at moving them toward a yes — the quiet compounding return of building systems instead of one-offs.
Outcome
70% of new users now grant notification permission during onboarding — for a permission Android deliberately made hard to get, on the channel this business runs on. The existing-user system lifted grants significantly on top of that, with the trending-news popup and native feed card as the strongest performers. The front door stayed open.
What I'd do differently
Treat the permission as a loan, not a grant. Winning the yes is half the work; keeping it is the other half, because every over-sent or off-target notification pushes a reader toward mute or revoke — quietly un-earning what the design earned. I'd pair any permission system with notification-quality governance from day one: frequency caps, relevance standards, and revocation tracking as a first-class metric sitting right next to the opt-in rate.