Mobile push · FCM + APNs
Most people install your app, open it twice, and forget it. Mobile push is how you win them back — a tap on their lock screen that reopens the order they abandoned, the cart they left, or the offer they missed. ReachBell reaches Android phones through FCM (Firebase Cloud Messaging, Google’s free pipe to Android devices) and iPhones through APNs (Apple Push Notification service, Apple’s equivalent) — both wired into the same campaigns, segments, and analytics as your web push. Upload your keys once and stop maintaining two notification systems. Built in India, billed in INR with GST invoices.
Write one notification, send it to every app user — Android through FCM, iPhone through APNs. No separate campaigns, no copy-pasting between two tools. Route iPhones through Firebase if that’s already your stack, or talk to Apple directly with your .p8 key — both are first-class paths.
Fire instant pushes the moment something happens — “Order shipped,” “Payment received,” “Your food order is 5 mins away.” One API call finds the user by your own ID and lands on whichever phone they used last, in seconds.
Send shared content, then let each platform shine: group order updates into an Android “notification channel” users can mute on their own, set iPhone urgency levels so OTP-style alerts cut through Do Not Disturb, and add custom sounds — all without rewriting the campaign.
Every device has a “token” — a unique address the app gets when a user allows notifications. When someone uninstalls, that address goes stale. ReachBell spots dead tokens on every send, drops them automatically, and keeps your reported delivery rate honest instead of inflated.
Upload your Firebase service-account file and Apple .p8 key once. Both are encrypted at rest with AES-256-GCM and never handed back out by any API — so your sending credentials can’t leak through ReachBell.
Frequency caps, quiet hours, and preference-center opt-outs apply across web, Android, and iPhone at once. A user who taps “stop deal alerts” is respected everywhere — one policy, no leaks, no angry 11pm pushes.
No SDK to rip out, no notification code to rewrite. Your app already asks users for permission and gets a device token in return — keep doing exactly that. Hand each token to ReachBell with one API call, and we take over the hard parts: who to message, when to send, retries when a phone is offline, and which taps turned into opens. Your developers wire it in once; your marketing team runs campaigns from the dashboard forever after.
9:41
Your order #4821 is on the way — arrives tomorrow.
How it works
No SDK wrestling, no DevOps tickets — most teams finish setup before their chai goes cold.
Drop your Firebase service-account file (for Android) and Apple .p8 key (for iPhone) into Project Settings. We check them on the spot and encrypt them at rest — no fiddly server config.
When a user allows notifications, your app gets a device token. Pass it to POST /subscribers with tokenType fcm or apns — one call, from your app or backend. That’s the only code change.
Write a title and message, pick a segment (or everyone), and hit send. Android and iPhone go out together, quiet hours and caps apply automatically, and you watch opens roll in live.
FAQ
Everything teams usually ask before switching. Something missing? Email us — a human replies.
They’re just the two delivery pipes phones use. FCM (Firebase Cloud Messaging) is Google’s free service for getting notifications onto Android phones. APNs (Apple Push Notification service) is Apple’s equivalent for iPhones and iPads. You don’t have to learn either one — ReachBell talks to both for you. You upload your keys once, and we pick the right pipe for each user automatically.
Yes — that’s the whole point. Android goes through Firebase Cloud Messaging using your service account. iPhone can go through Firebase too, or straight to Apple with your .p8 key — whichever matches how your app is already set up. One campaign reaches both.
Yes. ReachBell works with the device tokens your app already collects when users allow notifications. You add exactly one API call to register each token with us — no SDK to swap, no rewrite of how your app shows notifications. A developer can wire it up in an afternoon.
Anything from a one-off campaign to an instant alert. A D2C brand might send “Flat 30% off ends at midnight — your size is back in stock 👟”. A food app sends “Your order is 5 mins away 🛵”. A fintech app sends “₹2,400 credited to your account”. A news app sends “Breaking: …”. You can personalise each one with merge tags like {{name}} or {{city}} so it reads “Rahul, your Mumbai order shipped.”
Call POST /transactional/send with your own user ID (the one you set via identify) and the message — for example the moment an order ships or a payment succeeds. ReachBell finds that user’s most recent device, whether web, Android, or iPhone, and delivers within seconds. Your frequency caps still apply, so a flurry of order updates won’t spam someone.
When a user uninstalls, their device token quietly goes dead. Firebase and Apple report this back on the next send, and ReachBell marks the token dead immediately, stops sending to it, and purges it after your chosen retention window. The upside: your delivery rate reflects real, reachable users — not a vanity number padded with phones that uninstalled months ago.
Free forever for your first 1,000 subscribers. Set up in five minutes — no credit card needed.
Start free today