· 7 min read

Push Notification Permission in India: When to Ask

Push notification opt-in stays low when apps ask on first open. Ask at the moment a reminder solves a daily need, and keep a route back for users who said no.

Push notification permission: ask when a reminder solves a daily need, not on first open. Plus a plan for users who said no.

Updated October 2026.

Ask for push notification permission at the moment a reminder would solve something the user already cares about, not on the first screen. Tie the ask to your app's everyday use, such as a water reminder, an event in their city or a price drop on something they saved, explain it in your own words before the phone's prompt appears, and plan a second route for the people who say no.

I'm Raviraj Ramavarapu, founder of Compound Lab, a retention agency for D2C brands and consumer apps. I led CRM and ecommerce at Healthify and now review consumer apps where push opt-in sits in low single digits. This page is how I'd fix that.

Why do so few users allow push notifications?

Because most apps ask before the user has a reason to say yes. The phone's prompt appears on first open, says the app "would like to send you notifications", and gives no reason. A new user who hasn't seen what the app does taps "Don't allow".

Android made this harder. Since Android 13, notifications are off by default for newly installed apps until the user grants permission. Airship's 2025 push benchmarks show what that did: the median Android opt-in rate fell from 71.3% to 59.5% in a year, while iPhone, which always asked, held at about 49%.

The same report puts the bottom 10% of media apps below 29.8%. An app in low single digits isn't facing a tough market. Its ask is in the wrong place.

When should you ask for notification permission?

Ask when a notification would clearly help the user with something they do every day in your app. That's the moment they understand why they'd want to hear from you. Android's own guidance says the same thing: let people get to know the app first, ask in context after they take an action, and it's fine to wait until the third or fourth launch.

At Healthify we asked very subtly: did the user want to be reminded about their daily water intake? It was a small nudge, and it was very impactful. It didn't read as a request for permission. It read as the app offering to help with something people already wanted to get right.

Bigger consumer apps work the same way. When I log in to District, it doesn't ask for notifications in general. It tells me I'll otherwise miss important events happening in my city. Myntra asks when there's something new worth hearing about. Neither treats notifications as a setting. Both tie them to the reason people open the app.

You can still have a light hook in onboarding. But the ask that works best sits on your app's core, most understandable feature, the one tied to a daily need:

App type The moment to ask What the ask offers
Health and fitness Right after the first meal or drink is logged A nudge at the hour they usually forget
Events and tickets When they browse events in their city A heads-up before something they'd like sells out
Shopping When they save an item or set a size A note when it drops in price or comes back in stock
Learning and content After the first lesson or episode The next one, at the time they chose
Family and tasks When they add a task with a date A reminder on the day, so nothing slips

Two permission screens. On the left, the phone's own prompt on first open with no reason given. On the right, the app's own card after the first glass of water is logged, offering a daily reminder, with a Yes and a Not now button.

How should the permission ask be worded?

In your own screen first, in one line about the user's need, with a clear way to say not now. Only show the phone's prompt after they tap yes.

That order matters because the system prompt can't be changed and can't explain anything. Android's permissions guidance recommends explaining why before you request, and always letting the user cancel. Four rules for the wording:

  1. Lead with their need, not your feature. "Want a reminder to drink water at 11?" beats "Turn on notifications to stay updated".
  2. Be specific about what they'll get. A time, an event, a product. "Updates" means nothing.
  3. Say how often. "One reminder a day" lowers the fear of being spammed.
  4. Make "Not now" easy. Users who feel trapped tap no on the next screen too.

For the notifications themselves, my push notification examples show what to send by moment, and the push notification preview tool shows how a message will look on the lock screen before you send it.

What about iPhone users?

On iPhone you get one system prompt. Apple records the answer the first time you ask, and after a no, only the user can change it in Settings. So the same rule holds even more strongly. Explain the benefit on your own card, and trigger the system prompt only after a yes.

Apple also offers provisional authorization. The app can send notifications quietly to Notification Center, with no sound, no banner and no prompt, on a trial basis. The user then chooses to keep them or turn them off. It suits apps whose value is easy to see in one message, like an event alert or a price drop.

How do you reach users who said no?

Use the channels you still have, show value first, and ask again only when there's a new reason. Airship found in-app messages lift opt-in by 14% on average among users who had opted out.

Know the limits before you plan. On Android, a user who taps "Deny" twice will never see the system prompt again for that app. On iPhone, one no is final from the app's side. After that, the only way back is a button that opens the app's notification settings.

  1. In-app first. Show the value inside the app: "Your water reminder would have gone off 20 minutes ago." Add a button that opens notification settings. Show it at most once a week.
  2. Ask again on a new reason. A new feature, a saved item, an upcoming event. A fresh reason works. Repeating the old ask doesn't.
  3. Email and WhatsApp for the rest, only where the user has opted in. WhatsApp marketing messages are charged per message even inside the 24-hour window, so keep them for moments that matter, not daily nudges.
  4. Never punish a no. The app should work fully without notifications. Users who feel pressured uninstall.

What should the first notifications say so people keep them on?

Exactly what you promised when you asked. If the ask was about a water reminder, the first notification is that water reminder, at the hour they picked. People turn notifications off when the first few feel like marketing.

Keep the first week to one useful notification a day at most. Make every one open the right screen, not the home page. And hold back offers until the user has had a few notifications that helped. If you're writing these from scratch, the push notification generator drafts them within each platform's character limits.

Does India's DPDP law change how you ask?

The phone's permission covers whether you can send push notifications at all. India's Digital Personal Data Protection Rules add a separate layer for how you use personal data, including for marketing. The Rules were notified on 13 November 2025, and their notice and consent obligations apply from 12 May 2027.

The practical step now is to record what each user agreed to, on which channel and when, and to make it as easy to withdraw as it was to give. An ask tied to a clear purpose, like a water reminder, is easier to defend than a blanket "allow everything". I'm not a lawyer, so check the specifics for your app with one.

How do you know your notification permission strategy is working?

Measure opt-in among new users each week, split by where the ask appeared, and check that opted-in users stay. A higher opt-in that leads to more people switching off later hasn't worked.

Measure What it tells you
Opt-in rate of new users, by week Whether the new ask is working
Yes rate on your own screen, by placement Which moment and wording people agree to
Share who allow after tapping yes on your screen Whether the system prompt follows the promise
Opt-outs within 30 days Whether the first notifications matched what you offered
Return visits, opted-in vs not What each opt-in is worth to retention

If the opt-in rate moves but new users still don't come back, the problem is earlier, in the first session. I cover that in how to improve app retention in India.

Where I fit

Compound Lab works with D2C brands and consumer apps on everything after the install, from onboarding and permissions to first-week messages, renewals and win-back. If your push opt-in is low and you're not sure where to ask, book a 30-minute call and we'll go through your first session and find the right moment.

Next postApp Retention in India: Tell Users What to Do Next

Your customers already paid once. Make them pay again.

Book a Consultation