In-app subscriptions for digital content apps
Short answer: Both app stores sell auto-renewing subscriptions on your behalf, but they model them differently. Apple groups subscription tiers into a subscription group so people can move between them; Google Play uses one subscription product with base plans and offers. In both cases your app shows the purchase screen, the store takes payment, and your server should keep its own record of who's entitled to what, kept up to date by the stores' server notifications. Plan for trials, restoring purchases, failed payments and cancellations from day one.
For a language-learning app, a meditation library or a course platform, subscriptions are often the business model. The store side is well documented but scattered, and the part founders most often underestimate is not the purchase button: it's keeping access correct when cards fail, people switch plans or reinstall on a new phone.
How store subscriptions are structured
Apple: subscriptions inside groups
Apple's subscriptions overview explains that each auto-renewable subscription is assigned to a subscription group: a set of options with different access levels, prices and durations that people choose between. Within a group you rank subscriptions by level (level 1 offers the most), and that ranking determines upgrade, downgrade and crossgrade paths. Because the group is the set of options people choose between, a monthly and an annual plan for the same content belong in the same group.
Google Play: one product, several base plans
Google's Play Billing subscriptions guide describes a subscription as a recurring transaction that grants entitlements for a period. Through base plans and offers you create several configurations of the same subscription product, for example a monthly and an annual base plan, an introductory offer for people who've never subscribed, or an upgrade offer for existing subscribers.
A hypothetical mapping
A hypothetical Australian language app with "Standard" and "Plus" tiers, monthly and annual:
| Concept | App Store | Google Play |
|---|---|---|
| Container | One subscription group, "Learning access" | Two subscription products, Standard and Plus |
| Tiers | Plus at level 1, Standard at level 2 | Separate products |
| Durations | Four subscriptions: Standard monthly/annual, Plus monthly/annual | Monthly and annual base plans in each product |
| New-user trial | Introductory offer on each subscription | Offer on each base plan, eligible to new subscribers |
Trials and offers
On Apple, offer types include introductory offers, promotional offers, win-back offers and offer codes. Apple says you can create an introductory offer for each subscription per territory, and customers can redeem one introductory offer per subscription group. Offer codes can be one-time-use codes or custom codes such as a campaign word.
On Google Play, offers sit on base plans and can target new subscribers or upgrades, as described above.
Keep trials simple: one clear free period or discounted first term, shown with the full price that follows. Apple's guidance asks that the amount to be billed be the most prominent pricing element in the purchase flow.
Setup steps per store
App Store
- Create the subscription group and subscriptions in App Store Connect, with names, prices and descriptions; these appear in the in-app purchases section of your product page.
- Rank subscriptions by level within the group.
- Add any introductory offer.
- Build the purchase screen with StoreKit, including a way for existing subscribers to sign in or restore purchases, and links to your terms of use and privacy policy, as Apple's guidance lists.
- Enable App Store Server Notifications so your server receives real-time status changes.
- Consider enabling Billing Grace Period: Apple tries to recover the payment while the subscriber keeps access, for 3, 16 or 28 days depending on your setting.
- Decide whether to enable Family Sharing, which lets a subscriber share access with up to five family members.
Google Play
- Create the subscription product and its base plans in Play Console.
- Add offers to base plans where needed.
- Integrate the Play Billing Library for the purchase flow.
- Acknowledge purchases promptly after they're verified; Google's guide stresses acknowledgement, with tight deadlines for prepaid plans.
- Set up real-time developer notifications to your backend.
- Configure the recovery period: Google describes an optional grace period, where the user should keep access, followed by account hold, where access should be removed until payment is fixed.
What your backend must handle
Whichever store, your server is the source of truth for access.
- Entitlement records. For each user: which product or plan, which store, current status, renewal date.
- Server notifications. Process Apple's notifications and Google's RTDNs to update status on renewals, cancellations, expiries, refunds and billing problems. Google's guide, for example, describes cancellation-scheduled, cancelled and expired notifications for instalment plans.
- Restore and reinstall. When someone signs in on a new device, look up their entitlement on your server, and support the store's restore path. On Google Play,
queryPurchasesAsync()returns subscriptions for the user. - Plan changes. Upgrades and downgrades replace one purchase with another; Google returns a
linkedPurchaseTokenwhen a purchase replaces an existing one, so your records must link them. - Grace and hold states. Keep access during grace periods, remove it during account hold, and tell users how to fix payment.
- Cross-platform users. If someone subscribes on iPhone and later uses Android or the web, your account system, not the store, decides what they can access.
Store rules on linking to web sign-up or payment differ by store and region and change over time; check the current guidelines before you design a web sign-up path.
Handling churn
- Show subscription status in the app, with renewal date and a clear way to manage or cancel, as Apple recommends.
- Use grace periods so a temporary card problem doesn't lock out a paying learner.
- Ask why on cancellation, with a short optional question.
- Plan a win-back: Apple's win-back offers and Play offers for returning subscribers give lapsed users a reason to return.
- Watch which content keeps people. Courses or series that subscribers finish are your retention story.
FAQ
Do I need a server to sell subscriptions?
Technically, a simple app can check purchases on the device. For a content business with accounts across devices, a server-side entitlement record is the reliable route.
Should I offer monthly and annual plans?
Many content apps offer both. In Apple's model they sit in one group; on Play they can be base plans of one product.
What happens when a payment fails?
Both stores retry. Apple's Billing Grace Period and Google's grace period let users keep access while that happens, if you enable them.
Can users move between tiers?
Yes. Apple uses the levels in the subscription group; Google treats it as replacing one subscription purchase with another.
When your content is ready but the subscription plumbing behind it isn't, we can design the entitlement setup across both stores.