Push notifications: how to use them without annoying people

Ask for permission when the value is obvious, send only what users would hate to miss, let them choose the types, and measure opt-outs as closely as opens.

By Sohail Hussain21 November 20265 min read

Push notifications work when every message is something the user would be annoyed to miss: their order is out for delivery, their appointment is tomorrow, someone replied to them, a payment failed. They annoy people when they are used as free advertising. The rules that keep you on the right side are simple. Ask for permission at the moment the value is obvious, not at first launch. Send transactional messages freely and promotional ones rarely. Let people choose which types they get. And measure how many people switch notifications off, not just how many tap.

Push is also the feature that most often justifies building an app instead of a website, so it deserves a plan before anyone writes code. On our mobile app development projects, the first deliverable for push is the list of messages, not the code.

Which notifications do people actually want?

Sort every message you plan into one of three groups:

TypeExamplesRule
TransactionalOrder shipped, booking confirmed, payment failed, password changedSend every time. This is why people allowed notifications.
Personal and timelyA reply to your message, a reminder you set, a price drop on an item you savedSend, with a setting to turn each type off.
PromotionalSales, new products, "we miss you"Only to people who opted in to them, rarely, and never late at night.

If most of your planned messages are in the third row, the app probably does not need push yet. The mobile app development guide suggests deciding the three or four messages that really help the user before building the capability, and that list is the best test of whether push will work for you.

Apple writes part of this into its rules. Guideline 4.5.4 of the App Store Review Guidelines says push must not be required for the app to work, must not carry sensitive personal information, and must not be used for promotions unless the user explicitly opted in through consent wording in the app, with a way to opt out inside the app.

When should you ask for permission?

Not on first launch. A system prompt that appears before the user has done anything gives them no reason to say yes, and on iOS you only get to show it once. If they decline, the only way back is through the Settings app, and few people go there.

Android works the same way since Android 13: apps must request the notification permission at runtime, as described in Android's notification permission guide, and after repeated refusals the system stops showing the prompt.

Ask at the moment the benefit is concrete:

  • Right after someone places an order: "Get a notification when your order ships?"
  • After they book an appointment: "Want a reminder the day before?"
  • When they start a chat: "Turn on notifications so you see replies?"

Many apps show their own explanation screen first, with "Turn on" and "Not now" buttons, and only trigger the system prompt when the user taps "Turn on". That keeps the one-time system prompt for people who already said yes.

iOS also offers provisional authorisation, which delivers notifications quietly to Notification Center without asking first. The user sees them there and chooses to keep or turn them off. It suits apps whose first notifications are clearly useful and low-key.

How many notifications is too many?

The wrong question. Ten delivery updates in one afternoon are fine; one irrelevant promotion can be one too many. Volume is a problem only when the messages are not wanted.

A few rules hold in every app we have built:

  • No duplicates across channels. If the order update arrives by push, do not also send the same text by SMS and email unless the user chose that.
  • Respect the user's local time. Promotional messages only in waking hours, in the user's own time zone. Transactional messages can go any time they are relevant.
  • Cap promotions. Decide a maximum per week before the marketing team asks.
  • Collapse bursts. Five replies in a thread become one notification, not five.

How do you give people control?

People who can turn off one type of notification keep the rest. People who cannot, turn off all of them.

Build a notification settings screen with each category as its own switch: orders, reminders, messages, offers. On Android, map each category to a notification channel, so users can also control them from the system settings. On iOS, use the right interruption level: reserve "time-sensitive", which can break through Focus modes, for things that really cannot wait, as Apple's Human Interface Guidelines on notifications recommend.

Store each user's preferences on your backend, not just on the phone, so they follow the user to a new device and so your sending system can respect them.

What does a good notification say?

Specific, short and actionable, and it opens the exact screen it refers to.

WeakBetter
"You have a new update""Your order #1042 has shipped. Arriving Thursday."
"Don't forget!""Dental check-up tomorrow at 10:30 with Dr Rao. Tap to reschedule."
"We miss you!"(Do not send it.)
"New message""Priya: The quote looks good, can we start Monday?"

Two technical details make the difference. Deep links: tapping the notification should land on the order, the booking or the conversation, not the home screen. Privacy: the message is shown on the lock screen, so leave out anything sensitive, such as medical details or account balances, unless the user chose to see it.

What should you measure?

Track four numbers per notification type, not just one:

  1. Opt-in rate: the share of users who allowed notifications. Check permission status on each app open, because users change it in Settings without telling you.
  2. Open rate: the share of delivered notifications tapped.
  3. Disable rate: the share of users who turn a category, or all notifications, off within a few days of a send.
  4. Uninstalls after a campaign: the bluntest signal that a message was unwelcome.

A promotion with a good open rate and a spike in disables cost you more than it earned: those users will not see your next order update either.

Building push properly, with device tokens for both platforms, a sending service, deep links, categories and preferences, is typically 20 to 50 hours of a cross-platform build as of October 2026, as listed in how much a mobile app costs. Our app cost calculator includes it as a line item. Write the message list first; it decides how much of that you need.

Was this guide useful?

Questions

Frequently asked.

How many push notifications per week is too many?

There is no safe number, because it depends on what the messages are. Ten order updates in a day are welcome during a delivery; one irrelevant promotion a week can be enough to get notifications switched off. Count promotional messages separately, keep them rare, and watch the rate at which people disable notifications after each campaign.

Can I send marketing push notifications?

On iOS, only to people who have explicitly opted in to promotional messages through consent wording in your app, and only if the app lets them opt out again, under Apple's guideline 4.5.4. Treat the same rule as good practice on Android. Transactional messages such as order updates do not need the separate opt-in, but they still need notification permission.

Do push notifications cost money to send?

Apple's and Google's push services do not charge per message. The costs are building it (device tokens, a sending service, deep links, preferences), typically 20 to 50 hours for a cross-platform app as of October 2026, and any third-party messaging platform you use for scheduling and segmentation, which usually charges by audience size.

Sohail Hussain

Founder, MSH Technologies

Sohail has designed and built websites, web apps and AI products for over 12 years, for clients from Singapore-based industrial groups to early-stage SaaS startups. He writes about what actually worked.

Keep reading

Related guides.

All posts

Your next move

Like what you see? Tell us about it.

A process that takes too long, a website that undersells you, or an idea ready to take shape. Tell us where you are and we will suggest a useful next step.

India · Working with clients worldwide

Sohail, Founder, replies within 1 working day (Mon–Sat, IST). Free and no obligation.