Facts read November 18, 2026
Apple Push Notification service (direct) vs Expo push notifications
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 Apple Push Notification service (direct) if you care most about Swift iPhone apps.
Side by side
| Fact | Apple Push Notification service (direct) | Expo push notifications |
|---|---|---|
| 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. | Expo's push service: one API and one token format that delivers through APNs on iOS and FCM on Android. |
| Free plan | Apple lists no per-notification price; sending needs an Apple Developer Program membership ($99 a year). | No cost to send through the Expo push notification service; 600 notifications per second per project. |
| Paid from | Not stated | Not stated |
| At 1,000 users | $0/month | $0/month |
| Open source | No | Yes |
| Self-hostable | Yes | No |
| Best for | iPhone-only Swift apps; Keeping user data out of another vendor; Time-sensitive alerts and Live Activities | Expo and React Native apps; One backend call for iOS and Android; Reminders and replies without a marketing tool |
| 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. | 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. |
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) | Expo push notifications |
|---|---|---|
| an iPhone app in Swift with Xcode | +3 Apple's own service, with nothing between your backend and the phone. | −3 Its tokens come from the expo-notifications library, which a Swift app doesn't use. |
| native iOS or Android app | +1 Reaches iPhones and iPads; Android needs FCM too. | +3 One API and token for iOS and Android, built into Expo apps. |
| fewer vendors | +1 No push vendor to sign up for. | 0 No particular strength here. |
| regulated or compliance-sensitive | +1 No third party holds your users' device tokens or message contents. | 0 No particular strength here. |
| high volume | 0 No particular strength here. | −1 Capped at 600 notifications a second per project. |
Sources: Apple Push Notification service (direct) pricing (read November 18, 2026), Expo push notifications pricing (read November 18, 2026). No vendor pays for placement.