Facts read November 18, 2026
Apple Push Notification service (direct) vs Firebase Cloud Messaging
Firebase Cloud Messaging is Cuely's default push notifications pick when your description doesn't favor either one: no-cost push on both platforms from Google, with native Swift and Kotlin SDKs. Pick Apple Push Notification service (direct) if you care most about Swift iPhone apps.
Side by side
| Fact | Apple Push Notification service (direct) | Firebase Cloud Messaging |
|---|---|---|
| What it is | Sending straight to Apple's APNs from your backend over HTTP/2 with a token signing key, with no service in between. | 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 | Apple lists no per-notification price; sending needs an Apple Developer Program membership ($99 a year). | 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 | No | No |
| Self-hostable | Yes | No |
| Best for | iPhone-only Swift apps; Keeping user data out of another vendor; Time-sensitive alerts and Live Activities | Apps already on Firebase; Native Swift plus Android apps; Topic messages to many devices |
| Watch out | iOS only; Android needs FCM alongside it. You write the sender: a JWT signed with your .p8 key, HTTP/2 requests, and deleting tokens APNs reports as no longer valid. | 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 | Apple Push Notification service (direct) | Firebase Cloud Messaging |
|---|---|---|
| an iPhone app in Swift with Xcode | +3 Apple's own service, with nothing between your backend and the phone. | +1 Has a Swift SDK, and one API if an Android app follows. |
| native iOS or Android app | +1 Reaches iPhones and iPads; Android needs FCM too. | +2 Native SDKs for iOS, Android and React Native, at no cost. |
| regulated or compliance-sensitive | +1 No third party holds your users' device tokens or message contents. | 0 No particular strength here. |
| marketing or re-engagement campaigns to segments of users | −2 A raw send API; segments and scheduling are yours to build. | −1 The Firebase console can send simple campaigns, but segments and journeys need other Google tools. |
| high volume | 0 No particular strength here. | +1 Topics send to large audiences in one request. |
| prefers open source or self-hosting | 0 No particular strength here. | −1 Proprietary Google service. |
Sources: Apple Push Notification service (direct) pricing (read November 18, 2026), Firebase Cloud Messaging pricing (read November 18, 2026). No vendor pays for placement.