Skip to main content
You’re reading the docs for Newly v1 (legacy), the classic newly.app builder. Using app.newly.app or Newly for Mac? Go to the Newly v2 docs. Credits, pricing and features differ between the two.
Newly handles most of the RevenueCat setup automatically. Here’s what happens when you add subscriptions to your app.

​
One-click setup

When you ask the AI to add a paywall or subscriptions, the flow is:
1

Connect your RevenueCat account

An OAuth popup lets you connect your RevenueCat account. This gives Newly permission to create products and fetch API keys on your behalf.
2

Choose your price

You pick a monthly subscription price (e.g. $9.99/month). Newly does the rest.
3

Everything gets created automatically

Newly creates the following in your RevenueCat dashboard:
  • An entitlement (always named “pro”)
  • A product with your chosen price
  • An offering and package linking them together
  • App Store and Play Store apps in RevenueCat
  • App Store Connect subscriptions and products
Then the AI agent generates all the code in your app:
  • SubscriptionContext.tsx — provider with RevenueCat SDK
  • A paywall screen at /paywall
  • Integration into your onboarding flow
  • SDK API keys in app.json

​
What gets automated

​
The “pro” entitlement

Newly uses a single entitlement called “pro” for all subscriptions. Custom entitlement names are not supported. If a different name is accidentally set, the system auto-corrects it to “pro”.
You don’t need to worry about entitlement names — the system handles this automatically. If you see “pro” in your RevenueCat dashboard, that’s expected.
When you have authentication, onboarding, and a paywall, Newly enforces a deterministic navigation order:
  1. Authentication — user signs in or creates account
  2. Onboarding — app onboarding screens
  3. Paywall — subscription screen
This order is enforced regardless of the sequence you set things up in.