Push notification strategy: how to be helpful, not annoying

How to earn notification permission, send messages people value, time and personalise them well, and measure whether notifications help or hurt retention.

By the UK Technology Hub teamPublished 4 minute read

The short answer

Push notifications are powerful because they reach people instantly, and risky because too many lead users to disable them or delete the app. Ask for permission in context, send messages that are timely, relevant and useful, let users choose what they receive, respect quiet hours, link straight to the right screen and track not just opens but retention and opt-outs.

A good notification feels like a helpful tap on the shoulder: your order has shipped, your appointment is tomorrow, someone replied to your message. A bad one feels like spam. The difference decides whether notifications grow your app or drive users away.

Earn permission first

On iOS, apps must ask permission before sending push notifications, and Android 13 and later also require a runtime permission. You usually get one good chance.

  • Don't ask on first launch before users understand the value.
  • Ask in context: after someone books an appointment, offer reminders.
  • Explain the benefit with your own pre-permission screen before the system prompt.
  • Make it easy to enable later from settings.

Types of notifications

Transactional: order updates, booking confirmations, payment receipts, security alerts. High value, expected by users.

Reminders: upcoming appointments, tasks, renewals.

Social and activity: messages, comments, mentions.

Content and recommendations: new articles, products or features matching interests.

Promotional: offers and sales. Use sparingly and only with clear consent where required.

Make every notification earn its place

Before sending, ask:

  1. Is it timely?
  2. Is it relevant to this person?
  3. Is it useful, or just useful to us?
  4. Is the message clear without opening the app?

Timing and frequency

  • Send at sensible local times based on the user's time zone.
  • Respect quiet hours, typically late evening and night.
  • Cap the number of marketing notifications per week.
  • Batch low-priority updates into summaries.
  • Trigger notifications from behaviour, such as a saved item coming back in stock, rather than fixed schedules.

Let users choose

Offer notification categories in settings, such as orders, reminders, messages and offers, so people can turn off the types they don't want without turning off everything. Android notification channels support this at the system level.

Write good notifications

  • Lead with the most important information.
  • Keep it short; text is truncated on many devices.
  • Be specific: "Your table at 7:30 p.m. is confirmed" beats "Booking update."
  • Use a friendly, consistent tone.
  • Avoid clickbait and false urgency.

Tapping a notification should open the relevant screen, not the home screen. Our guide to deep linking explains how.

Rich notifications

Images, action buttons such as "Confirm" or "Reschedule," and grouped notifications can make messages more useful. Use them where they genuinely help.

Personalisation and AI

Personalised timing and content can improve relevance, for example sending reminders at the time a user usually engages. AI can help choose content or timing, but keep users in control and avoid feeling invasive.

Privacy and rules

  • Don't put sensitive information, such as health details or account balances, in notification text visible on a lock screen.
  • Get appropriate consent for marketing messages under the laws where your users live.
  • Follow app store guidelines, which restrict using push notifications for advertising without opt-in.

Measure the right things

  • Permission opt-in rate.
  • Open rate by notification type.
  • Conversions or actions after opening.
  • Opt-out and disable rates.
  • Uninstalls after notification campaigns.
  • Retention for users with and without notifications.

If a campaign raises opens but also raises opt-outs, it may be doing long-term harm.

When notifications don't arrive

Delivery problems are common, from expired tokens to misconfigured certificates. Our guide to fixing push notifications that aren't working walks through the checks.

A simple notification plan

Write down every notification your app sends in a table: name, trigger, audience, timing, frequency cap, category and the action it should prompt. Review it with product, marketing and support together. This makes it obvious where you're sending too much, where valuable messages are missing and which notifications have no clear purpose.

Handling notification fatigue

If opt-out rates rise, review frequency first, then relevance. Consolidating several small updates into one daily summary often keeps users informed without overwhelming them.

How we help

Our mobile app development team builds notification systems with categories, deep links and analytics. Our app development service designs permission flows that respect users, and our AI solutions team can add smarter, personalised timing.

Frequently asked questions

How many push notifications should an app send?

It depends on the app and what users chose, but quality beats quantity. Transactional messages are welcome; frequent promotions lead to opt-outs.

When should I ask for notification permission?

When the user does something that makes notifications clearly useful, such as booking or ordering, not on first launch.

Can I send marketing push notifications?

Yes, with appropriate consent and in line with app store rules and local laws. Keep them relevant and infrequent.

This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.

Related guides

All web & mobile apps guides