In-App Purchases & Subscriptions
Sell subscriptions and one-time purchases inside iOS and Android apps, and know who has paid, without writing receipt validation for each store.
Trends
RevenueCat gained the most ground in package downloads: +174% against the median npm package over a year.
Public counts each month: pull requests on GitHub, package downloads, stars, Product Hunt followers. They show direction, not market share.
The real choice
Subscription backend or paywall experiments. A subscription backend validates purchases across App Store and Google Play and tells your app what each user is entitled to. A paywall tool focuses on the screen that asks for money and lets you change and A/B test it without shipping an app update.
Pick by situation
Tap the ones that are you — the tools that fit light up below.- You're adding the first paid plan to an iOS or Android app and need purchases and restores to just work
RevenueCat - You want the purchase backend and paywall A/B tests in one tool
Adapty
Qonversion - You already have a subscription backend and want to change the paywall without shipping app updates
Superwall - You also sell on the web and want one record of what each user has paid for
RevenueCat - Your React Native or Expo app's purchases are simple and you'd rather verify them on your own server than share revenue
react-native-iap
Compare the tools
Grouped by the side of the choice they answer, not ranked. Open a row for when to use it, the trade-off and what makers say.
RevenueCatplatformA widely used cross-platform SDK for purchases, entitlements and subscription analytics, free until meaningful revenue.


111+3 open source705.8k/wk+174% vs npm
Use it whenYou're adding your first subscription to a mobile app and don't want to write receipt validation or handle store server notifications.
Trade-offTakes a percentage of tracked revenue past the free threshold.
In Replit, RorkUsed by Alfabird, ASO, Aupair Valley, BabyCheck, Backed AI and 106 more · in 3 open-source projects.
RevenueCat handles all the subscription complexity across iOS and Android. Their SDK made implementing in-app purchases painless, and the dashboard gives real-time revenue insights.
AdaptyplatformA subscription backend with a built-in paywall builder and A/B tests, when you want both in one tool.

615.4k/wk−18% vs npm
Use it whenYou want to change paywalls and test prices without adding a second vendor.
Trade-offRevenue-percentage pricing past its free threshold; smaller community than RevenueCat.
Used by ClarifierAI for IOS, MindTastik Meditation App, The Breathing App for Diabetes, GlowIsland, Vocabuo and 1 more.
Adapty : For managing paywalls, subscription segmentation, and A/B testing, Adapty is our chosen platform.
QonversionplatformA subscription backend with entitlements, analytics and paywall experiments, at a lower revenue share past its free threshold.
3358/wk
Use it whenYou want what RevenueCat does and the revenue-percentage fee is the deciding factor.
Trade-offTakes a percentage of tracked revenue past the free threshold; smaller community and fewer integrations than RevenueCat.
Used by MobiSystems, Amobear, XAPPIFY.
SuperwallplatformApps that want to iterate on paywall design, pricing and placement remotely and A/B test them.

13+1 open source31.3k/wk
Use it whenDownloads are steady and conversion on the paywall is your bottleneck.
Trade-offTakes a percentage of attributed revenue once past its free threshold.
Used by Backed AI, GoPolar, OpenWhispr, Amiry, Blixy and 8 more · in 1 open-source project.
Enabled us to create stunning, high-converting mobile paywalls in minutes — and run A/B tests without app updates. Absolute game-changer for monetization.
react-native-iaplibrary · open sourceReact Native and Expo apps that want to call StoreKit and Google Play Billing themselves, with no third-party backend or revenue share.8 open source135.4k/wk−30% vs npm
Use it whenYour purchases are simple (one subscription or a few unlocks) and you're willing to verify receipts and handle store notifications on your own server.
Trade-offNo dashboard, analytics or cross-platform entitlements; renewals, refunds and restores are yours to get right.
No maker's product we track shows it for this yet · in 8 open-source projects.
Before you choose
Wire up a subscription backend first — entitlements and restore purchases have to be right before anything else. Keep your user ID linked to the store customer so web and mobile purchases can meet later. Test paywall price and layout only once you have enough installs to read the results.
- Leaving out a Restore Purchases button, which Apple requires for restorable purchases and App Review will reject.
- Unlocking features from the purchase callback without handling renewals, refunds and expirations, so users keep premium after they cancel or get refunded.
- Running paywall A/B tests on a few hundred installs, where the gap you see is noise rather than a winner.
Decided alongside
What the 124 makers' products here chose for their other decisions.