In-app purchases for Flutter
Subscriptions and paywalls with RevenueCat
The RevenueCat skill wires subscriptions into a Riverpod v3 notifier: subscription state, entitlement gating and a paywall, either the RevenueCat-hosted UI or a fully custom one.
What this feature covers
- Paywall: A native RevenueCat-hosted paywall or a fully custom one.
- Purchase flow: Purchase and restore, with subscription state kept current.
- Entitlement gating: Per-feature gating driven by the current entitlement.
- Identity: RevenueCat identity linked to the app's signed-in user.
How Flutter Agent Kit implements it
Subscription state lives in a hand-written Riverpod v3 Notifier exposed as a global provider, so any screen can gate a feature by watching it. The kit uses purchases_flutter, and optionally purchases_ui_flutter for the hosted paywall. This is client-side integration only: there is no backend webhook or server-side receipt validation, which the skill states explicitly and points to the RevenueCat REST API when a backend is later needed.
iOS uses Swift Package Manager with no Podfile edits, and Android billing is injected by the plugin with no build.gradle changes, so the agent does not invent native setup steps.
Frequently asked questions
Native paywall or a custom one?
Both are covered. Add purchases_ui_flutter for the RevenueCat-hosted native paywall, or skip it and build your own widget for full control over the design. The subscription state and gating logic are the same either way.
Do I need a backend for subscriptions?
No for the client-side flow the skill covers. Entitlement grants, restores and subscription state come from RevenueCat directly. A backend is only needed if you later want server-side promotional grants or entitlement overrides.
Get Flutter Agent Kit
Flutter Agent Kit ships this as a ready feature skill, together with the AGENTS.md context layer and the rest of the skills. €99.99 one-time, lifetime updates, unlimited personal and commercial projects.
Browse all features included in Flutter Agent Kit.