Raising subscription prices without a revolt: the consent rules on both stores
Play puts existing subscribers in a legacy price cohort until you migrate them; Apple decides whether your increase needs a notice or a yes. The clocks, the cohorts and the churn math.
Raising a subscription price is the highest-leverage revenue move an app business has, and the highest-churn one if you handle it badly. Both stores now wrap the move in consent machinery: who must agree, who only needs to be told, how far in advance, and what happens to subscribers who say nothing. The rules differ enough between Apple and Google Play that a single "we raised prices" email is not a compliance strategy.
Google Play: legacy cohorts by default
On Play, changing a base plan price leaves existing subscribers where they are: they enter a legacy price cohort and keep paying their original price at renewal. Moving them to the new price is a separate, deliberate act, and it comes in two flavors. An opt-in increase asks each subscriber to agree; an opt-out increase tells them the new price and proceeds unless they cancel. The opt-out path carries an advance notification period of 37 days, and Play itself notifies affected subscribers by email and push starting 30 days before the first charge at the new price. Two more constraints matter: only one price change can be in flight at a time (scheduling a second overwrites the first), and for opt-out increases you must show an in-app notice on every device type where the app is available, with watch devices the sole exception.
Apple: notice or consent, depending on the increase
Apple routes every auto-renewable price increase into one of two lanes based on its own criteria: a notice to active subscribers, or a request for consent. Subscribers on introductory or promotional pricing keep their displayed price for at least one more renewal period, and their notice or consent request goes out at least 30 days ahead. The consent lane has teeth: if the subscriber does not consent before the first renewal at the higher price, the subscription expires at the end of the last cycle at the former price. Like Play, Apple lets you preserve pricing for existing subscribers, and scheduling a second change overwrites the first.
What the machinery means commercially
A price increase is a re-acquisition campaign aimed at your own customers. Every consent request is a cancellation prompt wearing a notification badge, so the increase has to be worth the churn it invites. Grandfathering (preserving the old price for existing subscribers) converts the increase into a new-subscriber-only change - slower revenue, near-zero churn, and a loyalty story you can tell. The hybrid play - grandfather for a grace period, then migrate with a long runway - uses both stores' scheduling mechanics deliberately instead of tripping over them.
Practical checklist
- Model churn before you touch Console or Connect. A 20% price rise that loses 15% of subscribers is a win; one that loses 30% is a bonfire.
- Respect the clocks. 37-day advance notice on Play opt-out increases, 30-day minimum on Apple's offer-price subscribers - schedule migrations with these, not against them.
- One change at a time. Both stores overwrite a pending change with the next one. Batch your pricing decisions.
- Say it in the app too. Play requires the in-app notice for opt-out increases; doing the same on iOS is cheap goodwill that support tickets will thank you for.
The honest summary
Neither store lets you quietly reprice your base. Play defaults to grandfathering until you explicitly migrate a cohort; Apple decides whether your increase needs a notice or an explicit yes. Plan increases the way you plan launches - with dates, messaging and a churn model - because that is what the platforms have turned them into.
Sources
- Android Developers: Price changes for subscriptions
- App Store Connect Help: Manage pricing for auto-renewable subscriptions
Prepared with AI assistance and reviewed before publication. Store mechanics are drawn from the Android Developers and App Store Connect Help pages checked on 19 November 2026; Apple's lane criteria and any regional exceptions are governed by those pages, which change - confirm against them before scheduling a real increase.