Mobile monetization is not a pricing decision — it is a systems design problem constrained by rules you don't control. Apple and Google set the commission, the trial mechanics, the win-back tools, and even what you're allowed to say about a cheaper web checkout. A sound in app purchase subscription strategy starts by mapping those constraints, then designs pricing, trials, and retention flows to work with them, not against them.
Quick answer: Store commission runs 15-30% depending on tier and revenue, subscription mechanics (trials, intro pricing, grace periods, win-back) are store-controlled features you configure rather than build, and anti-steering rules limiting web-checkout mentions are loosening in some regions but not gone — so design your monetization system around today's rules with room to adapt.
How much do Apple and Google actually take from subscriptions
Apple and Google both charge a 30% commission on in-app purchases in year one of a subscription, dropping to 15% after a subscriber retains for more than 12 consecutive months. Both platforms also run a Small Business Program at a flat 15% for developers earning under $1 million a year in proceeds. The headline "30% tax" is real but only tells part of the story.
The practical effect: your unit economics change based on subscriber tenure and your company's revenue tier, not just your pricing. A PM modeling lifetime value has to build the commission schedule into the model, not bolt it on afterward.
| Store | Year 1 rate | Year 2+ rate | Small business rate |
|---|---|---|---|
| Apple App Store | 30% | 15% (after 1 year retained) | 15% (under $1M/year proceeds) |
| Google Play | 30% | 15% (after 1 year retained) | 15% (first $1M in annual revenue, all developers) |
Two nuances trip up teams:
- Google's 15% first-million applies to everyone, not just small developers — it's a bracket, similar to income tax, so even large companies pay 15% on their first $1M in Play Store revenue each year.
- Apple's small-business rate is an eligibility program, not a bracket — cross $1M and you're moved to the standard 30% rate going forward, which can produce an uncomfortable step-function in margin right when a subscription product is gaining traction.
Either way, model the commission curve over a subscriber's lifetime, not as a flat "take 30% off the top" assumption. A $9.99/month subscriber who churns in month 4 nets you meaningfully less, proportionally, than one who reaches month 13.
Where the web-checkout alternative fits in
Processing payments outside the app (web checkout via Stripe, Braintree, or in-house billing) typically costs 2-5% in payment processing versus the 15-30% store cut — a real margin difference, but one bounded by store rules on how you can point users there. That tradeoff, and how aggressively you can surface it, is the subject of the anti-steering section below.
What subscription mechanics do stores actually give you to configure
Apple and Google both expose a standard toolkit — free trials, introductory pricing, grace periods, and win-back offers — as store-level configuration, not custom code you build. Your job as a monetization PM is choosing which levers to pull for which segment, not engineering the plumbing underneath them.
- Free trials: a set number of days (commonly 3, 7, or 14) before the first charge; the store handles the countdown and reminder notifications.
- Introductory offers: a reduced price for an initial period (e.g.,
$0.99for the first month, then full price) — a proven lever for narrowing the gap between "download" and "pay full price." - Grace periods: when a renewal payment fails (expired card, insufficient funds), the store keeps access active for a defined window (typically 16-60 days depending on platform and billing type) while retrying the charge, instead of cutting the user off instantly.
- Win-back / retention offers: discounted pricing shown to users who cancelled or let a subscription lapse, aimed at reactivation without a support conversation.
- Family sharing / plan groups: users can share certain subscriptions in a household group, which changes your effective revenue-per-download math.
Why grace periods matter more than PMs assume
Involuntary churn — failed payments, not deliberate cancellation — is a large and under-discussed share of subscription loss on mobile, and grace periods are the store's built-in defense against it. If you're not actively monitoring how many subscribers pass through the grace-period retry window versus how many convert back to active billing, you're missing a lever that costs nothing to pull.
Treat grace-period recovery rate as a first-class retention metric, not an edge case buried in billing logs.
Trial length is a segmentation decision, not a universal default
A 3-day trial forces a fast value judgment; a 14-day trial gives a habit time to form but delays revenue and increases the population who trial and forget. The right length depends on how quickly your core job (see Customer Jobs framing below) delivers a felt outcome — a fitness app teaching a habit needs longer than a utility that proves value in one session.
How does the App Store's anti-steering policy limit mentioning a cheaper price
Anti-steering rules historically barred apps from telling users, inside the app, that a subscription is cheaper on the web — but regulatory pressure (the EU's Digital Markets Act, a U.S. court ruling in Epic Games v. Apple, and Japan's app-market legislation) has forced real, if uneven, cracks in that wall. The result is a patchwork: what you can say and link to now depends on the user's region and platform.
Historically, both Apple and Google prohibited in-app language pointing users to external, cheaper purchase options — no "save 20% by subscribing on our website" banners, no direct links out to a checkout page. That is still the default posture in most of the world. But:
- In the European Union, the Digital Markets Act has forced Apple to permit external purchase links and alternative payment processing for apps distributed there, under a revised (and still-contested) fee structure.
- In the United States, the Epic Games v. Apple injunction — upheld through appeals — requires Apple to allow external purchase links in the U.S. App Store without the prior "scare screen" friction Apple initially added.
- Google Play has separately settled litigation and rolled out limited alternative-billing pilots in several markets, ahead of and alongside its own regulatory pressure.
What this means for a monetization roadmap
Don't build a single global monetization flow and assume it travels. Build region-aware entitlement and pricing logic from the start, because "can we link to web checkout" is now a per-region feature flag, not a fixed policy.
| Region/jurisdiction | Can link to external checkout in-app? | Notable driver |
|---|---|---|
| European Union | Yes, with conditions | Digital Markets Act |
| United States (Apple) | Yes | Epic v. Apple injunction |
| Google Play (multiple markets) | Yes, via alternative billing pilots | Antitrust settlements |
| Most other regions | Generally no | Standard store terms still apply |
Treat this table as a snapshot, not a permanent map — store terms are being amended faster than most product roadmaps move, so whoever owns monetization should own a quarterly policy-diff review as a standing task, the same way security teams track CVEs.
How do you decide between in-app purchase convenience and web-checkout margin
Choose in-app purchase when trust, one-tap conversion, and platform-native billing UX outweigh the commission cost — typically for impulse or low-friction upgrades — and choose (or add) web checkout when your audience is already engaged, price-sensitive, and willing to leave the app briefly for a meaningfully lower price. Most mature subscription products run both, deliberately.
Consider a hypothetical $12.99/month productivity app subscription:
- IAP path: user taps subscribe inside the app, Face ID/fingerprint confirms, store takes 30% (year 1) — net to you roughly
$9.09/month. Zero friction, highest conversion rate at the moment of intent. - Web checkout path: user is directed (where regionally permitted) to a browser, enters card details via Stripe, you pay ~3% processing — net to you roughly
$12.60/month. Meaningfully higher margin, but conversion drops because leaving the app introduces friction and drop-off risk.
The math favors web checkout on margin per converted user, but IAP usually wins on total converted users, especially for anyone who hasn't already decided to subscribe. A reasonable framework:
- Default to IAP for first-time subscribers and impulse conversions — the friction cost of leaving the app usually exceeds the margin gained.
- Offer web checkout as a secondary path for engaged free users, renewal upsells, or win-back campaigns, where users are already invested and price-sensitive.
- Never make IAP feel like the "worse" option inside the app where anti-steering rules still apply — you can build web-checkout awareness through email, onboarding outside the app, or region-permitted in-app messaging, but don't create a compliance problem chasing a few points of margin.
What's a sound framework for running mobile subscription pricing experiments
A disciplined pricing experiment separates price level, trial length, and offer framing as independent variables, tests one at a time against a clear north-star metric (usually trial-to-paid conversion or 90-day retained revenue), and runs long enough to capture at least one full billing cycle plus churn signal. Skipping this structure is how teams end up with pricing "intuition" instead of evidence.
A five-step framework
- Segment before you test. New users, lapsed users, and win-back candidates respond to price differently — testing one blended cohort hides real effects.
- Isolate one variable per test. Price tier, trial length, and intro-offer framing each move conversion independently; changing two at once makes the result unattributable.
- Pick the right window. A 7-day trial needs at least 30-45 days of observation to see the first renewal outcome, not just trial-to-paid.
- Weight for commission tier. A price test that looks like a win on gross revenue can be a loss on net revenue once you factor in whether the cohort crosses the small-business or 12-month retention threshold.
- Decide the metric before you look at data. Trial-to-paid conversion, 90-day retention, and ARPU-per-install can point in different directions from the same test — pre-commit to which one wins ties.
Fogg's Behavior Model (B=MAP: motivation, ability, trigger) is a useful lens for trial-length decisions — a trial should be long enough for ability (learning the product) to catch up with motivation (why they downloaded), and the offer should trigger conversion right when that gap closes, not before.
Pricing signals worth tracking beyond conversion rate
- Refund/chargeback rate by price tier — a spike often signals a price that felt fair at tap-to-subscribe but not at first charge.
- Grace-period recovery rate — see above; a weak recovery rate can quietly erase gains from a "successful" price increase.
- Time-to-first-value relative to trial length — if most conversions happen on day 6 of a 7-day trial, you likely have room to shorten it.
Bringing subscription pricing back to the actual job the user is hiring your app for
Store rules set the boundaries, but the pricing decision inside those boundaries should follow the outcome a user is actually paying for — not a competitor's price point or a round number that feels safe. This is where Jobs to Be Done thinking earns its keep in a monetization roadmap: a subscriber isn't buying "premium," they're hiring your app to make progress on something specific.
Prodinja's Customer Jobs tooling — built on JTBD framing, Ulwick-style opportunity scoring, and a Forces of Progress view — is designed to help a PM connect a subscription tier directly to the job and outcome a user is hiring the app for, rather than pricing off intuition or a rival's paywall screenshot. Instead of guessing whether a $4.99 or $9.99 tier "feels right," the exercise pushes you to name the underlying job, size the opportunity gap, and let the tier structure follow that evidence.
That same job-to-outcome logic should also shape which features sit behind which tier, and how a Customer Journey emotion curve informs when a trial-to-paid prompt lands versus when it feels like an interruption — a pricing screen dropped at a moment of friction converts very differently than one dropped at a moment of felt progress.
For teams building this into a broader release plan, it's worth reading alongside how app store review timing fits into a release plan and the wider view in a complete guide to the mobile PM role, since monetization changes often need review-cycle lead time and cross-functional sign-off before they ship.
Key Takeaways
- Store commission is 30% in year one, dropping to 15% after 12 months of retained subscription, with a 15% small-business rate available under revenue thresholds on both platforms.
- Trials, intro pricing, grace periods, and win-back offers are store-configured mechanics — your leverage is in choosing settings and monitoring recovery rates, not building the plumbing.
- Anti-steering rules are cracking unevenly by region (EU's DMA, the U.S. Epic v. Apple ruling, Google's alternative-billing pilots), so region-aware entitlement logic is now a real product requirement.
- IAP usually wins on conversion volume; web checkout usually wins on margin per converted user — most mature products run both, sequenced by user intent and region.
- Pricing experiments need isolated variables, commission-tier-aware metrics, and a pre-committed north-star to avoid intuition dressed up as data.
- Tying subscription tiers to the actual job a user is hiring the app for, rather than to a competitor's price point, is a stronger foundation for both pricing and packaging decisions.
Frequently Asked Questions
What percentage does the App Store take from subscriptions?
Apple takes 30% of subscription revenue in a subscriber's first year, dropping to 15% after they've been subscribed for more than 12 consecutive months, and 15% flat for developers enrolled in the Small Business Program under $1 million in annual proceeds.
Can I tell users about a cheaper price on my website inside my app?
It depends on the user's region: the EU (via the Digital Markets Act) and the U.S. (via the Epic Games v. Apple ruling) now permit external purchase links in-app, while most other regions still fall under standard anti-steering restrictions — so this needs to be a region-aware setting, not a single global choice.
How long should a mobile app's free trial be?
Trial length should match how quickly your core job delivers a felt outcome — shorter trials (3-7 days) suit apps that prove value fast, while longer trials (14 days) suit products building a habit; test length as its own variable rather than defaulting to an industry-standard number.
What happens when a subscriber's payment fails?
Both Apple and Google offer a grace period — commonly 16-60 days depending on platform and billing type — where access stays active while the store retries the failed charge, giving you a built-in recovery window before treating the user as churned.
Is it worth building a web checkout option alongside in-app purchases?
Usually yes for engaged, price-sensitive, or lapsed users, since payment processing (roughly 2-5%) is far cheaper than the store's 15-30% commission — but it should supplement IAP for first-time conversions rather than replace it, given the friction cost of leaving the app.