Documentation
PaywallReady documentation
Public docs for adding RevenueCat subscriptions to your Expo app. Read them before purchase, then use the kit source code to implement.
What PaywallReady gives you
A subscription layer you copy into your existing app.
You already built the app. You already picked RevenueCat for payments. PaywallReady is the bridge between those two — the code that checks whether someone paid, shows a paywall, and unlocks the premium feature.
Without PaywallReady
- Read RevenueCat docs for the 5th time
- Wire auth identity to purchase state yourself
- Build restore purchase from scratch
- Debug entitlement sync for hours
- Write Firebase rules without a working example
With PaywallReady
- Copy the provider, gate one feature
- Anonymous customers work immediately
- Restore purchases included
- Entitlement state handled for you
- Firebase rules copy-paste ready
How it works in plain English
You have an app and one feature to gate
A button, a screen, a limit — whatever you want to make premium.
You copy PaywallReady into your app
The provider wraps your app once. The hook checks premium status anywhere.
You sell through the app stores
RevenueCat handles the purchases. PaywallReady checks if the user has access.
You add auth or Firebase later, only if needed
Most apps never need more. But the path is there when you do.
Read these in order
Each page is short. Read only what you need. Skip what you already know.