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.

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

Android

Everywhere

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 typeGood moment to ask
Habit / fitnessAfter they set their first reminder time
Messaging / communityAfter they send their first message ("get notified when they reply")
FinanceAfter they set their first budget ("we'll tell you when you're close")
LearningAfter the first lesson ("keep your streak with a daily nudge?")
Support-heavy appsWhen 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

BucketExamplesRules
Useful (transactional)A support reply, a reminder the user set, a friend's message, an order update, a failed paymentSend when it happens. Respect quiet hours unless it's truly urgent.
PromotionalFeature announcements, win-back messages, offers, recommended contentOnly 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

2. Onboarding nudge

3. First-value reminder

4. Paywall follow-up (promotional)

How to handle the conversation itself is in how to talk to users who leave at the paywall.

5. Progress summary

6. Win-back (promotional)

7. Feature announcement (promotional)

The in-app sheet that goes with a release is covered in What's New screens.

8. Billing problem

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 ofWrite
"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:

Step 5: set limits before you need them

Decide these before your first campaign:

LimitA sensible starting point
Promotional pushes per person per day1
Promotional pushes per person per week2 to 3
Quiet hours (local time)9pm to 9am for promotional
Same message to the same personNever twice
Win-back attempts1 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:

Common mistakes

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:

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.