understanding-revenuecat

Name: understanding-revenuecat
Availability: InStock
Author: RevenueCat

Explain RevenueCat Android SDK architecture and its billing components.

45|Updated Jun 2, 2026

Search Tags:#architecture #sdk #android #entitlements #offerings #revenuecat #customerinfo

Ready to run

npx skills add https://github.com/RevenueCat/play-billing-skills --skill understanding-revenuecat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: understanding-revenuecat
Source: https://github.com/RevenueCat/play-billing-skills/tree/main/revenuecat/understanding-revenuecat
Command: npx skills add https://github.com/RevenueCat/play-billing-skills --skill understanding-revenuecat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a foundational understanding of RevenueCat's Android SDK architecture, helping users navigate the SDK's components and functionalities effectively.

Core Features & Use Cases

SDK Architecture Overview: Understand how RevenueCat reorganizes BillingClient, Google Play Developer API, and RTDN into a single SDK.
Concept Mapping: Learn how Products, Packages, Offerings, Entitlements, and CustomerInfo connect within the RevenueCat ecosystem.
Use Case: Ideal for developers new to RevenueCat or transitioning from raw Play Billing, offering a clear mapping of concepts to the RevenueCat dashboard.

Quick Start

Use the understanding-revenuecat skill to familiarize yourself with the RevenueCat Android SDK architecture and its components.

Frequently Asked Questions about understanding-revenuecat

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

FAQPage Schema

How does RevenueCat organize Offerings, Packages, and Entitlements in the Android SDK?▼

RevenueCat organizes Offerings, Packages, and Entitlements by mapping Products into Packages, grouping them into Offerings, and linking them to Entitlements within CustomerInfo. This architecture simplifies managing in-app purchases and subscriber status across your Android application.

How do I transition from raw Play Billing to the RevenueCat Android SDK architecture?▼

Transitioning from raw Play Billing to the RevenueCat Android SDK involves understanding how RevenueCat reorganizes BillingClient, Google Play Developer API, and RTDN into a single SDK. This architecture handles purchase synchronization and entitlement management without direct Play Billing interactions.

Do I need to know the RevenueCat dashboard to use the Android SDK components?▼

Yes, using the RevenueCat Android SDK requires knowledge of the RevenueCat dashboard to effectively configure and map Products, Packages, Offerings, and Entitlements. The dashboard serves as the central hub for managing your app's subscription architecture and product relationships.

What is CustomerInfo in the RevenueCat Android SDK and how does it work?▼

CustomerInfo in the RevenueCat Android SDK is an object that provides real-time subscriber status and active Entitlements for a user. It works by aggregating purchase data from the reorganized BillingClient and Google Play Developer API to deliver accurate subscription information.

Why use RevenueCat for Android in-app purchases instead of direct BillingClient integration?▼

Using RevenueCat instead of direct BillingClient integration abstracts the complexity of raw Play Billing by unifying BillingClient, Google Play Developer API, and RTDN into a single SDK. This approach simplifies architecture by handling Offerings, Packages, and Entitlements automatically.