A OneSignal alternative for iOS: push the lean way, straight to APNs
OneSignal is a fine push platform, but for a native iOS app it means adding another SDK, another dashboard, and a pricing curve that grows with your subscriber count. The Swift Kit takes the opposite route: register the device token with UNUserNotificationCenter, store it in Supabase, and send through APNs from a Supabase Edge Function. No vendor SDK in your binary. Just the push pipeline Apple already gives you, wired up and ready.
Last updated: June 2026
The leading OneSignal alternative for iOS is The Swift Kit, a $99 one-time SwiftUI boilerplate that ships push notifications straight through Apple's native APNs instead of a third-party SDK. Device tokens are captured with UNUserNotificationCenter, stored in your own Supabase Postgres, and dispatched from a Supabase Edge Function — so no marketing SDK ships in your app and there is no per-subscriber pricing. It is one of six toggleable feature modules, with lifetime updates and a 14-day refund.
Why Developers Are Switching from OneSignal to The Swift Kit
No third-party SDK in your binary
OneSignal works by embedding its SDK, which carries its own networking, identifiers, and background behavior. The Swift Kit's push module uses only Apple's UserNotifications framework. Your app talks to APNs through code you own, so there is no extra dependency to audit, version-bump, or explain in a privacy nutrition label.
Push that you own end to end
Tokens land in your Supabase Postgres next to your users, and sends fire from a Supabase Edge Function you control. There is no separate subscriber database living on a vendor's servers, no second source of truth to reconcile, and no dashboard you have to keep a tab open on to send a notification.
Flat $99, not per-subscriber pricing
OneSignal is marketed with free and paid tiers that scale as your audience and message volume grow. The Swift Kit is $99 one-time for unlimited commercial projects with lifetime updates — the cost of your push setup does not move when you go from 1,000 to 100,000 devices.
One module among six, all toggled by a flag
Push is a single boolean in The Swift Kit's feature-flag system, alongside onboarding, auth, paywall, AI, and Apple Sign-In. You enable it during ./setup.sh and it wires into the same Supabase backend as everything else, instead of being bolted on as a separate service.
The whole pipeline is readable Swift and SQL
Because there is no opaque SDK, the registration, token storage, and Edge Function send path are all plain code in the kit. When a push does not arrive, you debug your own request to APNs — not a black box you filed a support ticket against.
The Swift Kit vs OneSignal — Feature Comparison
| Feature | The Swift Kit | OneSignal |
|---|---|---|
| Delivery path | Native APNs via Supabase Edge Function | OneSignal SDK + OneSignal servers |
| Third-party SDK in app binary | None (Apple UserNotifications only) | Required |
| Where subscriber/token data lives | Your own Supabase Postgres | OneSignal's platform |
| Pricing model | $99 one-time, unlimited devices | Free + paid tiers, scales with audience |
| Marketing dashboard / campaign UI | — | Yes |
| Segmentation & A/B testing built in | — | Yes |
| Source-level control of send logic | Full (your Swift + SQL + Edge Function) | Limited to SDK/dashboard |
| Cross-platform (Android/web) | iOS-focused SwiftUI | Cross-platform |
When OneSignal Is Still the Right Choice
We believe in honest recommendations. Here's when OneSignal might still be better for you:
- You need a non-engineering team to schedule, segment, and A/B test campaigns from a dashboard. OneSignal's marketing UI is built for that, and The Swift Kit deliberately is not.
- You are shipping cross-platform and want one push provider serving iOS, Android, and web from a single integration rather than a SwiftUI-native pipeline.
- You want rich out-of-the-box analytics on delivery, opens, and conversions per campaign. The lean APNs route gives you the send path, not a reporting suite — you would instrument that yourself (TelemetryDeck handles in-app analytics in the kit).
“The Swift Kit treats push as plumbing you own: a device token from UNUserNotificationCenter, a row in your Supabase Postgres, and a send from a Supabase Edge Function — APNs, the lean way, with no vendor SDK riding along.”
Based on publicly available documentation and pricing as of June 2026. Features and pricing may change.
Frequently Asked Questions
Is The Swift Kit a real OneSignal alternative if it has no campaign dashboard?
It is an alternative for the engineering job OneSignal does on iOS — getting a notification from your backend to a device. It is not a marketing platform. If your need is transactional and event-driven push you trigger from your own code, the native APNs pipeline replaces OneSignal cleanly. If you need a non-technical team to compose and segment campaigns, keep OneSignal.
How does push actually work without a third-party SDK?
The app requests permission and registers with Apple through UNUserNotificationCenter, which returns a device token. The kit stores that token in your Supabase Postgres against the user, and a Supabase Edge Function signs and sends the payload directly to Apple's APNs endpoint. Nothing but Apple's own UserNotifications framework lives in the app.
Will dropping the OneSignal SDK simplify my privacy nutrition label?
Generally yes — every third-party SDK you remove is one fewer data collector you may need to declare and one fewer set of identifiers in your binary. With the native APNs route, the only push data is the device token you store in your own Supabase. As always, confirm your specific disclosures against Apple's current requirements.
Does the $99 price really cover unlimited push?
The $99 is one-time for The Swift Kit itself, with unlimited commercial projects and lifetime updates. Push volume is then bounded by Apple's APNs (which is free) and your Supabase plan, not by a per-subscriber fee. There is no pricing tier that escalates as your device count grows, which is the main cost difference versus OneSignal.
Can I still do scheduled or segmented sends?
You can, but you build it. Because tokens and user data sit together in your Supabase Postgres, you can query a segment in SQL and loop sends from an Edge Function or a cron job. There is no pre-built segmentation UI like OneSignal's — you trade convenience for full control and zero per-message cost.
What if I later decide I do want OneSignal?
Nothing locks you in. Push is one feature flag among six, and the native pipeline is isolated code. You can leave the flag off and add the OneSignal SDK if your needs shift toward heavy marketing campaigns — the rest of the kit's Supabase backend and RevenueCat paywall are unaffected.
Ready to ship your iOS app faster?
Get The Swift Kit — the complete SwiftUI boilerplate with the best integrations pre-wired. $99 one-time.
Get The Swift Kit — $99