Skip to content
AppDues
Log in
Contact salesSign up

Google I/O 2022: What the New Subscription Model Means for Android Apps

Google I/O 2022 brought a major restructuring of Google Play subscriptions. Instead of a single billing period with an optional trial or introductory price, Play now separates what a subscriber receives from how that access is sold. That change affects how you configure products in Play Console, how you design offers, and whether you should consider prepaid plans for markets where auto-renewal is less preferred.

The three levels: subscription, base plan and offer

The new structure has three levels. At the top is the subscription itself: the bundle of benefits a user receives. Below it sits a base plan, which sets duration, price and regional availability. At the bottom are offers, which can carry their own pricing phases and eligibility rules. Think of the subscription as the promise, the base plan as the standard way to buy it, and offers as variations for particular audiences or moments in the purchase journey.

Play Console before and after

Before this change, a subscription in Play Console had one billing period, plus an optional free trial and introductory price. The redesigned flow separates benefits from purchase terms, so the same subscription can be sold through different billing periods and offers without duplicating the underlying entitlement.

What automatic migration did to existing products

Existing subscriptions were migrated automatically. The product ID moved to the new subscription, a base plan was created with the same billing period, and free trials and introductory prices became offers. Migrated base plans and offers carry a backwards compatible badge, meaning they continue to work with the Billing Library version used by the SDK at the time. That badge is your signal that a migrated item is safe to leave as-is.

Flexible offers and pricing phases

Offers are no longer limited to a simple trial or introductory price. You can define phases, where each phase specifies a billing period, price and recurrence. Ordered together, those phases describe the intended journey: for example, a short introductory phase followed by a standard recurring phase. Eligibility controls can also be narrowed to specific user segments. Until SDK support for the new controls is confirmed, edit migrated subscriptions only in a backwards-compatible way so you do not break the existing integration.

Prepaid plans for non-auto-renewing markets

Prepaid plans suit regions where non-auto-renewing subscriptions are preferred. The user pays for one period up front, access does not renew automatically, and the user can top up by paying for another period. This is a different retention mechanic from auto-renewal: instead of preventing cancellation, you rely on the user actively extending access before it ends, so reminders and top-up prompts need to be part of the product design.

Firebase extension and the Play SDK Index

Two other announcements matter for developers choosing and operating SDKs. A Firebase extension lets teams using Firebase store purchase data in Firestore, authenticate entitlements across platforms with Firebase Auth, and track purchase events with Google Analytics. Separately, the Play SDK Index (also called Play Index) publishes information about registered SDKs, including data safety guidance, version adoption and retention rates, with a provider side that surfaces crash insights and critical update notices.

Checklist before you change anything

A practical checklist for reviewing your setup: confirm each subscription maps to one clear set of benefits; check that every base plan has the intended duration, price and regional availability; review migrated offers and confirm the backwards compatible badge is present; decide whether phased offers match the journey you actually want; consider prepaid plans only where non-auto-renewing payment is a genuine market preference; and avoid non-backwards-compatible edits until your SDK integration supports them.

Subscription, base plan and offer at a glance
LevelWhat it definesPractical question to ask
SubscriptionThe set of user benefitsWhat does the user get?
Base planDuration, price and regional availabilityWhat is the standard way to buy it?
OfferPricing phases and eligibilityWhat variation should this audience see?

Based on the three-level structure described in the source material.