Push notifications bring users back when each one is something the user wanted to know anyway: an order update, a reminder they set, a reply, a price drop on a saved item. Ask permission after the app has shown its value, let people pick message types, cap frequency, and judge success by opt-outs and repeat use.
Notifications are the one channel that reaches a user's lock screen directly, which is exactly why they're easy to abuse. One irrelevant promotion can lead someone to switch them off for good, or delete the app. Once that permission is gone, it's very hard to win back. Notifications are one piece of the wider mobile app development picture; here we focus on getting them right from the first release.
When should your app ask for notification permission?
Ask at the moment the user can see why notifications help them, not on the first screen. The first launch is the worst time to ask, because the user hasn't experienced any value yet.
On iPhone, apps must get explicit permission before sending notifications, and recent Android versions require a runtime permission too. You usually get one clean chance at the system prompt; if the user declines, they have to change it later in their phone's settings.
A better sequence:
- Let the user complete something first, such as booking a class, placing an order or saving an item.
- Show your own short explanation screen (a "pre-permission" prompt): "Want a reminder an hour before your class, and an alert if it's cancelled?" with Yes and Not now buttons.
- Trigger the system prompt only if they tap Yes. If they tap Not now, you haven't spent your one chance, and you can ask again at a more relevant moment.
On iOS you can also use provisional notifications, which deliver quietly to the notification centre without a prompt, so users can judge their usefulness before deciding. It suits apps where value is easier to show than explain.
Which notifications are worth sending?
Send notifications the user caused or asked for. Be most cautious with purely promotional messages, which are also the ones store rules and privacy laws treat most strictly.
| Type | Example | Value to user | Risk of annoying | Guidance |
|---|---|---|---|---|
| Transactional | "Your order is out for delivery" | Very high | Very low | Always send; keep them fast and accurate |
| User-set reminders | "Your appointment is tomorrow at 10:00" | High | Low | Let users set timing |
| Activity on their content | "Priya replied to your question" | High | Low to medium | Batch if frequent |
| Saved-item alerts | "The jacket you saved is back in your size" | High | Low | Only for items they chose |
| Onboarding nudges | "Finish setting up your profile to get matched" | Medium | Medium | Two or three at most, then stop |
| Re-engagement | "New classes added for next week" | Medium | Medium to high | Tie to their past behaviour |
| Promotional | "20% off this weekend" | Low to medium | High | Separate opt-in category; send sparingly |
Apple's App Review Guidelines restrict using push notifications for promotions unless users have explicitly opted in and can opt out easily. Privacy laws such as the EU's GDPR, India's DPDP Act 2023 and Australia's Privacy Act 1988 also shape how you handle consent and personal data, so treat marketing notifications as an opt-in, not a default.
How often is too often?
There's no universal number, so set your frequency from how often people naturally use your service. A good rule: never send more notifications than the user would reasonably act on.
Practical guardrails:
- Match the natural cycle. A weekly class app shouldn't nudge daily. A food-ordering app can reasonably notify around mealtimes, but not every mealtime.
- Set a weekly cap for non-transactional messages, and let transactional ones bypass it.
- Respect quiet hours and time zones. Send based on the user's local time, not your office's.
- Bundle bursts. "3 new replies" beats three separate buzzes.
- Stop when ignored. If someone hasn't opened the last several re-engagement messages, slow down rather than speed up.
On Android, notification channels let users switch off one category, such as promotions, while keeping order updates. Design your categories carefully, because a user who can mute only promotions is less likely to mute everything.
How do you write a notification people tap?
Be specific, personal and actionable, and make the tap land exactly where the message promised. Generic messages are the fastest route to an opt-out.
| Weak | Stronger | Why it works |
|---|---|---|
| "We miss you!" | "Your 5-class pack expires Friday. 2 classes left." | Concrete, useful, time-bound |
| "Check out what's new" | "Tuesday 7am yoga is back on the timetable" | Tells them the actual news |
| "Don't forget to complete your booking" | "Your 4pm slot with Arjun is held for 15 more minutes" | Specific detail, real urgency |
| "Big sale today!!!" | "Linen shirts you viewed are 20% off until Sunday" | Relevant to their behaviour |
Writing rules worth adopting:
- Lead with the most important words; lock screens truncate long text.
- Use the user's context (their class, their order, their saved item).
- Avoid sensitive details that could be read over someone's shoulder, such as health appointments or account balances.
- Deep link every notification, meaning the tap opens the relevant screen inside the app, not the home screen.
Which automated notifications should you set up first?
Start with a small set of behaviour-triggered messages tied to your core user journey. These usually outperform scheduled blasts because they arrive when they're relevant.
- Confirmation and status updates for every booking, order or payment
- Reminders before appointments or deadlines, timed by the user
- Abandoned action nudge, sent once, a short time after someone starts but doesn't finish a booking or checkout
- Onboarding sequence of two or three messages over the first week, each pointing to one useful feature
- Lapsed-user check-in after a period of inactivity that's long relative to your normal usage cycle, ideally with something genuinely new
When you plan these, add them to your feature list from the start; our guide to planning features for your first app version shows how to fit them into scope without overloading it.
Should you use push, email, WhatsApp or ads to bring people back?
Use each channel for what it does best, and coordinate them so the same person isn't hit with the same message three ways. Push is best for timely, short and personal alerts to people who already have your app.
- Push: instant, free per message, but only reaches users who installed and opted in.
- Email: better for longer content, receipts and sequences; our piece on email flows that turn buyers into regulars covers this.
- WhatsApp or SMS: high visibility, but each message costs money and needs clear consent.
- Retargeting ads: reach people who visited but never installed or enquired; see retargeting ads that win back visitors.
What should you measure?
Measure whether notifications drive the action you care about, and what they cost you in opt-outs. Open rate alone rewards clickbait; retention and opt-out rate tell you the truth.
Track for each notification type:
- Tap rate (opens divided by deliveries)
- Downstream action, such as bookings or orders within a set window
- Opt-out and category-mute rate after sending
- Uninstalls in the days following a campaign
- Retention compared with a holdout group, a small share of users who don't receive that message, so you can see whether it actually made a difference
Tools such as Firebase Cloud Messaging and dedicated push platforms handle delivery through Apple's and Google's notification services; most also offer segmentation, scheduling and basic analytics. Make sure events from the app flow into your analytics, otherwise you'll only see opens.
Frequently asked questions
Should I ask for notification permission when the app first opens?
Usually not. Users are more likely to agree after they've completed something useful and can see why notifications help. A short explanation screen before the system prompt lets you ask again later if they say "not now".
Can I send marketing notifications to everyone who allowed notifications?
It's safer to treat marketing as a separate opt-in category. Apple restricts promotional push notifications without explicit consent, and privacy laws in many markets expect clear consent for marketing. Transactional messages, such as order updates, are a different case.
Do progressive web apps support push notifications?
Many do, including on recent iPhones when the web app is added to the home screen. Support and reliability are still more limited than in native apps, so test on your users' devices before relying on it. For critical alerts, a native app remains the dependable option.
How do I win back users who turned notifications off?
Don't nag. Show the value inside the app instead, for example a gentle in-app message when a reminder would have helped, with a link to settings. Some users will re-enable notifications once they see what they're missing.
What's a good tap rate for push notifications?
It varies widely by app type and message type, so compare against your own baseline rather than a generic figure. Transactional messages naturally get more taps than promotions. Track trends over time and watch opt-outs alongside taps.
Getting notifications right from day one
Good notifications are designed alongside the app, not bolted on afterwards: the right triggers, sensible categories and clean deep links. If you're planning an app and want retention built in from the start, see our services and get in touch for a fixed-price proposal.