Push notifications re-engage users. But they require a native app.
Push notifications are one of the highest-engagement mobile features. They require a React Native app (not a web app) and integration with APNs (Apple) and FCM (Google). Getting permissions, handling deep links, and sending targeted notifications at scale requires a solid implementation.
Need to send push notifications to mobile users — either adding to an existing app or building the mobile app that enables them
Push notifications require a native mobile app. Web apps (including PWAs on iOS) have limited push notification support. A React Native app built with Expo provides full push notification capabilities on both iOS and Android.
The implementation components:
Expo Notifications API. Expo provides a unified push notification API that abstracts APNs (Apple Push Notification Service) and FCM (Firebase Cloud Messaging). One API for both platforms.
Permission request. Users must grant notification permission. iOS shows a system permission dialog (allow/don't allow). Good timing for the request matters: ask when the user understands the value (not immediately on app open).
Push token storage. Each device that grants permission has a unique push token. Store these tokens in the database associated with the user. One user may have multiple tokens (multiple devices).
Server-side sending. Your backend sends push notifications via Expo's Push API or directly via APNs/FCM. Expo's API is simpler for getting started; direct APNs/FCM gives more control.
Deep linking. Notifications should navigate to the relevant screen when tapped. Deep link configuration connects the notification action to the correct app route.
Notification categories. Different notification types (new message, order update, payment) with different handling and user controls to opt in/out per category.
Push notification system with APNs/FCM delivery, notification permission flow, targeted sends by user segment, and deep link navigation from notification to the relevant screen
Expo push notifications
setup (APNs + FCM credentials)
Permission request flow
with appropriate timing
Push token management
(store, update, clean up expired tokens)
Server-side notification dispatch
(targeted by user, segment, or broadcast)
Deep link navigation
from notification to the relevant screen
One honest number to start.
Fixed-scope, fixed-price. The number below is the starting point — final scope is built from your brief.
Push notification system with APNs/FCM delivery, notification permission flow, targeted sends by user segment, and deep link navigation from notification to the relevant screen
Three steps, every time.
The same repeatable engagement on every project. No surprises, no mystery, no billable ambiguity.
Brief & discovery.
We send you questions, then get on a call. Output: a written scope with every step, feature, and integration listed.
Build & ship.
Fixed schedule, weekly reviews. No scope creep unless you change the scope — and if you do, we reprice it transparently.
Warranty & retainer.
30-day warranty on every launch. Most clients stay on a monthly retainer for ongoing features and maintenance.
Why Fixed-Price Matters Here
Push notification scope is defined: setup, permission flow, token management, and the notification types required. Fixed-price build.
Questions, answered.
Web push notifications work on Chrome and Android. iOS Safari requires a PWA installed to the home screen and iOS 16.4+. For consistent cross-platform push: native app is more reliable.
On iOS: 40-50% on average, depending on when the permission is requested and how well the value is communicated. Higher when asked after the user has experienced the product's value.
Tell Ryel about your project.
Describe what you’re building and what outcome you need. You’ll have a written, fixed-price scope within the week.