---
title: What app developers need to know about sending alerts notifications to users?
description: Learn how to design app push notifications that respect users, earn opt-ins and build trust, covering timing, frequency, permissions and platform rules.
image: https://weareaffective.com/hubfs/learning-centre-images/what-app-developers-need-to-know-about-sending-alerts-notifications-to-users.webp
---

[Skip to content](https://weareaffective.com/learning-centre/what-app-developers-need-to-know-about-sending-alerts-notifications-to-users#main-content)

[![we\_are\_affective\_logo\_200](https://weareaffective.com/hs-fs/hubfs/we_are_affective_logo_200.png?width=175&height=48&name=we_are_affective_logo_200.png "we_are_affective_logo_200")](https://weareaffective.com)

- [Home](https://weareaffective.com)
- About Us 
  
    - [Our Story](https://weareaffective.com/about)
    - [How We Work](https://weareaffective.com/how-we-work)
- Our Services 
  
    - [App Planning & Strategy](https://weareaffective.com/app-planning-strategy)
    - [App Design](https://weareaffective.com/app-design-agency)
    - [App UX Design](https://weareaffective.com/app-ux-design)
    - [App UI Design](https://weareaffective.com/app-ui-design)
    - [App Technical Architecture](https://weareaffective.com/app-architecture)
    - [Existing App Audits](https://weareaffective.com/app-audit)
- [Case Studies](https://weareaffective.com/case-studies)
- [Pricing](https://weareaffective.com/pricing)
- [Learning Centre](https://weareaffective.com/learning-centre)

- [Get Started](https://weareaffective.com/get-started)

Expert Guide Series

# What app developers need to know about sending alerts notifications to users?

 Table of Contents

A user opens your app for the first time, spends three minutes exploring, and then closes it. Two hours later, a notification arrives: "Don't forget to check in!" They had not forgotten. They had simply left. That single notification, sent without context or care, can be the moment they decide the app is not worth the noise.

Push notifications sit at a strange intersection of power and fragility. Used well, they bring users back at exactly the right moment, with exactly the right information. Used poorly, they become the reason someone opens their phone settings and turns you off entirely. According to [Business of Apps](https://www.businessofapps.com/marketplace/push-notifications/research/push-notifications-statistics/), over 71% of users uninstall apps because of intrusive notifications. That figure does not represent a technical failure. It represents [a design failure, a failure to think](https://weareaffective.com/user-psychology-app-design) carefully about what a notification is actually for.

#### Notification Categories Worth Separating

| Type | User-initiated? | Appropriate frequency | Risk if overused |
| --- | --- | --- | --- |
| Transactional (order, booking, payment) | Yes | As needed | Very low |
| Contextual (reminders tied to goals) | Partly | Low to moderate | Low if timed well |
| Engagement (re-engagement, streaks) | No | Low | High |
| Promotional (offers, content) | No | Very low | Very high |

Transactional notifications carry almost no risk because users have created an expectation by taking an action. Promotional notifications carry the highest risk because they serve the product first and the user second. The middle ground, contextual and engagement notifications, is where design judgement is most needed. They can genuinely serve users or [quietly manipulate them depending on how they are built](https://weareaffective.com/learning-centre/how-to-structure-a-behavioural-risk-register-before-you-write-a-single-user-stor).

## Timing, Frequency, and the Threshold of Annoyance

Timing a notification well requires [understanding what a user is likely doing and feeling](https://weareaffective.com/learning-centre/what-a-development-team-actually-needs-to-know-about-the-user-before-sprint-one) at the moment it arrives, and whether your message fits that state.

Sending notifications during a user's preferred time window increases open rates by up to 40%, according to [Wisernotify](https://wisernotify.com/blog/push-notification-stats/). That number suggests users have meaningful time preferences, but it also points to something deeper: a notification that arrives when someone is ready for it feels different from one that arrives mid-meeting or at dinner.

Frequency is the area where apps most quietly damage the relationship without noticing. Only 23% of users consider multiple reminder push notifications per day to be an acceptable frequency, according to [Statista, 2021](https://www.statista.com/statistics/1243276/us-users-opinion-appropriate-app-notifications/). And users who receive more than six push notifications per week from a single brand are 3.4 times more likely to uninstall the app within 30 days, according to [Klaviyo, 2026](https://www.klaviyo.com/).

Build in a mandatory cooldown period between non-transactional notifications. If a user has received a promotional or engagement notification in the last 48 hours, do not send another one regardless of what the campaign schedule says.

A simple internal test: if you would not want to receive the notification at that moment in that context, do not send it. The instinct is a better guide than most engagement dashboards.

## Context-Sensitive Notifications: Matching Messages to the User's Actual State

We built a concierge app for residents moving into a high-end residential block, typically people buying or renting at the top of the market. The temptation with that kind of product is to surface everything at once: recycling schedules, emergency contact numbers, local area guides, building rules. The information is all genuinely useful. The problem is the moment it lands.

Someone who has just moved does not arrive in a calm, information-ready state. Some had just bought their first property. Others were moving after a separation or divorce. The emotional range among new residents was wide, but it had one thing in common: no one was ready to process a directory of building information on day one. We made the deliberate decision to drip-feed notifications over time instead, sending recycling guidance a couple of days after move-in and local area recommendations across the first weekend.

We ran A/B testing with real users to validate this. The users who received delayed, staged notifications reported measurably lower stress levels than those given everything at once. More than that, those notifications were not experienced as interruptions or reminders about something requiring action. They were experienced as timely, helpful information arriving just before it was needed. That shift in emotional register changed the user's relationship with the product entirely.

[Map your notifications to the user's likely emotional state](https://weareaffective.com/learning-centre/why-product-owners-should-write-the-users-second-session-before-the-first-one) at each stage of their journey, not just their functional stage. A user who has just completed onboarding and a user who has been using the app daily for a month are not in the same state, even if they share a behavioural segment.

The principle extends beyond residential apps. [A fitness app sending a workout reminder](https://weareaffective.com/learning-centre/fitness-app-trends-2026-what-users-really-want-from-their-workout-apps) at 6am to a user who has not logged a session in two weeks is ignoring the emotional context of disengagement. That user does not need a push. They need a different kind of contact.

## Why Optimising for Open Rates Undermines User Trust

Open rate is a number that rises if you [write more alarming subject lines, use users' first names](https://weareaffective.com/learning-centre/how-do-i-write-push-notification-messages-that-users-actually-read) in ways that feel invasive, or send at moments of low resistance. Teams that optimise for open rate tend to find their rates climbing while something harder to measure quietly falls: the quality of the user's relationship with the product.

The problem is that open rate measures a behaviour, not a feeling. A user who opens a notification out of anxiety that they are missing something important is not in the same emotional state as a user who opens one because it arrived at the right moment with something genuinely useful. Both count as opens. Only one builds trust.

#### What Open Rate Misses

Forty-two percent of users adjust their notification settings to limit notifications when they receive too many, according to [Statista, 2021](https://www.statista.com/statistics/1242709/us-too-many-push-notifications-users-reaction/). Another 8% delete the app entirely. Neither behaviour shows up as a bounce or a failed open. The notification technically "worked, " it was delivered, perhaps even opened, and yet the net result was a loss of access to the user.

A more honest set of questions to ask about each notification type: Are users who receive this regularly more retained six weeks later? Are they [more likely to rate the app positively](https://weareaffective.com/learning-centre/what-emotional-triggers-make-users-rate-apps-positively)? If the honest answer to either is "we don't know, " the notification strategy has not been properly evaluated.

## Giving Users Granular Control Over What They Receive

Binary notification settings, on or off, are a design failure. They force users who want some notifications but not others into a choice between too much and nothing. Most will eventually choose nothing, which is a worse outcome than a more thoughtful control structure would have produced.

The goal is to let users specify what they actually want. Not "do you want notifications?" but "which of these do you want, and how often?" A user who wants order updates but not promotional offers should be able to say so. A user who wants weekly summaries but not daily reminders should have that option.

#### Building a Preference Centre

1. Group notifications by type with plain-language descriptions of what each does.
2. Let users set frequency preferences, not just on/off, for each category.
3. Make the preference centre easy to find, not buried in a sub-menu of settings.
4. Revisit preferences after significant product changes that alter the notification landscape.

This approach requires more design and development effort upfront. It pays back in retention. [Users who feel they have shaped their experience](https://weareaffective.com/learning-centre/why-do-some-apps-feel-like-they-were-made-just-for-you) with a product stay longer and engage more honestly, because the relationship is on their terms rather than yours.

Surface the notification preference centre immediately after a user disables notifications through the system settings. That moment is when they are clearest about what they do not want. Offering granular control then, rather than accepting a total opt-out, recovers a relationship that would otherwise be lost.

## How to Audit Whether Your Notifications Serve Users or Just the Algorithm

There is a simple framework we use to evaluate whether a notification strategy is genuinely user-serving or quietly optimised for platform metrics. It starts with a question about each individual notification type: is this notification there because the user needs this information at this moment, or is it there to pull them back into the app for the product's benefit?

The follow-on question is equally direct: can a user reduce the frequency of this notification without losing anything genuinely valuable from the product? If the answer is yes, the current cadence is higher than user benefit requires. It is there to serve retention numbers, not users.

The removal test is the most revealing of all. Ask your team: [what happens to engagement if we turn this notification off](https://weareaffective.com/learning-centre/5-things-that-make-the-difference-between-so-so-apps-and-stellar-apps-what-your-) for a segment of users for 30 days? If the instinctive response is "we would never do that, " that reaction tells you something. A feature the team will not test is a feature the team already suspects serves the product more than the user. The reluctance is the answer.

Run through each notification type in your product and apply all three questions. The ones that survive all three are the ones worth keeping. The ones that fail even one deserve a redesign before they go out again.

## Platform Rules and Technical Constraints Developers Must Know

Notification design does not happen in a vacuum. Both Apple and Google impose rules that determine what you can send, how you can send it, and what happens if you abuse the system.

Apple's guidelines require that notifications be directly relevant to the user's relationship with the app. Marketing notifications require explicit opt-in to the "promotional" category under iOS settings. Using notifications to deliver advertising without that consent violates App Store guidelines and risks app removal.

#### Key Platform Constraints to Build Around

- iOS limits background app refresh, which affects how reliably silent notifications can update content.
- Android 13 and above requires a runtime permission prompt, matching the iOS model more closely.
- Both platforms can throttle delivery if your notification volume triggers abuse detection.
- Notification grouping (threads on iOS, channels on Android) affects how your messages appear in the tray.

Android's channel system, introduced in Android 8, lets users control notifications at the channel level through their device settings. This means users can silence your promotional channel while keeping transactional notifications on. Designing your notification architecture around named channels is both good UX and good technical practice: it puts control where users expect it and reduces the likelihood of a full opt-out.

## Measuring Notification Performance Beyond Click-Through Rate

A click-through rate of 2-5% is a common benchmark for push notifications, according to [Mobiloud](https://www.mobiloud.com/blog/push-notification-statistics). That range tells you almost nothing useful on its own. A 5% CTR on a notification that erodes trust is worse than a 2% CTR on one that deepens it.

Better measurement looks at behaviour after the click and at what happens to users who receive a notification type over time compared to those who do not. Relevant signals include session length following the notification, retention at 7, 14, and 30 days for users segmented by notification type, and opt-out rates correlated to specific campaigns.

#### Metrics Worth Tracking Alongside CTR

| Metric | What it tells you |
| --- | --- |
| Session depth after click | Whether the notification delivered on its promise |
| Notification opt-out rate | Whether frequency or type is generating friction |
| 30-day retention by notification segment | Whether notifications are sustaining or harming long-term engagement |
| App store rating trend | Whether sentiment is shifting after notification changes |

Personalisation matters too. Personalised push notifications have four times higher open rates than generic ones, according to [Leanplum via iZooto](https://izooto.com/blog/best-time-of-day-to-send-push-notifications). But personalisation at scale requires behavioural data that is used respectfully. A notification that feels personally targeted is powerful. One that reveals you have been watching more closely than users expected has the opposite effect.

## Conclusion

Notifications are a conversation. Every message you send is a turn in that conversation, and users are deciding with each one whether to keep talking. The mechanics of push delivery are straightforward. The design judgement required to use them well is considerably harder.

The concierge app work showed us something that has stayed with us: when you match a notification to a user's actual emotional state, rather than just their functional stage in a funnel, the whole relationship with the product changes. Users stop feeling managed and start feeling supported. That shift is worth far more than any short-term improvement in open rate.

The practical steps are clear enough. Ask permission in a way that explains the value. Give users granular control over what they receive. Time your messages to emotional context, not just behavioural triggers. Audit regularly using the removal test, and retire anything that fails it. Measure what happens after the click, not just whether the click happened.

None of this requires sacrificing engagement. It requires being honest about what engagement actually means. A user who opens an app because a notification earned that visit is worth considerably more than one who opens it out of anxiety, habit, or a fear of missing out on a streak. Building for the former takes more care. It also builds something that lasts.

If you want to think through how your notification strategy sits against these principles, [let's talk about your app's notification design](https://weareaffective.com/get-started).

## Frequently Asked Questions

Why do push notifications cause users to uninstall apps?

Over 71% of users uninstall apps because of intrusive notifications, which points to a design failure rather than a technical one. When notifications arrive without context or relevance, users experience them as noise rather than value, and removing the app becomes the simplest solution.

What are the different types of push notifications and how risky is each one?

The four main types are transactional, contextual, engagement, and promotional notifications. Transactional notifications carry very low risk because users have already taken an action that creates an expectation, while promotional notifications carry the highest risk as they serve the product before the user.

How often is it acceptable to send push notifications to users?

Only 23% of users consider multiple reminder notifications per day to be acceptable, so frequency should be kept low for non-transactional messages. Users who receive more than six push notifications per week from a single brand are 3.4 times more likely to uninstall the app within 30 days.

Does the timing of a push notification actually affect how users respond to it?

Yes, sending notifications during a user's preferred time window can increase open rates by up to 40%. A notification that arrives when someone is ready for it feels considerate, while one that interrupts a meeting or a meal feels intrusive, even if the content is identical.

What is a cooldown period and should developers be using one?

A cooldown period is a mandatory gap between non-transactional notifications sent to the same user. If a user has already received a promotional or engagement notification within the last 48 hours, best practice is to hold the next one regardless of what the campaign schedule dictates.

How can developers tell whether a notification is worth sending?

A practical internal test is to ask whether you would want to receive that notification yourself, in that moment and context. If the answer is no, the notification should not be sent, as the discomfort you imagine the user feeling is likely accurate.

What makes contextual and engagement notifications different from other types?

These two categories sit in the middle ground where design judgement matters most, because they can either genuinely serve users or quietly manipulate them depending on how they are built. Unlike transactional notifications, they are not directly prompted by a user action, which means the intent and execution behind them carry greater responsibility.

What is the biggest mistake app developers make with push notifications?

The most common mistake is damaging the relationship through excessive frequency without realising it is happening. Apps that send too many notifications too often train users to associate the app with interruption rather than value, which leads to opt-outs and uninstalls that could have been avoided.

## Related Articles

[![We Are Affective](https://weareaffective.com/hubfs/we_are_affective_logo_mark.svg)](https://weareaffective.com)

20-22 Wenlock Road  
London, N1 7GU  
United Kingdom

+44 20 4572 8062  
[hello@weareaffective.com](mailto:hello@weareaffective.com)

<https://linkedin.com/company/weareaffective> <https://instagram.com/weareaffective> <https://facebook.com/weareaffective>

Services

[App planning & strategy](https://weareaffective.com/app-planning-strategy) [App design](https://weareaffective.com/app-design-agency) [App UX design](https://weareaffective.com/app-ux-design) [App UI design](https://weareaffective.com/app-ui-design) [App technical architecture](https://weareaffective.com/app-architecture) [Existing app audits](https://weareaffective.com/app-audit)

Legal

[Privacy policy](https://app.termly.io/policy-viewer/policy.html?policyUUID=b8fa9921-7518-4fb5-8ddd-9dc7f5977ed2) [Terms](https://app.termly.io/policy-viewer/policy.html?policyUUID=8b6a6ad5-91bd-4176-a5f7-6d36b0398f70)

Case studies

[TravAI](https://weareaffective.com/case-studies/travai) [Meditech](https://weareaffective.com/case-studies/harley) [WorkingWeight](https://weareaffective.com/case-studies/workingweight) [SkinSync](https://weareaffective.com/case-studies/skinsync) [Three Lochs](https://weareaffective.com/case-studies/three-lochs) [Drift](https://weareaffective.com/case-studies/drift)

About us

[Our Story](https://weareaffective.com/about) [How We Work](https://weareaffective.com/how-we-work)

Guides

[Creating an app](https://weareaffective.com/how-to-create-an-app) [Building an MVP](https://weareaffective.com/building-an-mvp) [Cost and budgeting](https://weareaffective.com/app-development-cost) [App technology](https://weareaffective.com/app-development) [Planning and strategy](https://weareaffective.com/app-planning-strategy) [User research](https://weareaffective.com/app-user-research) [Onboarding design](https://weareaffective.com/app-onboarding-design) [User psychology](https://weareaffective.com/user-psychology-app-design) [Launch and growth](https://weareaffective.com/app-launch-growth)

 Copyright © 2026, weareaffective.com. All rights reserved.