revenuecat

Integrate RevenueCat subscriptions into Replit Expo/mobile apps with entitlement-based access control.

Updated Dec 10, 2025
One-click install
npx skills add https://github.com/KhaledMKhaled/FodaStore --skill revenuecat-khaledmkhaled
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revenuecat
Source: https://github.com/KhaledMKhaled/FodaStore/tree/main/.local/skills/revenuecat
Command: npx skills add https://github.com/KhaledMKhaled/FodaStore --skill revenuecat-khaledmkhaled

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about revenuecat

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up RevenueCat subscriptions in an Expo React Native app?

Set up RevenueCat subscriptions by running a standalone seed script to configure products and entitlements, storing the logged environment variables, then wiring client initialization and entitlement-based access control. This uses react-native-purchases for client-side flows.

Do I need a separate server-side SDK for RevenueCat CRUD operations?

Yes, RevenueCat requires correct SDK separation: use react-native-purchases for client-side purchase and restore flows, and @replit/revenuecat-sdk for server-side standalone scripts performing CRUD operations and project inspection.

How do I prevent duplicating subscription product catalogs with RevenueCat?

Prevent duplicating product catalogs by using RevenueCat as the single source of truth, deriving UI pricing directly from offerings and package context, and avoiding parallel local product tables or duplicated catalog storage in your database.

Can I gate premium features in my mobile app using RevenueCat entitlements?

Yes, you can gate features using RevenueCat entitlements. The skill enforces entitlement-based access control, allowing you to unlock premium plans consistently across stores based on the user's active subscription status.

What environment variables are required to configure RevenueCat for a mobile app?

Configuring RevenueCat requires environment-variable driven public keys and project identifiers. You must complete the mandatory SKILL.md configuration step and store the variables logged during the initial seed script execution.

What is the best way to manage RevenueCat offerings after initial setup?

Manage offerings post-setup using standalone server-side scripts with the @replit/revenuecat-sdk. This supports ongoing CRUD operations and inspection of products, entitlements, offerings, and packages without altering the client code.