subscriptions
Installation
SKILL.md
Subscriptions
Google Play models every subscription as three nested objects: Subscription, Base Plan, and Offer. The catalog you build in the Play Console must match the catalog your app queries and the paywall your users see. This skill guides you through the hierarchy, helps you pick a catalog shape, and shows how to query and launch the right offer with Play Billing Library 9.x.
Phase 0: Intent
Confirm the goal before you touch the Play Console or write code. Answer these questions first.
| Question | Why it matters |
|---|---|
| What product are you selling? | One Subscription per logical entitlement (Premium, Cloud Storage, etc). |
| How many billing periods? | Each billing period becomes a separate Base Plan under that Subscription. |
| Do you need trials, intro pricing, upgrade incentives, or win back? | Offers attach to Base Plans. Prepaid Base Plans cannot carry Offers. |
| Who decides who qualifies for an offer? | Google managed eligibility for new customer trials, developer determined for everything else. |
| Do you have add ons? | Each add on is a separate Subscription. Your backend, not Google, enforces the parent relationship. |
Stop here if the answer to "what are we actually selling" is not yes or no clear. Modeling a fuzzy catalog locks you into Product IDs that you cannot rename later.