Facts read November 18, 2026
Expo push notifications vs Firebase Cloud Messaging
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 Firebase Cloud Messaging if you care most about Swift iPhone apps.
Side by side
| Fact | Expo push notifications | Firebase Cloud Messaging |
|---|---|---|
| What it is | Expo's push service: one API and one token format that delivers through APNs on iOS and FCM on Android. | Google's push service: native on Android, and delivers to iOS through your APNs key, with SDKs for Swift, Kotlin, React Native and the web. |
| Free plan | No cost to send through the Expo push notification service; 600 notifications per second per project. | Cloud Messaging (FCM) is no-cost on both the Spark and Blaze plans. |
| Paid from | Not stated | Not stated |
| At 1,000 users | $0/month | $0/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 | Apps already on Firebase; Native Swift plus Android apps; Topic messages to many devices |
| 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. | On iOS it still needs an APNs key uploaded to Firebase, and the Firebase SDK in the app. The app needs the Firebase SDK for push even if the rest of the backend isn't Firebase. |
Where they differ
The published scores, from −3 to +3, that decide which one Cuely picks for each need.
| Need | Expo push notifications | Firebase Cloud Messaging |
|---|---|---|
| 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, and one API if an Android app follows. |
| high volume | −1 Capped at 600 notifications a second per project. | +1 Topics send to large audiences in one request. |
| native iOS or Android app | +3 One API and token for iOS and Android, built into Expo apps. | +2 Native SDKs for iOS, Android and React Native, at no cost. |
| marketing or re-engagement campaigns to segments of users | −2 A send API for developers; no segments, scheduling or campaign dashboard. | −1 The Firebase console can send simple campaigns, but segments and journeys need other Google tools. |
| fewer vendors | 0 No particular strength here. | +1 Same console as Firebase's database and auth. |
| prefers open source or self-hosting | 0 No particular strength here. | −1 Proprietary Google service. |
Sources: Expo push notifications pricing (read November 18, 2026), Firebase Cloud Messaging pricing (read November 18, 2026). No vendor pays for placement.