The Complete App Push Notifications Guide (That Won't Annoy Your Users)
Push notifications are the most direct channel you own. This app push notifications guide explains how they work, why they beat email and social, and how to use them without spamming.
How push notifications actually work
A push notification isn't sent directly from your server to a phone. On iOS your app registers with Apple Push Notification service (APNs); on Android it registers with Firebase Cloud Messaging (FCM). Each install receives a unique device token, which your backend stores. When you want to reach a user, you send the message plus that token to APNs or FCM, and Apple or Google delivers it to the device — even when the app is closed.
Two things follow from this. First, you need a real native app to hold that token; a plain website can't register with APNs. Second, the user must grant permission. Once they do, you can deliver a title, a body, an icon, and a deep link that opens a specific screen. Transform To APP wires push into every app it builds — the token registration, the bridge to your website, and the deep link handling — so you send messages without touching native code.
Why push beats email and social reach
Email inboxes are crowded and open rates are unpredictable; a promotion can sit unread for days or land in spam. Social reach is rented, not owned — an algorithm decides how many of your followers see a post, and that share keeps shrinking. Push is different: it lands on the lock screen of someone who chose to install your app, with no gatekeeper deciding whether it arrives.
That directness is the strength and the responsibility. Because a push interrupts, it earns attention email rarely gets — ideal for time-sensitive, personally relevant messages. But the same interruption is why a careless blast gets your app muted or deleted. Treat push as a premium channel for messages that genuinely help the reader right now — an order is ready, a wishlisted item is back — not as a cheaper megaphone for everything you'd have emailed anyway.
Earn the opt-in (don't ask on first launch)
The fastest way to lose the channel is to fire the system permission prompt the second the app opens. A cold user has no reason to say yes, and on iOS a decline is close to permanent — the prompt won't show again, and re-enabling means digging through Settings. You usually get one clean ask.
So earn it. Let people use the app first, then ask at a moment where notifications obviously pay off: after a purchase (to get shipping updates), when they favorite an item (to hear about restocks or price drops), or on an order-tracking screen. Show a friendly in-app explainer ("Want a ping when it ships?") before the real system dialog, so the OS prompt only appears for people already inclined to accept. Note that Android 13 and later also require this runtime permission, so the same earn-it approach now applies on both platforms.
Timing and frequency that respect the reader
Frequency is where most programs go wrong. There's no universal magic number, but the honest test is simple: would this specific message be welcome on this person's lock screen right now? If you're padding a schedule to "stay top of mind," you're training users to swipe you away — or worse, to disable notifications entirely.
Timing matters as much as count. Respect time zones so a 9 a.m. offer doesn't arrive at 3 a.m. Send transactional messages (order shipped, ready for pickup) instantly, because their value is the immediacy. Send promotional messages when the reader can act — around lunch, early evening, weekends for leisure categories — and avoid firing the same campaign to everyone at the identical second. When possible, give users control over categories, letting them keep order updates while muting marketing. A smaller, respected list outperforms a large, annoyed one.
Segmentation: send less, mean more
Blasting an identical message to your whole list is the fastest route to the mute button. Segmentation means sending a message only to the people it actually fits, using signals you already have: what someone browsed, bought, or favorited; their language or country; whether they're a first-time visitor or a loyal repeat customer; how recently they opened the app.
Start simple and behavior-based. A restock alert should go only to people who viewed or wishlisted that product. A win-back message belongs to users who haven't opened the app in 30 days, not to someone who bought yesterday. Personalize the content too — a name, the exact item, the actual order number — and always attach a deep link so the tap lands on the relevant screen, not a generic home page. Relevance is the whole game: fewer, sharper notifications beat frequent, generic ones every time.
Real playbooks: cart, restock, offers, order-ready
Concrete beats theory. Abandoned cart: if someone adds to cart and leaves, wait an hour or two, then send "Still thinking it over? Your cart is saved" with a deep link straight back to checkout — one reminder, maybe a second a day later, then stop. Restock: "Back in stock: [item]" to everyone who wishlisted or viewed it while sold out; this is often the highest-converting push you can send because the intent is already there.
Offers: keep them targeted and time-boxed — "Members-only: 20% off today" to a segment that buys the relevant category, not the whole base. Order-ready and shipping: "Your order is ready for pickup" or "Shipped — track it here" are pure service, delivered instantly, and they build the trust that makes people keep notifications on. Notice the pattern: every example is timely, specific, and genuinely useful to the person receiving it.
FAQ
Do users have to accept notifications for push to work?+
Yes. Both iOS and Android 13+ require the user to grant notification permission. If they decline, you can't send push to that device, and on iOS re-enabling means going into Settings. That's why you should ask at a helpful moment, not on first launch.
Can a website send push notifications without an app?+
Only in a limited way. Web push exists but is inconsistent across browsers, and on iOS it requires the user to add your site to the home screen first. A real native app registers with APNs or FCM and reaches the lock screen reliably — one reason to turn your site into an app.
How many push notifications should I send per week?+
There's no fixed number. Send when you have something genuinely useful or timely, not to fill a calendar. Transactional messages (order ready, shipped) can be as frequent as events occur; marketing should be sparing. Let users mute categories, and watch your opt-out rate.
Do I need my own Apple and Google developer accounts?+
Yes, and that's a good thing — your app is published under your brand. The Apple Developer Program costs 99 USD per year and a Google Play developer account is a one-time 25 USD fee. Transform To APP publishes the app under your accounts and handles the technical setup.
What makes a push notification feel spammy?+
Irrelevance, bad timing, and volume. A generic blast to everyone, a marketing ping at 3 a.m., or the fifth "don't miss out" of the week all push people toward the mute button. Segment by behavior, respect time zones, and only interrupt when the message helps the reader.