A common onboarding problem

Users deny your permission prompts

The short answer: ask when the flow needs it. Here is how to recognise this problem in your funnel, why it happens, and how the best consumer apps design it away.

How to recognise it

  • Grant rates sitting well under half
  • The native prompt fires on first open, before any value
  • A growing segment you can never prompt again

Why do users deny permission prompts?

On iOS and Android you get one native prompt per permission. Decline it, and winning it back means a trip to system settings almost nobody makes.

Most apps spend that one shot on first open, when the user has no idea why the app wants it. At that moment the honest answer to “Allow notifications?” is “why would I?”.

A denied prompt is rarely about privacy. It is about timing: the ask arrived before the reason existed.

How do you increase permission grant rates? Ask when the flow needs it

Tie every permission to the moment the user is trying to do the thing it unlocks.

Location, when they tap “find near me”. Camera, when they choose to scan. Notifications, when there is something specific they would plainly want to hear about: a reply, a streak, a price drop.

A short pre-prompt in your own interface tends to help: one line on what saying yes unlocks, with a real choice. If they are not ready, you keep your native shot for a better moment.

How much explanation your users need varies by audience. Test the timing before the wording: in most funnels, timing moves grant rates more.

The building blocks that solve it

These come from the Onboarding stack of the Product Design Playbook. Each building block is five cards: the tactic and the psychology behind it, a Make It Yours prompt card, and three real app examples.

  • Permission Serve: Ask for access at the moment it unlocks something wanted.
  • JTBD Copywriting: Write the ask around the user's why, not the system's need.

Who does this well

Duolingo: The notification ask comes after your first lesson, framed as protecting the streak you just started. Saying yes feels like helping yourself.

Uber: Location is requested when you ask for a ride: the one moment it is obviously required to get what you came for.

Questions founders ask

What is a good permission grant rate?

It varies too much by permission and category for one number to mean much. Location asked in context tends to do far better than notifications asked cold, and utility apps see different baselines than social ones.

The more useful habit is tracking your own rate per permission and watching the direction after you move the ask.

Can you ask again after a user denies a permission?

Mostly no, not natively. On iOS the system prompt is effectively once; Android allows limited retries before it stops showing.

What you can do is catch a later moment of clear need and deep-link to settings with one line of reasoning. It works, but far less often than getting the first ask right.