
Key takeaways
- Ask for notification permission after the user has seen value, and explain what they will receive.
- Send messages that are timely, relevant and actionable; transactional messages beat promotions.
- Control frequency, respect quiet hours and let users choose what they receive.
- Link each notification to the exact screen it mentions, and measure opens, actions and opt-outs, not only sends.
Why notifications fail
Most users mute or disable notifications that are generic, too frequent or badly timed. A message that nobody acts on trains people to ignore the next one. Good notifications feel like a helpful service: they tell users something they care about, at a moment when they can act on it.
Ask for permission at the right moment
Do not show the system permission prompt on first launch. First let users experience value, then ask in context with a short explanation, for example “Get an alert when your order is on its way”. Many platforms allow only one system prompt, so a polite in-app message first protects it. If a user declines, give them a way to enable notifications later in settings.
Send what matters
| Type | Examples | Why it works |
|---|---|---|
| Transactional | Order confirmed, driver nearby, booking reminder, payment received | Expected and useful, rarely muted |
| Time-sensitive | Appointment tomorrow, offer ends tonight | Valuable only if timely |
| Personal | Item back in stock, points about to expire | Based on the user’s own activity |
| Broadcast | New menu, general promotions | Use sparingly and segment the audience |
Frequency, timing and quiet hours
- Set a weekly cap for promotional messages and stick to it.
- Send at times that suit the user’s local day, and avoid night hours.
- Offer separate categories so people can turn off promotions but keep order updates.
- Stop sending to users who have not opened any message for a long time.
Write messages people act on
- Put the useful information first: “Your driver arrives in 5 minutes”.
- Use plain language in the user’s language, including Arabic written naturally.
- Add one clear action, and open the exact screen it refers to.
- Do not use fake urgency or repeat the same message.
A worked example
A café app sends a daily promotion at noon and sees many users turn notifications off. The team separates order updates from marketing, limits promotions to twice a week and sends an offer only to users who ordered coffee recently. Opt-outs fall and the offers that do go out are used more. This is an illustrative scenario, not a client story, but the pattern is reliable: fewer, more relevant messages perform better.
Measure what matters
- Delivery and open rates by message type.
- Actions taken after opening, such as completing an order.
- Opt-out and uninstall rates after campaigns.
- Results of simple tests of timing and wording.
Build a simple notification plan
- 1List every message your app could send and mark it as essential, useful or promotional.
- 2Give each type its own setting so users can mute promotions without losing order updates.
- 3Write the message, the trigger and the destination screen for each one in a single table.
- 4Start with essential messages only, add useful ones next and promotions last.
Review the plan every quarter and retire any message that nobody opens.
Next step
Notifications work best inside a well-planned app. Read about mobile app onboarding, see our mobile apps service, or talk to us about engagement in your product.
Frequently asked questions
When should an app ask for notification permission?
After the user has seen value and understands what they will receive. Ask in context with a short explanation rather than on first launch.
How many push notifications are too many?
It depends on the app, but promotional messages should be limited and relevant. Transactional updates are expected, while frequent broadcasts cause opt-outs. Test and watch opt-out rates.
Do push notifications work for Arabic users?
Yes, when written naturally in Arabic and sent at suitable local times. Test the display with right-to-left text on real devices.

