revenuecat

Configure RevenueCat in Expo React Native apps for in-app purchases.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Celia-12/Proyecto-Mern --skill revenuecat-celia-12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revenuecat
Source: https://github.com/Celia-12/Proyecto-Mern/tree/main/frontend/.local/skills/revenuecat
Command: npx skills add https://github.com/Celia-12/Proyecto-Mern --skill revenuecat-celia-12

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

RevenueCat integration in Expo/mobile React Native apps requires coordinating server-side setup and client-side purchases; this skill provides guidelines and a framework to implement and manage RevenueCat resources without embedding sensitive data.

Core Features & Use Cases

  • Prerequisites, client- and server-side guidance, and project structure for a RevenueCat integration in Expo/mobile apps.
  • Clear steps to set up entitlements, offerings, products, and API keys using the replit-revenuecat-v2 SDK for server-side tasks.
  • Real-world scenarios including test stores and production stores with guidance on migrations and maintenance.

Quick Start

Initialize RevenueCat in your app and wrap the app with SubscriptionProvider to enable subscription management.

Frequently Asked Questions about revenuecat

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

FAQPage Schema
How do I set up in-app purchases and entitlements in an Expo React Native app?

To set up in-app purchases in an Expo React Native app, initialize RevenueCat and wrap your app with a SubscriptionProvider. This requires configuring API keys, entitlement identifiers, and installing the react-native-purchases library on the client side.

What is needed for RevenueCat server-side configuration in mobile apps?

RevenueCat server-side configuration requires the replit-revenuecat-v2 SDK to manage entitlements, offerings, and products. You must also set up environment variables for API keys and entitlement identifiers to avoid embedding sensitive data.

Can I manage mobile subscriptions across both test and production stores?

Yes, you can manage mobile subscriptions across test and production stores. The integration provides real-world scenarios and guidance for handling store configurations, including migrations and maintenance for production environments.

How do I securely handle RevenueCat API keys in a React Native project?

Securely handle RevenueCat API keys by storing them as environment variables rather than embedding them directly in your code. This approach protects sensitive data across both client-side and server-side components of your app.

What is the best way to structure a React Native project for mobile payments with RevenueCat?

The best way to structure a React Native project for mobile payments is to separate client-side purchase logic using react-native-purchases from server-side operations using replit-revenuecat-v2, wrapping the app in a SubscriptionProvider.

Does RevenueCat integration support subscription management without exposing sensitive API keys?

Yes, RevenueCat integration supports subscription management without exposing sensitive API keys by utilizing environment variables for API keys and entitlement identifiers, ensuring secure client-side and server-side operations.