Contents
Push notifications are one of the most effective channels for bringing users back into your app – and one of the fastest ways to annoy them. Used well, they deliver something relevant at the right moment. This article explains the technology behind push, the right time to ask for permission and a strategy that doesn't drive users to switch notifications off.
How push notifications work technically
Push messages are not sent directly from your server to the phone but via the platform providers' services:
- Registration: the app requests a device token from the operating system – on iOS via the Apple Push Notification service (APNs), on Android via Firebase Cloud Messaging (FCM).
- Storing the token: the app sends the token to your backend, which links it to the user account. A user may have several devices and therefore several tokens.
- Sending: your backend sends the message with the token to APNs or FCM, which deliver it once the device is reachable.
- Display and action: the operating system shows the notification. When the user taps it, the app opens – ideally via a deep link straight to the right screen.
Many teams also use FCM for iOS because it covers both platforms through one interface, or rely on specialised services for segmentation and campaigns. Operationally, tokens change, invalid tokens must be cleaned up and delivery is never guaranteed. Critical information should therefore also be available inside the app, for example in a message centre.
Types of notifications and how to use them
| Type | Examples | Trigger | Value for users |
|---|---|---|---|
| Transactional | Order shipped, appointment confirmed, payment received | User action or system event | Very high – expected |
| Reminders | Appointment tomorrow, subscription expiring, task due | Time or deadline | High, if requested by the user |
| Social interaction | New message, comment, mention | Other users | High, with control over frequency |
| Behaviour-based | Abandoned cart, feature not yet tried | Usage data | Medium – depends heavily on timing and tone |
| Marketing | Promotions, new products, newsletter content | Campaign | Low to medium – highest opt-out risk |
| Silent pushes | Refresh data in the background | Server | Indirect – invisible, throttled by the system |
The further down the table, the more sparingly you should send. Marketing pushes may also raise consent questions under data protection law – clarify these with your data protection officer.
The permission prompt: timing is everything
On iOS users must explicitly allow notifications, and since Android 13 a runtime permission is required there as well. The system prompt usually appears only once; anyone who declines has to enable notifications manually in the settings later. Don't waste that moment:
- Don't ask on first launch. Users don't yet know the value of the app.
- Ask in context: for example right after an order ("Would you like to be notified when your parcel is on its way?") or when booking an appointment.
- Explain first: a custom screen before the system prompt (a "pre-permission" screen) explains the benefit. If users decline here, the system prompt remains available for later.
- Consider provisional delivery: iOS can deliver notifications quietly to the notification centre first, so users can experience their value.
The permission prompt is part of onboarding and should be designed together with it.
Strategy: relevance over reach
Every notification competes with dozens of other apps for attention. A sound push strategy follows a few simple rules:
- Offer categories: let users choose in the app which kinds of messages they want. Android notification channels support this at system level too.
- Cap frequency: set a maximum per user per week, especially for marketing.
- Respect time zones and quiet hours: no promotional messages at night or early in the morning.
- Personalise instead of broadcasting: "Your appointment at Dr Miller's practice tomorrow at 9 am" is more valuable than "Don't forget your appointment!".
- Always lead somewhere: every push should open a specific screen via deep link, not just the home screen.
- Avoid sensitive content: notifications appear on the lock screen. Health or financial details don't belong in the text.
Push is one element of retention, but not the only one. How it interacts with onboarding, content and gamification is described in our article on retention strategies for apps.
Measuring and optimising
Without measurement, push strategy is guesswork. Useful metrics include:
- Opt-in rate: the share of users who allow notifications, split by platform.
- Open rate: the share of delivered messages that are tapped.
- Follow-up action: what do users do after opening – complete an order, reply to a message?
- Opt-outs: do users disable notifications or even uninstall the app after certain campaigns?
Test wording and timing with A/B tests and evaluate results over a sufficient period. Further key metrics are covered in app analytics: the KPIs that matter. Keep in mind that tracking in apps may require consent – see consent for app tracking under the German TDDDG.
Implementation checklist for your project
- Define push use cases and categories before development.
- Token management in the backend supporting several devices per user and cleanup of invalid tokens.
- Deep links for every notification type.
- An in-app settings page for categories and quiet hours.
- A pre-permission screen and contextual permission prompt.
- Rich notifications (images, actions) only where they add real value.
- Logging of sends and errors, monitoring of delivery rates.
- Privacy policy updated to cover push services.
Conclusion
Push notifications are technically manageable; their success depends on strategy. Ask for permission at the right moment, send mainly transactional and personally relevant messages, give users control and measure consistently. If you are planning an app with a well-thought-out notification concept, our offer wizard leads to a fixed-price quote after a free analysis.
Frequently Asked Questions
Do I need Firebase for push notifications?
On Android, delivery usually runs through Firebase Cloud Messaging; on iOS through APNs. Your backend can talk to APNs directly or use FCM for both platforms.
When should an app ask for notification permission?
Ideally at a moment when the benefit is obvious, such as after an order or booking. An explanatory screen before the system prompt increases acceptance.
How many push notifications are too many?
There is no fixed number. Transactional messages are expected; limit marketing pushes significantly and watch your opt-out rate.
Do push notifications work for web apps?
Yes, web push is supported by modern browsers, although on iOS only for web apps added to the home screen. Reach and capabilities are usually lower than with native apps.