The problem

Android 13 made notification permission opt-in. Overnight, the app's primary traffic channel depended on readers actively saying yes, and our opt-in rate collapsed.

Why the standard playbook failed

Best practice says ask during onboarding, while the user is fresh and moving through setup. We were doing exactly that, correctly, and it was not working.

The reason is what the question actually asks. At onboarding, a permission dialog asks someone to accept an abstract risk of being interrupted forever, from an app they have used for ninety seconds. Most people say no, and on Android that answer is expensive to reverse.

What I did

I broke the rule and added friction on purpose.

• A rehearsal before the ask. Readers saw a real news alert exactly as it would appear on their lock screen, then were asked for permission. The decision changed from an abstract risk to a concrete judgement about something they had just seen.

• News-triggered re-permission for existing users. Rather than nagging on app open, the prompt appeared alongside a genuinely major story, when the value of an alert was self-evident.

Results

• 70% opt-in at onboarding, after the collapse

• The app's main traffic channel survived the platform change

What I took from it

Best practices are someone else's context, generalised. Now when I follow one, I want to know what it was protecting. Asking honestly outperformed asking earlier.