In-App Purchases & Subscriptions for Next.js: what 18 makers' products chose
Among 18 makers' products built with Next.js that we know the In-App purchases & subscriptions of, RevenueCat leads: 16 of them (89%). Next come Adapty (1) and Qonversion (1).
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.
What makers on Next.js chose
| Option | Next.js products | All makers |
|---|---|---|
| 16 (89%) | 87% | |
| 1 (6%) | 5% | |
| 1 (6%) | 2% | |
| 1 (6%) | 10% |
Live makers' products with a source for both: that they're built with Next.js, and what they use for In-App purchases & subscriptions. A product using two options counts in both; not market share. "All makers" is the option's share among every maker's product that made this decision.
Which to pick, by situation
- You're adding the first paid plan to an iOS or Android app and need purchases and restores to just work
RevenueCat 16 here - You want the purchase backend and paywall A/B tests in one tool
Adapty 1 here
Qonversion 1 here - You already have a subscription backend and want to change the paywall without shipping app updates
Superwall 1 here - You also sell on the web and want one record of what each user has paid for
RevenueCat 16 here
RevenueCat
Subscription backend16 Next.js products here (89%).
In Replit, RorkBest forA widely used cross-platform SDK for purchases, entitlements and subscription analytics, free until meaningful revenue.
Trade-offTakes a percentage of tracked revenue past the free threshold.
“Shoutout to RevenueCat for streamlining our subscription management in Aupair Valley! Couldn't have managed our diverse user groups without you. #GameChanger 🚀”
“Subscriptions are hard. RevenueCat makes them boring — in the best possible way. One integration, fewer edge cases, less “why did this user lose access?” energy.”
In-App Purchases & SubscriptionsMaker says so · source ↗“Best subscription solution for mobile”
In-App Purchases & SubscriptionsMaker says so · source ↗“I'm one person and the purchase had to work on both iOS and Android. Writing receipt validation twice sounded miserable. RevenueCat lets me check a single entitlement everywhere, and it even handles people who buy before signing in.”
In-App Purchases & SubscriptionsMaker says so · source ↗“RevenueCat is the thing that ties our Subscriptions/Payments together! It would be a mess without it.”
In-App Purchases & SubscriptionsMaker says so · source ↗“RevenueCat is seamless to integrate, provides clear analytics, and simplifies subscription management.”
In-App Purchases & SubscriptionsMaker says so · source ↗“No brainer to start monetizing a mobile app while abstracting store APIs. Love the paywall builder and making changes without having to submit new app version.”
In-App Purchases & SubscriptionsMaker says so · source ↗“We use RevenueCat to handle in-app purchases and subscriptions. We love how easy it is to integrate, we've been using it for all our products.”
In-App Purchases & SubscriptionsMaker says so · source ↗“Makes everything easy when it comes to handing payments on both Ios and Android. Thank you”
In-App Purchases & SubscriptionsMaker says so · source ↗“Monetize your apps very quickly with powerful paywall !”
In-App Purchases & SubscriptionsMaker says so · source ↗“Shoutout to RevenueCat for streamlining our subscription management in Aupair Valley! Couldn't have managed our diverse user groups without you. #GameChanger 🚀”
In-App Purchases & SubscriptionsMaker says so · source ↗Also chosen, and not seen yet
Fewer Next.js products here: Adapty (1), Qonversion (1), Superwall (1).
Real options for In-App purchases & subscriptions not seen among these Next.js products yet: react-native-iap.
Getting In-App purchases & subscriptions right
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.
The rest of the Next.js stack
What makers' Next.js products chose for their other decisions, the most common pick for each:
- Hosting: Vercel 1,078 of 1,312
- Transactional Email: Resend 493 of 830
- Database: Supabase 171 of 382
- Payments: Stripe 288 of 359
- LLM API: OpenAI API 222 of 301
- Authentication: Clerk 176 of 211
- Web Analytics: Google Analytics 105 of 197
- Product Analytics: PostHog 123 of 168
Questions
What do most Next.js apps use for In-App purchases & subscriptions?
Among 18 makers' products built with Next.js that we know the In-App purchases & subscriptions of, RevenueCat leads: 16 of them (89%). Next come Adapty (1) and Qonversion (1).
How this is counted: a product is on Next.js when a live-product source says so (the maker, its website, a customer story or a subprocessor list), and the same for its In-App purchases & subscriptions. How evidence is collected.