A phone collects dozens of alerts a day, and most people decide quickly which apps get to stay in that stream. A reminder that a 12-day streak ends tonight tells someone about their own progress. A "Come back and see what's new!" message sent to every lapsed user on a Tuesday afternoon tells them nothing.
That difference shapes retention more than most teams expect. For apps chasing award-level engagement, the push channel deserves the same design care as onboarding or the first-run experience.
The Notification Budget Is Smaller Than It Looks
Researchers at Telefonica ran an in-situ study of mobile phone notifications with 15 users and found they handled 63.5 notifications a day on average, mostly from messaging and email apps. People viewed most alerts within minutes, whether the phone was on silent or not. The same study linked a rising number of notifications to more negative emotions.
Every push your app sends lands in that crowded pile, and users read it fast. If it reads as noise, their next tap may well be the settings screen.
Android raised the stakes further. Since Android 13, apps need a runtime permission before they can send most notifications, and Google's notification permission guidance tells developers to let people get familiar with the app before asking. Google's examples of good moments to ask include a user tapping an alert bell or following another account. In each case the person has just shown they want updates about something specific.
Start With an Event, Not a Calendar
Weak push programs run on a marketing calendar. Strong ones run on user behavior: a streak about to break, an achievement just unlocked, a friend who moved ahead on a leaderboard, or three quiet days after a run of daily activity.
Trophy, a gamification platform for consumer apps, builds its push notifications triggered by streaks and achievements around this idea. Streak reminders, achievement alerts and reactivation sequences fire from in-app events in each user's local time zone, and they deliver through Firebase, APNs or Expo. The team at Trophy sums up the goal plainly: "every notification reflects real user activity."
The approach shows up in Trophy's own data. Across 250 million user interactions from 1.5 million people on apps running Trophy, one in five people (22%) who received a streak reminder push about an imminent streak loss kept going. Each of those users was about to lose their progress and came back because the message was about them.
For your own app, list the moments where a user has something to gain or lose right now. Those are your push candidates. Everything else belongs in email, an in-app message or nowhere at all.
Match the Urgency to the Moment
Apple is direct about promotional pushes. Apple's guidance on managing notifications says apps should not send marketing or promotional content through notifications without people's explicit agreement, and should never use the Time Sensitive level for a marketing message. Time Sensitive is for events happening now or within the hour.
A streak that expires at midnight fits that definition. A 20% discount on a premium plan does not. Apple also asks teams to build trust by representing the urgency of each notification accurately, which makes a good test for any message in your queue. Would the user agree it couldn't wait?
Time Zones Decide Whether a Reminder Helps
A streak reminder sent at 8 p.m. New York time reaches someone in Sydney mid-morning, long before their streak is at risk. It reaches someone in London around midnight, when the day is already over. Both messages miss.
Timing varies by day of the week too. Trophy's analysis found Wednesday accounts for 21% of streak losses, three times Sunday's share of just under 7%. A midweek nudge, sent at the user's local time, protects more streaks than a weekend one.
These details are easy to get wrong in a homegrown system. Each user needs their own clock, their own quiet hours and a schedule that survives daylight saving changes.
Give Users Control Over the Channel
People keep notifications switched on when they feel in charge of them. That means separate controls for streak reminders, social updates and product news, plus frequency caps and quiet hours. Apple expects apps that send promotional pushes to offer an in-app settings screen where people can change their choice.
A preference center also tells you something about your content. If most users turn off one category, the messages in that category are the problem.
Measure Pushes Like a Product Feature
Treat each automated sequence as a feature with its own results. Track how many messages were sent, scheduled and suppressed, then compare return rates by trigger and by inactivity window. A reactivation message after three quiet days and one after 30 days serve different users and need different copy.
Keep copy and logic editable without an app release. Teams that can adjust a streak reminder in an afternoon test more ideas than teams waiting on a store review.
Notifications That Earn Their Place
The apps people praise for engagement rarely send the most notifications. They send the ones users would have asked for: a heads-up before progress is lost, a moment of recognition when a goal is reached, a nudge timed to the user's own day.
As operating systems hand people more control over alerts, behavior-based pushes are the ones that will survive the permission prompt. Build them around what users did, and the channel stays open.