Push notification strategy for indie apps: re-engagement that doesn't get you muted
Push is the only marketing channel that lands on your user's lock screen. It's also the easiest one to lose. Send three pointless notifications and people turn yours off, and from then on you can't reach them even when you have something they'd want.
This guide is for small teams and solo founders. It covers how to earn the permission in the first place, the platform rules you have to follow, a set of re-engagement campaigns with example copy, and the limits that keep you from being muted.
Hailbell is our product, built and run by one developer, Vidur Saini, and it sends push. The section on where it fits is near the end; the strategy works with any push provider.
What the numbers say about opt-in
Before strategy, a reality check on how many of your users you can reach at all.
- Business of Apps reports push opt-in rates of about 53% on Android and 49% on iOS in 2025, with Android down sharply since 2021.
- Android's drop has a clear cause. On Android 13 and later, an app's notifications are off by default for new installs until the app asks for the
POST_NOTIFICATIONSpermission and the user grants it. - Timing matters too. The same Business of Apps summary reports open rates falling through the day, from 5.1% at 8am to 3.2% by 11pm.
So roughly half your users will say yes if you ask well. Every push you send either justifies that yes or wastes it.
The rules you have to follow
Apple
- Consent for marketing. App Review Guideline 4.5.4 says push notifications should not be used for promotions or direct marketing purposes unless customers have explicitly opted in through consent language shown in your app, and that you must give users a way in the app to opt out. The same guideline says push must not be required for the app to work, and shouldn't carry sensitive personal information.
- Interruption levels. Every non-communication notification on iOS has an interruption level: passive, active (the default), time sensitive or critical. Apple's guidance says to use Time Sensitive only for things happening now or within an hour, and never for marketing. Critical needs a special entitlement.
- No repeats. Apple's HIG says to avoid sending multiple notifications for the same thing, even if someone hasn't responded, because people may turn off all your notifications.
- Provisional authorization. iOS lets you send notifications quietly on a trial basis without asking first. They go to Notification Center only, with buttons to keep or turn them off. It's an option for apps whose notifications prove their value once seen.
Android
- Runtime permission on Android 13+. If your app targets Android 13 or higher, you control when the permission dialog appears. Google's guidance is to ask in context, and to show an explanation first if
shouldShowRequestPermissionRationale()returns true (Android developers). - Channels. Android lets users turn off notifications per channel. Create separate channels (for example "Replies," "Reminders," "Tips and offers") so someone who's tired of tips can turn those off without losing replies.
Everywhere
- Respect local law on marketing messages where your users live.
- Make opt-out easy inside the app, in settings, with separate switches for promotional and useful notifications.
Step 1: earn the permission
Don't ask on first launch
Apple's own example is a task app that asks after the person schedules their first task, because the purpose is clear then. Find the equivalent moment in your app:
| App type | Good moment to ask |
|---|---|
| Habit / fitness | After they set their first reminder time |
| Messaging / community | After they send their first message ("get notified when they reply") |
| Finance | After they set their first budget ("we'll tell you when you're close") |
| Learning | After the first lesson ("keep your streak with a daily nudge?") |
| Support-heavy apps | When they send a support message ("we'll notify you when we reply") |
Use a pre-permission screen (honestly)
A short screen before the system dialog, explaining what they'll get, gives people a reason to tap "Allow." Keep it honest: list the notifications you'll actually send. Include a "Not now" button that doesn't trigger the system prompt, so you can ask again later at a better moment. On iOS, the system dialog only appears once: Apple notes that later authorization requests don't prompt the person, so after a "Don't Allow" the user has to go to Settings.
Example copy:
Get a nudge when it matters
• A reminder at the time you pick
• Your weekly progress on Sundays
• Replies from our team when you ask for help
No spam. Change it any time in Settings.
[Turn on notifications] [Not now]
Ask separately for marketing
If you'll send promotional pushes (offers, feature announcements, content you recommend), you need explicit consent on iOS under 4.5.4. A simple toggle in onboarding or settings works: "Send me tips, new features and occasional offers." Default it to off, or show it as a clear choice. Keep a record of who opted in.
Step 2: sort your notifications into two buckets
| Bucket | Examples | Rules |
|---|---|---|
| Useful (transactional) | A support reply, a reminder the user set, a friend's message, an order update, a failed payment | Send when it happens. Respect quiet hours unless it's truly urgent. |
| Promotional | Feature announcements, win-back messages, offers, recommended content | Only to people who opted in. Capped. At a good local time. |
Many apps get muted because they blur the two: a "reminder" that's really an ad. Keep them separate in your code, your channels and your caps.
Step 3: eight campaigns worth starting with
Start with triggered messages (sent because of something the user did or didn't do) rather than broadcasts to everyone. Each needs a trigger, a delay, a cap and a destination.
1. Support reply
- Trigger: you reply to a chat after the user left the app.
- Copy: Title: "[App] Support" / Body: "We replied: [first line of your reply]"
- Opens: the conversation.
- Why it works: they asked for it. This is the most welcome push most apps can send.
2. Onboarding nudge
- Trigger: started onboarding, didn't finish, 24 hours passed.
- Copy: "You're one step away from [first result]. It takes about a minute."
- Opens: the exact step they stopped at.
- Cap: once.
3. First-value reminder
- Trigger: finished onboarding but hasn't done the core action after 2 days.
- Copy: "Try this: [specific action] takes 30 seconds and [benefit]."
- Opens: the action.
4. Paywall follow-up (promotional)
- Trigger: closed the paywall without buying, 24 hours later, at the hour they usually open the app.
- Copy: answer the most common question rather than pushing a deal. "Yes, you can cancel the trial any time in Settings. Here's what Pro includes."
- Opens: the paywall.
- Cap: once per week; cancelled if they buy first; opted-in users only.
How to handle the conversation itself is in how to talk to users who leave at the paywall.
5. Progress summary
- Trigger: weekly, for people with activity.
- Copy: "This week: 4 workouts, 2 more than last week." Real numbers only.
- Opens: the summary.
- Why it works: it's about them.
6. Win-back (promotional)
- Trigger: no opens for 14 days, opted in.
- Copy: lead with something new or useful since they left. "New since you last checked: [feature]. [One-line benefit]."
- Opens: that feature.
- Cap: one. If they don't come back, stop. Don't send a second "we miss you."
7. Feature announcement (promotional)
- Trigger: a release with something users can see, sent to opted-in users who haven't opened since.
- Copy: the benefit, not the version number. "Your streak now pauses while you travel."
- Opens: the feature.
The in-app sheet that goes with a release is covered in What's New screens.
8. Billing problem
- Trigger: a renewal failed.
- Copy: "Your [App] renewal didn't go through. Tap to see how to update your payment."
- Opens: an in-app message with steps.
- Note: don't put card or payment details in the notification. Apple's 4.5.4 says push shouldn't carry sensitive information.
Where these moments sit in a churn plan is in reducing app churn with in-app support.
Step 4: write pushes people want to open
Apple's HIG asks for concise, informative notifications, and notes the system already shows your app icon, so you don't need your app name in the text.
| Instead of | Write |
|---|---|
| "Don't forget to check out the app!" | "Your 7-day streak ends tonight. 5 minutes keeps it." |
| "New update available!" | "Search now finds photos by what's in them." |
| "We miss you 😢" | "3 new recipes match what you saved last month." |
| "Special offer just for you!!!" | "Yearly is now available. Here's what's included." |
| "Hey there, open the app" | "Your report for October is ready." |
Rules of thumb:
- One message, one action. The tap should open the exact screen the push mentions.
- Use real data. Names, numbers, the thing they saved. Generic copy reads like spam.
- Personalize carefully. "{{first_name}}" with no fallback becomes "Hi ," in production. Always set a default.
- Don't tell people to do tasks. Apple's HIG notes that instructions are hard to remember after dismissing a notification. Link to the task instead.
Step 5: set limits before you need them
Decide these before your first campaign:
| Limit | A sensible starting point |
|---|---|
| Promotional pushes per person per day | 1 |
| Promotional pushes per person per week | 2 to 3 |
| Quiet hours (local time) | 9pm to 9am for promotional |
| Same message to the same person | Never twice |
| Win-back attempts | 1 per lapse |
Send in each user's local time zone. A "good morning" push at 3am because your server runs on UTC is how you get muted.
Step 6: measure the cost, not just the opens
Open rate is the vanity metric of push. Track:
- Opt-out and disable rate per campaign. If a campaign causes notification disables, it's costing you future reach even if opens look good. On iOS you can check authorization status on launch; on Android you can check whether notifications are enabled per channel.
- Downstream action. Did the person do the thing the push was about?
- Uninstalls after campaigns. A spike after a broadcast is a warning.
- Opt-in rate over time, by the moment you ask. Compare your number with the ~49% iOS and ~53% Android rates above.
Common mistakes
- Asking for permission on first launch with no context.
- Sending marketing to people who only agreed to reminders.
- Broadcasting the same message to everyone at the same UTC time.
- Using Time Sensitive for a sale.
- A chain of three "come back" messages.
- Pushes that open the home screen instead of the content.
- Badges that show stale counts. Apple's HIG says badges should only show unread notifications and be kept up to date.
Where Hailbell helps
Hailbell is in-app support chat and push for iOS, Android and the web, in one SDK. For push strategy, that means:
- Local time and variables. Write a campaign once with variables like
{{first_name|there}}, city, local weather and today's occasion, and each person gets it at the hour you pick in their own time zone. - Opt-in and caps built in. Promotional pushes are opt-in, marketing sends skip people who opted out, and there are quiet hours and a daily cap per person, counted across iOS, Android and web.
- Support replies as push. When you answer a chat after the user left, they get a push titled "[App] Support" that opens the conversation.
- Follow-ups you turn on. A paywall follow-up is off until you enable it. Your app records the close, the push goes at the hour that person usually opens the app, only to people who allowed promotional pushes, and it is cancelled if they buy first. A failed renewal from Superwall or RevenueCat can put a message you wrote in the chat during their daytime, and is skipped if the payment recovers. That one stays off until you turn it on too.
- One campaign, every platform. Send to iOS, Android and web at once, with one push per signed-in person.
It's built for small teams that want push and support in one place; if you need complex multi-channel journeys across email and SMS, a dedicated lifecycle tool fits better. Pro is $29 a month for 10,000 monthly active users, with push included, a 14-day free trial, no card needed, and a 14-day money-back guarantee on the first payment if AI replies used less than 20% of the monthly allowance. Try Hailbell.
Questions
What is a good push notification opt-in rate?
Business of Apps reports 2025 opt-in rates of about 49% on iOS and 53% on Android. Asking in context, after a clear explanation, is the most reliable way to beat your own baseline.
How many push notifications should an app send?
There's no universal number. A safe start is at most one promotional push per person per day and two or three per week, with useful notifications (replies, reminders the user set) sent when they happen. Watch disable rates and adjust.
Do I need permission to send marketing push notifications on iOS?
Yes. Apple's guideline 4.5.4 requires explicit opt-in through consent language in your app before you send promotional or direct marketing pushes, and a way to opt out in the app.
When should I ask for push notification permission?
At the moment the value is obvious: after the user sets a reminder, sends a message or asks for support. Avoid asking on first launch, when people don't yet know what your notifications will be for.
What's the best time to send push notifications?
When your users usually open the app, in their own time zone. Business of Apps' summary of push data shows open rates falling through the day, but your own app's usage pattern is the better guide.
Send pushes people are glad to get. Hailbell gives you push at each user's local time, opt-in and caps built in, plus in-app support chat, for iOS, Android and web. Try it free for 14 days.
Questions about a push campaign? Start a chat with us.