Skip to content
Superapp
Esc
↑↓navigate↵open⌘Jpreview
On this page

RevenueCat or StoreKit?

Choose between Superapp’s integrated subscription platform and direct Apple APIs.

RevenueCat and StoreKit are not competing payment processors. Apple still handles the transaction. The decision is whether your app manages purchase state directly with StoreKit or uses RevenueCat as an additional subscription-management layer.

The practical difference

What RevenueCat adds

RevenueCat turns App Store products into named entitlements, keeps customer purchase state available through its SDK and APIs, and adds dashboards, offerings, paywall management, targeting, and subscription analytics. Superapp can work with the connected RevenueCat project through its built-in integration.

What direct StoreKit means

The app talks directly to Apple’s StoreKit APIs. It can use native StoreView, ProductView, or SubscriptionStoreView components and determine access from Apple’s signed transactions and subscription status without adding RevenueCat.

What both approaches still require

Products and subscription groups must be configured in App Store Connect. The app still needs correct purchase, entitlement, expiration, restore, and error handling, and every product must pass App Review.

Choose RevenueCat when your goal is growth

  • You expect several products, plans, paywalls, or customer segments.
  • You want to change offerings or supported paywall content without shipping app code.
  • You need subscription analytics, customer history, webhooks, or backend access checks.
  • You may expand beyond one Apple app or platform later.
  • You want Superapp’s integrated RevenueCat tools to help configure the system.

Choose direct StoreKit when your goal is simplicity

  • You have one Apple-only app with a small, stable product catalog.
  • You want Apple’s native subscription UI and localized merchandising.
  • You prefer fewer third-party services and less customer data leaving Apple’s stack.
  • You are comfortable keeping entitlement and lifecycle logic correct in the app.
  • You do not need advanced paywall analytics, targeting, or remote experiments.

A simple rule

Start with StoreKit

Ship the simplest reliable version

A single premium unlock or one straightforward subscription can stay entirely native.

Start with RevenueCat

Build a subscription business

If pricing, retention, segmentation, and paywall iteration are core product work, use the operational layer from the beginning.