Skip to content
AppDues
Log in
Contact salesSign up

Android In-App Subscriptions: From Play Console to Entitlements

Android subscription setup has two halves: defining products in Google Play, then giving your app a reliable way to decide who gets access. This walkthrough follows a small example app that sells unlimited access to cat GIFs through a monthly plan, an annual plan with a trial, and a one-time purchase. The platform-specific steps below describe a subscription-management workflow of the kind documented in the original tutorial; if you use a different subscription-management layer, treat those steps as a reference pattern rather than your own product's instructions.

Plan the product mix before opening the console

Start by writing down what a customer can buy and what each purchase unlocks. In the example, the catalog has three entries: a monthly subscription, an annual subscription with a one-week free trial, and a one-time lifetime purchase. All three unlock the same thing — unlimited GIFs — which matters later when you attach products to a single access level.

A practical checklist before you touch the console:

  • List each price and billing period you intend to sell.
  • Decide which products share the same access outcome.
  • Note which products need a trial or introductory price.
  • Decide whether a billing grace period should keep access open during payment problems, and for how long.

Keeping this list short at first is fine. You can add products later, but the identifier rules below make some choices hard to reverse.

Google Play Billing and where configuration happens

Google Play Billing is the purchase system Google provides for Android apps. Configuration lives in the Google Play Console, and the steps are the same whether you call the Billing Client directly or use a client library such as the Purchases SDK for Android from a subscription-management platform of your choice. The console-side configuration described here does not depend on which client library you pick; only the in-app integration differs later on. Two prerequisites come first: a payments profile on the developer account, and an app that already exists in the console. From there, open the app and find the in-app products area under the store presence menu. That area splits into two tabs — Managed Products for one-time purchases and Subscriptions for recurring ones. The example uses both: two subscription products and one managed product for lifetime access.

Product IDs: choose once, carefully

A product ID is the internal name that identifies a specific product. It is not shown to customers, so pick something readable for your own team that describes the product. Two constraints matter: the ID cannot be changed after creation, and it cannot be reused within the same app.

In the example, the monthly plan uses onemonth and the annual plan uses annual, with the one-time product using onetime. The price table below records the intended prices for that example catalog.

Titles and descriptions are different — those are customer-facing and can be edited later. Treat the ID as permanent and the display text as adjustable.

Pricing, trials, and grace periods

When you add a price, the console lets you set different amounts per country. The example skips that and uses a single price for simplicity. It also skips introductory pricing, though the console supports trials, introductory prices, and grace periods.

The annual plan in the example carries a seven-day free trial. The grace period is a separate setting: it controls how long a customer keeps access while a billing problem is being resolved. Choose a duration that matches how much leniency you want to extend.

One console behavior to watch: a subscription must be marked Active, and after that it cannot be deactivated. Managed products do not share that restriction — they can be made inactive at any time. That difference is worth knowing before you publish a subscription you may later want to retire.

Adding the one-time product

Switch to the Managed Products tab to create the lifetime purchase. Its settings mirror subscription settings but are simpler, since one-time products have no trial or billing period. The example uses the ID onetime. If you are not using a subscription-management layer, this is the point where you continue with the Google Play Billing client integration. The remaining steps cover connecting the same products to a subscription-management platform so that access decisions, entitlements, and offerings are handled outside the app binary.

Service credentials: letting the backend talk to Google

For a backend to verify purchases with Google on your behalf, it needs service credentials. The setup is multi-step but limits what access is granted.

The sequence in the console:

  1. Open the API access area under the developer account and create a new project, or link an existing one.
  2. Create a service account tied to that project.
  3. In the Google API Console, create the service account, give it a name and description, and assign Owner permissions.
  4. Create a JSON key and store it safely — creating the key downloads the file.
  5. Return to the Play Console, where the new service account appears, and grant it access with the Finance role.

One detail is easy to get wrong: the role for the service account in the Play Console should be Finance, not Release Manager. The downloaded JSON key is what the backend uses to communicate with Google and read subscription data, so treat it as a secret.

Registering the Android app

Inside the subscription-management dashboard, create an app and open its Android configuration section. Two inputs are required: the Google Play package name — the same package declared in the Android manifest — and the contents of the JSON key downloaded earlier. Open the key file in a text editor and paste its contents. Name the app, keep the JSON key in a safe place, and save. At this point the backend can authenticate with Google for that package.

Entitlements and offerings: access versus presentation

An entitlement describes something a customer is entitled to, usually as the result of a purchase. In the example there is one entitlement, unlimited, which grants unlimited GIF access. Every product in the catalog — monthly, annual with trial, and one-time — is attached to that same entitlement, so any of the three purchases unlocks the same feature.

Offerings are a separate concept: they define which products are presented together on a paywall or upsell screen. The example uses a single offering containing all three products. Because offerings are configured remotely, you can later test a different combination — for instance, a shorter or longer trial — without shipping an app update.

A useful way to keep the two straight:

  • Entitlement = what the customer can do.
  • Offering = what the customer is shown.

Attach products to entitlements first, then group them into offerings for display.

Where to go after configuration

With products, credentials, entitlements, and an offering in place, the remaining work is client-side: integrating the SDK into the Android app so it can fetch offerings and make purchases. The console-side configuration does not need to change when you do that.

Example product catalog
Product IDPriceBilling
onemonth$0.99monthly
annual$2.99yearly, 7-day free trial
onetime$5.99one-time purchase

These are the example prices used in the original walkthrough, not a recommendation for your catalog. Prices, trials, and grace periods are configured per app in the Play Console.

Frequently asked questions

Can I change a product ID after creating it?

No. A product ID cannot be modified and cannot be reused within the same app. Titles and descriptions, by contrast, can be edited later.

Can a subscription be deactivated after it is marked Active?

Once a subscription is marked Active in the Play Console, it cannot be deactivated. Managed products can be made inactive at any time.

Which role should the service account have in the Play Console?

Finance. Release Manager is the wrong choice for this purpose.

What is the difference between an entitlement and an offering?

An entitlement represents what a customer is entitled to, such as unlimited access. An offering is the set of products presented together on a paywall or upsell screen. Multiple products can map to one entitlement, and one offering can contain several of those products.