ASOhack
Back to Blog
Growth Hacks

Push Notification Best Practices for Mobile Apps (2026)

How to use push notifications without burning your audience — permission rates, frequency, segmentation, and the data on what works in 2026.

ASOhack TeamMay 19, 20266 min read

Push notifications are the highest-leverage retention tool indie devs have access to — and the easiest one to break. One bad notification campaign and your opt-out rate doubles overnight.

This is the working playbook for push notifications in 2026, including the permission grants, segmentation, frequency, and copy patterns that actually move retention.

Permission rates: the baseline

iOS users grant push permission at:

  • ~30% when asked on launch (no context).
  • ~50% when asked after first value delivery, with context.
  • ~65%+ when asked at a moment that makes notification feel useful ("Tomorrow's reminder — turn on notifications").

Android (until Android 13): permission was automatic. From Android 13+, opt-in is required and rates are similar to iOS.

If your permission rate is below 40%, the issue is when you ask, not how often.

The 4 notification types

Different rules apply to each:

1. Transactional

Order confirmations, password resets, payment receipts. Highest opt-in tolerance. Users expect these.

Rule: send 100% of the time when triggered, no batching, no marketing copy.

2. Re-engagement

"You haven't checked your portfolio in a week." "Your friend posted." "Streak about to end."

Rule: target inactive users (>3 days inactive for most apps). Cap at 1-2 per week. Make them feel personally relevant.

3. Recommendation / Update

"New feature: collaborative editing." "New course available."

Rule: send sparingly (1-2 per month). Segment by relevant cohort.

4. Marketing / Promo

"50% off Pro this weekend." "Refer a friend, both get rewards."

Rule: maximum 1 per month for general audience, 1 per week for actively engaged. The first promo notification permanently affects permission rate — make it count.

Frequency limits

A working cadence for most consumer apps:

User cohortMax notifications/week
Highly active (>3 sessions/week)3-5
Moderately active (1-3 sessions/week)1-2
Inactive (no session in 7+ days)1
Dormant (no session in 30+ days)1 every 2-4 weeks

Exceed these and opt-outs spike. The drop from 60% permission to 30% permission is permanent — you can't get it back.

The copy that converts

Pattern 1: personal + actionable

✅ "Sara, you logged 4 workouts this week. Lock in the 5th by 8pm?"
❌ "Keep up your streak!"

Pattern 2: scarcity (used carefully)

✅ "Your free trial expires in 24 hours. Save 30% if you upgrade today."
❌ "Limited time offer inside!"

Pattern 3: relevance

✅ "AAPL is up 3% today — your portfolio reacted."
❌ "Market update."

Pattern 4: emoji selectively

A single relevant emoji at the start can lift open rates 10-20%. Five emojis in a row tank credibility.

✅ "🎯 You're 2 habits away from a 30-day streak."
❌ "🔥💪🚀 LEVEL UP YOUR FITNESS NOW 🔥💪🚀"

Timing

The right time depends on your category:

  • Productivity / habit apps: morning (7-9am local).
  • Social / messaging: lunch + evening (12pm, 6pm local).
  • Shopping / e-commerce: evening (6-9pm local).
  • News / content: early morning (6-8am local).
  • Fitness: early morning OR right before user's typical workout (you should know this from app usage).
  • Sleep / meditation: evening (8-10pm local).

For most apps, avoid late-night (11pm-6am local). Even users who don't read it that night will associate the app with disruption.

Most push platforms (OneSignal, Firebase, Customer.io, etc.) have time-zone-aware sending. Use it.

Segmentation

Critical segments for indie apps:

By engagement

  • Heavy users (daily): your power users. Few notifications, mostly transactional + new features.
  • Regular users (weekly): the main retention battleground. Re-engagement nudges work.
  • Lapsed (30+ days): win-back notifications. Lower frequency, higher relevance.

By lifecycle

  • New (D1-D7): onboarding nudges, get-started prompts.
  • Trial (active subscription apps): trial-ending warnings, value reminders.
  • Subscribed: feature usage, retention.
  • Churned: win-back.

By behavior

  • Goal-set users: progress nudges.
  • Goal-unfinished users: encouragement.
  • Specific feature users: feature-specific tips.

Even basic segmentation (active vs lapsed) outperforms blast notifications by 2-3× on retention impact.

What never works

  • Generic "We miss you" — universally weak.
  • "Open the app" with no reason — opt-outs spike.
  • Blast notifications to all users — high cost, low benefit.
  • Multiple per day — even for engaged users, this is overkill.
  • Drip campaigns timed to your team's working hours — users get fired-from-meeting notifications.
  • Vague urgency ("Don't miss out!") — no specific reason.

The unsubscribe asymmetry

When users disable push permission:

  • iOS: in Settings → AppName → Notifications.
  • Android: in Settings → Apps → AppName → Notifications.

Almost no users return. Treat your permission grant as a one-time resource. Once lost, gone.

Mitigation:

  • Allow users to mute categories within your app ("Don't send marketing, do send re-engagement").
  • Make it easy via in-app preferences, not iOS Settings.
  • Some users who'd disable all notifications will keep some on if you give them the option.

Tracking the right metrics

  • Permission grant rate: % of users who allow notifications.
  • Open rate per notification: ideally 5-15% per send.
  • Conversion rate per notification: did the user do the thing you wanted (open trial, complete action)?
  • Opt-out rate by campaign: critical. If a campaign causes >2% opt-out, kill it.

The opt-out rate is the single most important metric because the loss is permanent.

Tools

For indie apps:

  • OneSignal free tier (up to 30k users + unlimited notifications). Solid default.
  • Firebase Cloud Messaging free. Reliable but lower-level.
  • Customer.io / Iterable paid, for more advanced segmentation. Justify when scaling.

Common mistakes

  • Asking permission on launch. Cuts grant rate in half.
  • No segmentation. Blast sends destroy engagement long-term.
  • Generic copy. "Open the app" content is rejected by users.
  • Wrong time zone. Push platforms handle this — configure it.
  • Treating push as marketing channel. It's retention. Marketing is email or in-app.
  • No A/B testing copy. Easy win missed.

Try the tools

Ready to Optimize Your App Store Listing?

Try our free ASO tools — no signup required.