See Superapp in action
The same product recording shown on our landing page. Explore the publishing workflow, then build and test the features your own project needs.
Explore Superapp appsWhat in-app purchases mean for your product
A purchase should unlock a clearly defined benefit. Decide what stays free, what the customer receives, and how long access lasts before designing a paywall. A useful offer explains the result in plain language and matches the feature that becomes available after payment. Avoid making a paid screen look complete while the underlying access checks are missing.
StoreKit provides Apple’s purchase framework; RevenueCat helps manage purchase and entitlement information. Superapp can build the app’s integration around those services. Your product configuration, commercial agreements, and customer promises still belong to you. Keep the displayed price and subscription period aligned with the actual store product.
Consumables, one-time purchases and app subscriptions
Consumables are benefits that can be used up, such as a pack of credits. Non-consumables are lasting unlocks, such as a premium feature purchase. Auto-renewable subscriptions provide access for a recurring period. Choose the type based on the value you deliver and the ongoing costs of providing it.
A subscription is appropriate when the product offers continuing value, not merely because recurring revenue is attractive. If your app calls a paid AI provider, model the cost of active users before selling unlimited access. A one-time purchase may be simpler for a permanent local feature, while consumables require careful accounting for what has been spent.
How to add in-app purchases on iOS
Create the products and commercial configuration required in App Store Connect, then map the intended access in RevenueCat. The app needs to display the correct offering, start the purchase, handle the result, and refresh the customer’s access. Ask Superapp to build the complete journey rather than only a visually convincing paywall.
The important boundary is the entitlement: what the customer can actually use. Test a fresh account, a successful purchase, a cancelled purchase, and restoring an earlier purchase. Reopening the app should not silently remove paid access. Equally, the app should not grant permanent access just because someone opened the paywall or a request failed.
A paywall that customers can understand
A clear paywall explains the benefit, price, billing period, and any trial terms. Customers should know what happens after a trial ends and how a recurring subscription differs from a one-time payment. Keep a visible route back to the app and provide the account and support information customers need.
Design the surrounding experience too. Show a useful explanation when access has expired, and do not blame the customer for a temporary network problem. Confirm how the app behaves when a user signs in on another device. Purchase restoration and account identity are product decisions that should be tested with the real configuration.
Apple commission and other running costs
Apple’s standard commission is commonly 30%, while qualifying Small Business Program participants can receive a 15% rate. Subscription terms, region, and commercial arrangements can change the applicable economics. Check Apple’s current program and agreement for your account instead of assuming one rate applies to every transaction.
Store commission is only one cost. RevenueCat service charges, your backend, AI usage, support, and Superapp development credits may also matter. Estimate the amount left after those costs for a realistic active customer. A working paywall proves you can collect a payment; it does not prove the subscription is profitable.
How it works
Define the paid benefit
Write down the exact feature or content that payment unlocks and whether it is consumed, permanent, or recurring. Decide how free users experience the app before adding a paywall. Use that definition to choose the correct store product type.
Configure products and entitlements
Complete the required App Store Connect setup and RevenueCat configuration. Keep product identifiers and entitlement names consistent. Account ownership, commercial agreements, and pricing decisions remain with you rather than being inferred from the visual design.
Build the purchase journey
Ask Superapp to connect the offering, paywall, purchase result, and access checks. Include restore behavior and clear states for cancellation, expiration, and connectivity problems. The interface should explain what happened without promising access that the backend has not confirmed.
Test before charging customers
Run purchase tests using Apple’s supported testing environments. Verify access after reopening the app and restoring purchases. Review the paywall copy and submission information before release. Repeat the checks when products or entitlement rules change.
Compare monetization implementation paths
Compare the workflow and responsibilities, then check the linked providers for current plans and terms.
| Approach | Purchase integration | Paywall and access logic | Cost basis |
|---|---|---|---|
| Superapp | StoreKit and RevenueCat workflow | Generated Swift you review and test | Development credits plus provider costs |
| RevenueCat with your own app | Entitlement and purchase services | You build and integrate the client | Provider pricing plus development |
| StoreKit directly | Apple framework | You implement and maintain the flow | Developer time and Apple terms |
Pricing and running costs
Superapp offers free starting credits in supported countries, with paid plans starting at $25 per month. Building and revising uses credits. Budget separately for your domain, connected services, and usage inside the finished product. Publishing an iOS app also requires your own Apple Developer membership.
Check current plans and credit allowances before starting. Estimate both the first release and ongoing operation: maintenance, provider usage, and customer support continue after launch. Start with a focused workflow so you can measure actual costs before expanding the product.
Limitations and your responsibilities
Purchases require your commercial configuration and testing. Digital purchases and physical-goods checkout are different workflows. Trials depend on eligibility. Regional store rules and provider terms can change. Superapp does not guarantee review approval, subscription revenue, or profitability, and a paywall design alone does not enforce paid access.