Back to all posts
Notifications7 min read·October 25, 2026

Push Notifications Users Keep Switched On

TB
ThynkBlox Apps Team
App Engineering

A good push notification strategy gives users timely information they asked for, with control over what arrives and how often. Ask permission when the benefit is clear, separate service updates from promotions, and judge results by useful actions alongside opt-outs. Treat permission as the start of an ongoing agreement about interruptions.

What deserves a push notification?

Start with the user's reason for installing the app. A notification should help them complete something, respond to a change or follow an event they chose to track.

Before adding a message, write down its trigger, recipient, useful action and expiry point. If you cannot explain why someone needs it outside the app, consider showing it inside the app instead.

Use a planning table like this:

Message typeUser benefitSuggested approach
A requested service updateKnow that something has changedSend when the change happens and still matters
A reminder the user createdRemember an intended actionFollow the user's chosen schedule
Activity in a followed conversationRespond to relevant activityOffer grouping and controls per conversation
A product tipLearn a useful featurePrefer an in-app explanation at the relevant moment
An offer or promotionHear about an optional opportunityMake it a separate, optional category

These are design recommendations, not a requirement to build every category. For a first release, choose the smallest useful set, as described in how to scope an app MVP.

When should you ask for permission?

Ask after a user takes an action that makes the benefit concrete. Someone who has just created a reminder has a clearer reason to consider notifications than someone looking at an unfamiliar welcome screen.

Explain the specific benefit before presenting the permission request. For example: “Get a reminder at the time you choose.” Avoid a broad promise such as “Stay updated”, which leaves the user guessing about future messages.

Android 13 and later use a runtime notification permission for non-exempt notifications, so on those versions the app must ask before it can show them.

Plan the permission journey as part of the feature:

  • Let the user understand or configure the feature first.
  • Explain which notifications it will send.
  • Provide a clear action to enable them and an equally clear way to continue.
  • Request system permission from that action where the platform allows.
  • If permission is declined, keep the feature's current status accessible inside the app.

Do not design repeated requests after every visit. Offer a settings route when the user later chooses a feature that needs notifications. Include permission states in your Android release testing.

How do you separate useful messages from promotions?

Classify a message by its purpose, not by the label your team gives it.

A service update explains something about an action already taken. A promotion asks the user to consider another action for the business's benefit. A discount added to a service update is still promotional content, even if the opening sentence concerns an existing request.

Keep those purposes separate. Let users receive updates about an active booking without also agreeing to offers.

For every category, document:

  • What event makes a message eligible.
  • What the message helps the user do.
  • Whether the user explicitly requested it.
  • Where its setting appears.
  • When it should stop being sent.

Write notification text with the same discipline. State what changed and what action is available. Avoid false urgency, vague curiosity hooks or claims that imply a personal message when none exists.

For sensitive information, design a discreet preview and place the detail behind the app's normal access checks.

How often should you send notifications?

Choose limits around the user's task. There is no useful universal sending schedule for every app.

A reminder should follow the schedule its owner selected. A conversation may need a summary of unread activity. An optional offer can wait if another notification has already interrupted the same person.

Set both category limits and an overall limit. Otherwise, several individually restrained campaigns can still create an excessive combined schedule.

Consider this illustrative example: a user has a reminder, several conversation updates and an optional offer waiting. Send the requested reminder at its chosen time, group eligible conversation activity, and defer the offer. The point is to prioritise the user's intent before filling a campaign calendar.

Also define quiet hours, expiry and duplicate handling. Decide which messages may interrupt quiet hours, and explain those choices in settings. Check whether a queued message is still relevant before sending it. Cancel reminders for completed actions and avoid repeating an update the user has already handled.

What settings should users control?

Offer controls that match reasons people want messages. “Notifications on or off” is too coarse for someone who wants reminders but no promotions.

A practical settings screen might separate:

  • Updates about active requests.
  • Reminders the user schedules.
  • Conversations or followed activity.
  • Offers and product news.

Add controls within a category where they serve a clear need, such as muting one conversation or changing reminder times. Avoid building a large preference screen for categories you do not send.

Use plain descriptions with examples. “Offers and product news” says more than “Engagement”. Make optional promotional choices explicit.

Design the distinction between an in-app preference and system permission carefully. Do not present a category as ready to deliver when the app has observed that system permission is disabled. Provide a clear explanation and a route to the relevant settings.

Test that saved preferences actually control sending, including queued messages and changes made from another signed-in device.

How should you measure opt-outs?

Define each measure before building a dashboard. A category being disabled, system permission being observed as off and a reminder being deleted are different events. Keep them separate.

Record permission requests and responses where observable. Record changes to category preferences. For system permission, report the latest state your app can observe rather than claiming to know the exact moment a user changed it.

Give each measure a clear denominator. A permission acceptance measure should refer to people shown the request. A promotional opt-out measure should identify the promotional audience and the observation window.

Review results by message type and sending frequency. Ask:

  • Did recipients complete the action the message was intended to support?
  • Did category opt-outs rise after a campaign?
  • Are heavily contacted users disabling more categories?
  • Are messages arriving after the underlying action is complete?
  • Are support requests revealing confusing controls?

Treat patterns as investigation leads. A rise in opt-outs after a campaign does not, by itself, prove the campaign caused them.

Agree on a review window before comparing changes. This review belongs in ongoing app maintenance, alongside checking delivery failures and outdated message rules.

What common mistakes should you avoid?

Asking before explaining the benefit. Move the request to a relevant action and make the explanation specific.

Calling every message essential. Write down the user consequence of missing it. If the main consequence is a missed promotion, classify it accordingly.

Optimising only for opens. Review the action completed after opening, alongside opt-outs and complaints.

Stacking messages from separate features. Apply an overall interruption limit, with explicit priority rules.

Keeping stale messages in the queue. Recheck relevance and expiry before sending.

Treating notification delivery as the whole feature. Make the current status available inside the app, and test the experience with permission declined.

Before release, include these cases in your Google Play release checklist. For each message type, verify its trigger, preference control, expiry rule and destination when opened.

What questions come up before launch?

Should every app have push notifications?

No. Add them when there is a clear reason to reach someone outside the app. If the information can wait until the next visit, start with an in-app message.

Should promotional notifications be enabled automatically?

Prefer an explicit, separate choice. Explain the content users are signing up for and make that choice easy to change.

What should happen when someone declines permission?

Keep the app useful. Show relevant updates inside it and provide a settings route if the user later wants notifications. Avoid making unrelated actions depend on accepting permission.

What should we launch first?

Start with the message type most closely tied to a user request. Verify permission handling, preferences, message expiry and opt-out measurement before adding more categories. A notification can open a specific screen; see how to plan mobile app deep links.

Ready when you are

Planning an app of your own?

Tell us where your project is today. We will help you work out the scope before you commit to a budget.