Facts read November 18, 2026
Expo push notifications vs OneSignal
Expo push notifications is Cuely's default push notifications pick when your description doesn't favor either one: one send API for both stores, free, already part of an Expo app. Pick OneSignal if you care most about marketing and re-engagement campaigns.
Side by side
| Fact | Expo push notifications | OneSignal |
|---|---|---|
| What it is | Expo's push service: one API and one token format that delivers through APNs on iOS and FCM on Android. | A messaging platform for push, in-app messages, email and SMS, with segments, journeys and a dashboard for sending campaigns. |
| Free plan | No cost to send through the Expo push notification service; 600 notifications per second per project. | Free: unlimited mobile push for organizations with up to 1,000 monthly active users; 10,000 emails a month. |
| Paid from | Not stated | Growth: from $19/month, plus $0.012 per monthly active mobile user. |
| At 1,000 users | $0/month | $31/month |
| Open source | Yes | No |
| Self-hostable | No | No |
| Best for | Expo and React Native apps; One backend call for iOS and Android; Reminders and replies without a marketing tool | Marketing and re-engagement campaigns; Teams where non-developers send messages; Push plus in-app messages and Live Activities |
| Watch out | Sending is capped at 600 notifications a second per project, and 100 per request; throttle and retry on your server. A push ticket only means Expo received the message; fetch push receipts later to see delivery errors and drop dead tokens. | Free covers mobile push for up to 1,000 monthly active users, counted whether or not they opted in; past that, Growth is $19/month plus $0.012 per MAU. Marketing pushes need explicit opt-in in the app and a way to opt out (App Review Guideline 4.5.4). |
Where they differ
The published scores, from −3 to +3, that decide which one Cuely picks for each need.
| Need | Expo push notifications | OneSignal |
|---|---|---|
| marketing or re-engagement campaigns to segments of users | −2 A send API for developers; no segments, scheduling or campaign dashboard. | +3 Segments, journeys, A/B tests and a no-code message builder for campaigns. |
| an iPhone app in Swift with Xcode | −3 Its tokens come from the expo-notifications library, which a Swift app doesn't use. | +1 Has a Swift SDK with Live Activities support. |
| keep costs as low as possible | +1 Expo charges nothing to send. | −1 Free stops at 1,000 monthly active users, counted whether or not they opted in to push. |
| native iOS or Android app | +3 One API and token for iOS and Android, built into Expo apps. | +2 SDKs for iOS, Android, React Native and Flutter, with in-app messages included. |
| high volume | −1 Capped at 600 notifications a second per project. | 0 No particular strength here. |
| fewer vendors | 0 No particular strength here. | +1 Push, in-app messages and email in one dashboard. |
| prefers open source or self-hosting | 0 No particular strength here. | −1 Proprietary and hosted only. |
Sources: Expo push notifications pricing (read November 18, 2026), OneSignal pricing (read November 18, 2026). No vendor pays for placement.