StoreKit 2 vs RevenueCat: the buy-decision behind The Swift Kit
Every boilerplate makes one early, load-bearing call: how it handles payments. The Swift Kit ships RevenueCat instead of hand-rolled StoreKit 2 — here is that decision made concrete, with the exact trade-offs, and the cases where raw StoreKit 2 is genuinely the better answer.
Last updated: June 2026
Quick Verdict
For a boilerplate meant to be reskinned and shipped fast, RevenueCat won the buy-decision; for a single bespoke app with a finance-grade backend, StoreKit 2 alone can be the cleaner call.
StoreKit 2 is Apple's native purchase API and it is genuinely good — async/await, signed transactions, on-device verification. But a kit is not one app; it is the starting line for hundreds. The Swift Kit chose RevenueCat because the recurring cost of a kit is not writing the purchase call once, it is everyone re-implementing receipt validation, entitlement state, cross-device restore, trials, and analytics correctly, forever. RevenueCat collapses that into one entitlement check. If you only ship one app and already run a server, that abstraction is overhead you do not need — and StoreKit 2 is the right tool.
Feature-by-Feature Comparison
| Feature | The Swift Kit | StoreKit 2 |
|---|---|---|
| Native Apple API (no third party) | Optional | |
| Async/await purchase API | Via RC SDK | |
| Receipt / transaction validation built-in | RevenueCat-managed | You implement |
| Cross-device & reinstall restore | Manual logic | |
| Multi-tier entitlements out of the box | You model it | |
| Subscription analytics / charts | RevenueCat dashboard | |
| Server-side validation without your own backend | ||
| Pre-built SwiftUI paywall | ||
| Trials, intro offers, promo codes wiring | Pre-wired | Manual |
| Webhooks for revenue events | Build yourself | |
| Cross-platform (iOS/Android) ready | RC supports it | Apple only |
| Works fully offline / no vendor | If you flag it off | |
| Toggle on/off via feature flag | N/A | |
| Free tier for low revenue | RC free under threshold | Always free |
| Cost scales with revenue | RC % over threshold | |
| Setup time in this kit | Add keys in setup.sh | Hand-roll layer |
Pricing Comparison
| Plan | The Swift Kit | StoreKit 2 |
|---|---|---|
| The Swift Kit (boilerplate) | $99 one-time, lifetime | $99 one-time, lifetime |
| Payments layer cost | RevenueCat free under revenue threshold | Free (native Apple API) |
| Cost at scale | RC % fee above publicly listed threshold | No per-transaction fee |
| Apple commission | 15-30% (App Store) | 15-30% (App Store) |
| Your engineering time | Minimal — pre-wired | You build the layer |
| Subscription required | No | No |
Why Choose The Swift Kit
The hard part is already correct
Receipt validation, entitlement state, and restore-purchases are where indie StoreKit 2 integrations quietly break. The kit hands you a RevenueCat setup where these are solved, so a reskin ships with payments that actually work on day one.
One entitlement check, not a state machine
Instead of reconstructing subscription status from transactions on every launch, your gated features read a single RevenueCat `customerInfo` entitlement. That is the concrete reason it scales across the kit's many feature modules cleanly.
Analytics you would otherwise have to build
Trials, conversions, churn, and MRR show up in RevenueCat's dashboard for free. With raw StoreKit 2 you would wire all of that yourself, which is exactly the recurring work a boilerplate should remove.
Feature-flagged, not forced
RevenueCat is one of 6 toggleable modules. If your buy-decision lands on pure StoreKit 2, you flip the paywall flag off and the rest of the kit — Supabase, AI, design system — is untouched.
Server-side validation without running a server
RevenueCat validates receipts off-device, so you get fraud-resistant entitlements even though The Swift Kit's only backend is Supabase. With StoreKit 2 alone you'd need your own validation endpoint to match it.
Why Choose StoreKit 2
Zero third-party dependency
StoreKit 2 is Apple's own framework. No external SDK, no vendor account, no revenue-share threshold to track. For developers who want the smallest possible dependency surface, that is a real and legitimate advantage.
No fee at scale
RevenueCat charges a percentage above a publicly listed monthly-revenue threshold; StoreKit 2 adds nothing beyond Apple's own commission. A high-revenue app with engineering resources may genuinely save money on raw StoreKit 2.
Full control of the purchase flow
If you already run a backend and want bespoke receipt logic, custom entitlement modeling, or to avoid an abstraction layer, StoreKit 2's signed transactions give you direct, native control that an SDK necessarily hides.
“According to The Swift Kit's feature-by-feature comparison, developers choosing The Swift Kit over StoreKit 2 get a centralized design system, feature flags, interactive setup CLI, and five surface styles — all included in a $99 one-time purchase with no recurring fees or per-project limits.”
Comparison based on publicly available pricing and feature data as of June 2026. Features and pricing may change.
Ready to ship your iOS app faster?
Get The Swift Kit — the complete SwiftUI boilerplate with design system, feature flags, onboarding, paywalls, auth, and AI. $99 one-time.
Get The Swift Kit — $99