Warranty support for every website and app 🛡️

App development

How to use push notifications in your app without annoying customers

When to ask for notification permission, which notifications need separate consent and how to plan them under Apple and Android rules before development starts.

How to use push notifications in your app without annoying customers

Plan push notifications before development starts, as a list of specific triggers rather than a channel for mass messages. Ask for permission at the moment people understand why a notification is useful to them, not on first launch. Keep marketing messages behind explicit consent and offer settings for each type of notification inside the app. This keeps the app within Apple's and Google's rules and gives people fewer reasons to switch everything off at once.

This article is for owners and managers commissioning an app for bookings, orders, customer accounts or internal work who want to know what to put in the specification. The requirements were checked against Apple's and Android's official documentation as of November 2026. The platforms change them, so check again before launch.

What the platform rules say

On both iOS and Android, notifications are no longer on by default. The app has to ask for permission, and the person's answer decides what it can send.

  • Android. Since Android 13 (API 33), apps need the POST_NOTIFICATIONS permission. On a new install, notifications are off until the user allows them. If the app targets Android 13 or higher, it decides when the dialog appears. Since Google Play now requires new apps and updates to target a much newer version (see the pre-launch checklist), this choice is effectively yours.
  • Android, repeated requests. If someone denies the same permission more than once, the system treats it as a permanent “don't ask again” and the dialog no longer appears. The only way back is through system settings.
  • iOS. The system prompt appears only on the first request. Later requests do not prompt again, so you get one chance to pick a good moment.
  • App Store rules. Under Apple's App Review Guidelines (section 4.5.4), an app must not require notifications to function, and notifications should not carry sensitive personal or confidential information. Section 5.1.1 forbids making features or rewards conditional on turning notifications on.

Start with a list of notifications

Before design, write down every occasion on which the app will contact the person. For each one, decide its type, its urgency and whether separate consent is needed. These decisions later become Android channels and iOS interruption levels, so it is cheaper to make them early.

Notification typeHypothetical exampleSuitable iOS levelSeparate marketing consent
Order or request statusYour order is ready for pickupActive, or Time Sensitive if the event is happening now or within an hourNo
Reminder the person asked forYour appointment is tomorrow at 10 amActiveNo
Account securityNew sign-in from an unknown deviceTime SensitiveNo
Message from a staff memberReply from supportCommunication notificationNo
Promotion, offer, newsSaturday discountPassive or Active, never Time SensitiveYes

Apple describes four interruption levels. Passive is for information people can look at when they like. Active is the default. Time Sensitive breaks through Focus and scheduled summaries, so Apple recommends it only for events happening now or within an hour. Critical requires a special entitlement from Apple and is meant for health and safety, so it is not an option for most business apps.

On Android, since version 8.0, every notification must belong to a channel, and users control each channel separately in system settings. Once a channel is created, the app can no longer change its behaviour, only its name and description. Channels should therefore match the types in your list, for example “Orders”, “Reminders” and “Offers”. If everything sits in one channel, someone who does not want ads will also switch off their order updates.

When and how to ask for permission

  1. Wait for the right action. Apple's example is a task app that asks after the person schedules their first task. In a business app, that might be the first booking or order.
  2. Explain the benefit on your own screen before the system dialog. One sentence about what the person will receive, plus a way to decline. Android explicitly recommends that such an explanatory screen can always be dismissed.
  3. Consider trial notifications on iOS. With provisional authorization, the app can send quiet notifications without asking first. They appear only in Notification Center, with buttons to keep or turn them off. This works well when the notification itself shows its value best.
  4. Accept a no. The app must work without notifications. Show the order status inside the app and offer to turn notifications on from settings instead of asking again every time the app opens.

Marketing notifications need separate consent

Permission from the system dialog is not consent to advertising. Apple only allows promotional notifications if people have explicitly opted in through consent language shown in the app's interface and can opt out inside the app. In its design guidelines, Apple adds that you should describe the kind of messages you will send and provide a settings screen where the choice can be changed.

In practice, this means a separate “Offers and news” switch, off by default, with clear wording next to it. Record in your system when and with which wording consent was given, so you can show it if needed. If notifications are personalised using purchase history or other personal data, discuss data protection requirements with a lawyer. This article is not legal advice.

Settings inside the app

The notification screen in the app should mirror the types in your list rather than offer a single on/off switch. It helps to include:

  • a separate switch for each type, with a short description of what it covers;
  • a visible status if notifications are turned off at system level, with a button to system settings;
  • where it makes sense, quiet hours when no marketing messages are sent;
  • syncing the choices to the account, so they survive a phone change.

This is a design task as much as a coding one. If the interface is being built from scratch, include this screen in the UI/UX design from the first version.

Connecting to your CRM and other systems

Useful notifications usually come from events in other systems. An order changes status in the warehouse, an appointment is confirmed in the calendar, a staff member replies in the CRM. If these connections are not specified, notifications stay manual and go out to everyone at once.

  • Describe which event in which system triggers which notification, and for whom.
  • Keep notification preferences in one place, so nobody gets the same message by email, by text and in the app.
  • Do not put data in the notification text that should not be visible on a locked screen, such as amounts, health information or access codes. Write “You have a new message” and show the details after sign-in.

Connecting an app to a CRM, warehouse or calendar is a typical automation and integration project.

What to measure

Do not track only how many notifications were sent. A few metrics split by platform and notification type are more useful:

  • what share of people grant permission, and on which screen the question was asked;
  • how many people switch off a particular type in the in-app settings;
  • how many opens lead to an action, such as a confirmed appointment or a collected order;
  • whether marketing campaigns coincide with a rise in opt-outs.

If a notification links to a page on your website, tag the link the same way you tag your other channels, so the visits can be told apart in your analytics.

Common mistakes

  • The system prompt appears on the very first screen, before the person has seen what the app does.
  • All notifications share one Android channel, so opting out of ads also stops important messages.
  • Time Sensitive is used for promotions, which Apple's guidelines explicitly rule out.
  • Promotions go to everyone who allowed notifications, without separate consent.
  • A feature or discount is locked until the person turns notifications on.
  • The notification text contains personal or financial details.

A hypothetical example

This example is made up and only serves as an illustration. A beauty salon commissions a booking app. Its list of notifications contains appointment confirmations, a reminder the day before, changes made by the salon and monthly offers. The app asks about notifications right after the first booking, with a screen saying “Shall we remind you of your appointment the day before?”. Offers are a separate switch, off by default. On Android there are three channels, “Bookings”, “Reminders” and “Offers”. If a customer declines notifications, her appointment and any changes are visible in the app, and the salon can decide whether to send reminders through another channel she has agreed to.

Checklist for your specification

  • There is a list of all notification types with trigger, recipient and urgency.
  • Each type has an Android channel and an iOS interruption level.
  • The moment when the app asks for permission is defined, along with the explanatory screen before it.
  • The app works fully without notifications.
  • Marketing notifications have separate consent, wording and an in-app opt-out.
  • There is a settings screen by type and a link to system settings.
  • It is specified which CRM, warehouse or calendar events trigger notifications.
  • Notification texts contain no sensitive data.
  • The metrics you will track after launch are chosen.

If you are planning a new app or want to tidy up notifications in an existing one, this list is a good starting point for a conversation with your team, or with us as part of app development.