Blog post
Priming-Based Onboarding: Convert Subscribers Before the Paywall
Most onboarding flows educate. The best ones prime subscribers to buy. Here's the psychology-backed framework for onboarding that converts.
Nami vs. RevenueCat
RevenueCat's stack, or yours.
RevenueCat ties teams to its own billing layer. Nami is the no-code platform for building paywalls, pages, and subscriber journeys across connected TV, web, and mobile, working with the commerce stack you already run. Nami is a standalone subscription platform that connects directly to Apple, Google, Amazon, and Roku billing.
Which is the best fit?
RevenueCat
For teams whose only need is mobile in-app purchase plumbing on iOS and Android: receipts, entitlements, and subscription state.
Nami
For multi-platform enterprise teams who build paywalls, pages, and subscriber journeys across connected TV, web, and mobile, with the commerce stack they already run.
Feature comparison
What each platform does, side by side.
Source for RevenueCat details: revenuecat.com (May 2026).
Platform coverage
 | RevenueCat | |
|---|---|---|
| Web | ✓ (paywalls) | |
| iOS app (native paywall builder) | ||
| Android app (native paywall builder) | ||
| Apple TV | SDK only† | |
| Roku | SDK only† | |
| Fire TV, Samsung Tizen, LG webOS, Android TV, Google TV, Vizio | — |
Subscriber journey scope
| | RevenueCat | |
|---|---|---|
| Paywalls | ||
| Landing pages | — | |
| Onboarding flows with conditional logic | — | |
| Upgrade & cross-sell screens | — | |
| Win-back screens | — | |
| Modals, half sheets, popovers | — | |
| Conditional routing across platforms (mobile + connected TV + web) | — |
Experimentation
| | RevenueCat | |
|---|---|---|
| A/B testing on paywalls | ||
| Multivariate testing | ||
| Experiments on landing pages, onboarding flows, and offers | — | |
| Experiments across mobile apps and connected TV | — | |
| Subscription-aware experiment results |
Architecture: bring-your-own-billing vs. required billing layer
| | RevenueCat | |
|---|---|---|
| Commerce engine | Integrates: App Store IAP, Google Play IAP, Stripe, Recurly, Roku Pay, in-house | Required: RevenueCat subscription layer in the IAP path |
| Customer data platform / segmentation | Integrates: Amplitude, Adobe Experience Cloud, custom CDPs | Webhook integrations to CDPs |
| Behavioral analytics platform | Integrates: Amplitude, mParticle, Segment, Adobe | Webhook integrations to Amplitude, Mixpanel, others |
| Native mobile in-app purchases (App Store, Google Play) | ✓ | ✓ |
Service & pricing
| | RevenueCat | |
|---|---|---|
| Engagement model | Enterprise sales-led; dedicated Professional Services partnership | Self-serve with paid support tiers; Enterprise plan available for high-volume apps |
| Pricing model | Custom enterprise pricing based on subscriber volume, platform scope, and service tier | Free up to $2,500 monthly tracked revenue; 1% of revenue above; Enterprise plan with custom terms |
† RevenueCat supports Smart TV transactions through its SDK for entitlements and state, but does not ship a no-code paywall builder for CTV platforms. Source: revenuecat.com/docs.
Why Nami wins for enterprise teams
Why enterprise teams choose Nami over RevenueCat.
Nami is built for enterprise teams from the ground up: every customer, custom-quoted pricing, no revenue share, Professional Services partnership, and a platform that connects to the commerce stack you already run. RevenueCat's commercial model takes a percentage of monthly tracked revenue, which is why their architecture requires their billing layer. For enterprise teams running at scale, that's a meaningful gap.
Bring your own billing stack
Nami connects to the commerce stack you already run: App Store IAP, Google Play IAP, Stripe, Recurly, Roku Pay, or in-house. RevenueCat is built around its own billing layer with a commercial model that takes a percentage of revenue flowing through it. Enterprise teams who've invested in their commerce infrastructure keep what they have.
Connected TV, mobile, and web from one platform
Nami's no-code paywall builder ships Apple TV paywalls, Roku paywalls, Samsung TV paywalls, and Android TV paywalls alongside iOS, Android, Fire TV, LG webOS, Google TV, Vizio, and the web, from one dashboard. RevenueCat's paywall product covers iOS, Android, and web; connected TV transactions sit at the SDK layer. For streaming and OTT teams operating across screens, that's the difference between one system and several.
Experimentation beyond the paywall
RevenueCat Experiments test paywall design and pricing. Nami's experimentation engine runs on every step of the subscriber journey: landing pages, onboarding sequences, upgrade prompts, and offer logic. Configurable traffic allocation and subscription-aware results read each step honestly.
Subscription-aware analytics
Nami Insights connects creative and journey decisions to outcomes like conversion, trial starts, and revenue, segmented by platform, campaign, and product. It complements Amplitude, mParticle, or Segment rather than replacing them.
Enterprise service model
Nami operates as an enterprise platform with a Professional Services team that handles onboarding, template configuration, and the first round of experiments. RevenueCat's model is primarily self-serve with paid support tiers and a separate Enterprise plan. Some platforms try to work with the most. Nami works with the best.
Switching from RevenueCat
Most teams arrive here when their strategy outgrows mobile-only IAP plumbing. The web needs more than receipts, entitlements, and state. The connected TV launch can't run on a mobile-app-only stack. The team is ready for one platform built to orchestrate the full subscriber journey across every screen, with Professional Services through rollout.
Comparison FAQ
Common questions before a Nami vs. RevenueCat decision.
Does Nami replace RevenueCat?
For multi-platform enterprise teams, yes. Nami is the subscription orchestration platform that designs, tests, and connects paywalls, pages, flows, and experiments across connected TV, web, and mobile, with bring-your-own commerce: no revenue share, no required billing layer. RevenueCat is mobile-first IAP infrastructure with its own commercial model. Teams whose only need is mobile IAP plumbing on iOS and Android may find RevenueCat sufficient on its own.
Does Nami require RevenueCat?
No. Nami is a standalone platform with its own subscription infrastructure across iOS, Android, web, and TV/OTT.
How is Nami's connected TV paywall support different?
Nami's no-code paywall builder runs on Apple TV, Roku, Fire TV, Samsung Tizen, LG webOS, Android TV, Google TV, and Vizio from the same dashboard as iOS, Android, and web. RevenueCat's paywall product is iOS, Android, and web; its smart TV support sits at the SDK layer, not as a paywall-building product.
We already use RevenueCat Experiments. What does Nami add?
RevenueCat Experiments focus on paywall design and pricing. Nami runs experiments across the full subscriber journey: landing pages, onboarding flows, upgrade screens, and offer logic. Pricing is one variable Nami tests; the page, the flow, and the offer are all variables too.
Proof at scale
Millions of subscribers served across our customer base. 99.99% uptime. SOC 2, GDPR, and CCPA compliant.