What problem does it solve?
This skill helps you correctly integrate RevenueCat in a Replit Expo/mobile project so subscriptions, entitlements, offerings, and purchases work reliably without you building and maintaining your own parallel in-app purchase catalog.
Core Features & Use Cases
- Guided RevenueCat setup for Expo/mobile on Replit: Ensures the correct client/server SDK separation and prepares a working RevenueCat configuration for products and entitlements.
- Safe subscription data handling: Enforces using RevenueCat as the source of truth (no product tables or duplicated catalog storage) and derives UI pricing from offerings/package context.
- Lifecycle operations for subscriptions: Supports initial seeding, subsequent CRUD/inspection via standalone scripts, and client purchase/restore flows using the entitlement to unlock access.
- Use Case: You want users to subscribe to a premium plan in an Expo app, show available packages on a paywall, and gate features based on an entitlement that stays consistent across stores.
Quick Start
Ask the system to set up RevenueCat for an Expo/mobile app by running the standalone seed script first, storing the logged environment variables, then wiring the client initialization and entitlement-based subscription provider.