AI Deployment
Feature 50  ·  Mobile Apps  ·  Edition Q1 2026

The store stopped
being a shop.

Five features on this desk describe five unrelated events. Each one takes something the developer used to hold - the identity signal, the install pool, the capability, the billing, the price - and moves it somewhere else. The commission was the argument. The dependencies were the change.

Five features on this desk describe five unrelated events. A set of American age-verification statutes. A flat year for installs. A retention gap in AI apps. A collapsing middle in subscription growth. Three regulators arriving at three incompatible remedies.

They have one thing in common, and it is not the app store. It is what the app store became while everyone was arguing about its commission.

Figure 01
Five findings from this desk
Each stands alone. Read together they point the same way.
45
The store became an identity authorityFour states now require the app store to establish a user's age bracket and pass it to the developer, who must act on it and carries the liability for acting wrongly. One of the four laws is in force. Three moved by amendment inside a year.
46
The install pool stopped growingDownloads across both stores rose 0.8% while revenue rose 10.6%. Revenue per download rose about 9.7%. Growth in 2025 came from depth, not reach, and one category appears to have supplied more than the market's entire net download gain.
47
The best-monetising category leaks fastestApps with AI features realise 41% more per user in Year 1 and retain roughly a third fewer subscribers at twelve months. The gap did not exist in the same study a year earlier.
48
The middle disappearedTop-quartile subscription apps grew 80% or more; the bottom quartile lost a third. The top 5% now earn 400 times the bottom quartile, against 200 times two years ago. More than 14,000 new apps arrive monthly.
49
One binary, three regimesJapan published a 5–26% fee schedule. The European Union wrote conduct rules and got a decade of dispute. A US court set link-out commission at zero, and the Supreme Court will hear the appeal.
Each row summarises a feature on this desk and carries its sourcing there. Nothing new is asserted in this table; the conflicts, limits and grading for every figure sit in the feature it came from.

The shape underneath

Take the five findings and ask, of each, what the developer controls.

The age bracket is determined by the store. The size of the install pool is set by the market. The capability an AI app sells is licensed from a model provider. A third of Android churn is a payment retry inside Google's billing system. The commission rate is set in Tokyo, Brussels and a federal courtroom, and one of those three may change its mind next term.

In every case the developer carries the outcome and does not hold the input.

That is the change. The app store used to be a distribution channel with a checkout attached - you built a product, the store carried it, and the arrangement was a fee for shelf space. What it is now is a set of dependencies: identity, demand, capability, billing and price, each supplied by someone else, each with its own failure mode, and none of them auditable from inside your product.

Figure 02
What moved
The same relationship, described before and after.
The store as a shop
The arrangement the industry litigated
What it suppliedDistribution, discovery and a payment mechanism
What it chargedA published percentage of the transaction
The contested questionWhether the percentage was fair
Where growth came fromNew installs, in a market adding them
What the developer controlledThe product, the price and the customer relationship
The store as a dependency stack
The arrangement that arrived while nobody was arguing about it
What it suppliesDistribution, discovery, payment, a verified identity signal, and statutory compliance the developer must consume
What it chargesThree different rates in three jurisdictions, one of them provisional
The contested questionStill whether the percentage is fair
Where growth comes fromRevenue per user, in a market adding almost no installs
What the developer controlsThe product, and a diminishing share of everything around it
This framing is ours. It is a reading of five features, not a finding from any of them, and the right-hand column is an argument rather than a measurement. It is offered because the individual findings are each easy to file as somebody else's problem.

The thing that did not change

Feature 14 of this edition is the counterweight and belongs at the end of this desk rather than the start.

Two landmark rulings, a European regulatory regime and roughly five years of industry argument produced, in the most permissive market available, revenue leaving App Store billing of 3–6%. Ninety-four to ninety-seven per cent of the money stayed where it was. And the store the industry spent half a decade litigating accounts for roughly a third of the mobile app economy; advertising is most of the rest, and almost nobody was arguing about it.

That finding sits underneath everything on this desk. The commission fight was won and the economics barely moved. Meanwhile identity became a platform function, the install market went flat, the fastest-growing category started leaking, the revenue distribution stretched from 200-to-1 to 400-to-1, and three regulators produced three incompatible answers.

None of those were on the agenda. All of them arrived anyway.

What the desk adds up to for a practitioner

The unifying practical point is unglamorous: the competence that decides outcomes has moved from building the product to managing the things around it that you did not choose.

Recovering involuntary Android churn is worth more than most acquisition work and requires no acquisition. Knowing whether your retention fell because your product got worse or because your install base doubled is a cohort chart, not a strategy offsite. Whether your trial is three days or twenty-one is a working-capital decision with a 17-point conversion consequence. Whether your age-rating assessment survives a Louisiana suitability challenge is a review someone has to sign.

None of that is product work. All of it decides more than the next feature will.

Figure 03
The desk in numbers
Every figure here is sourced and graded in the feature it comes from.
MeasureValueFeature
The market
Download growth, iOS + Google Play, 2025+0.8%46
Store revenue growth+10.6%46
Store revenue$167bn46, 14
Revenue per download, change~+9.7%46
Non-game IAP revenue, 2025~$85bn46
Games IAP revenue, 2025~$82bn46
Generative AI app downloads3.8bn46
The economics
Top quartile MRR growth, threshold+80%48
Bottom quartile MRR growth, threshold−33%48
Top 5% against bottom 25%, revenue400×48
New apps entering per month14,000+48
Google Play churn from billing failure31%48
App Store churn from billing failure14%48
Annual subscribers cancelling in Year 1~72%48
AI apps
Realised LTV premium, Year 1+41%47
Twelve-month retention, annual plans21.1% vs 30.7%47
Share of apps carrying AI features27.1%47
Regulation
US state ASAA laws passed445
US state ASAA laws in force145
Japan MSCA fee range5–26%49
US external link-out commission, current0%49
Revenue leaving App Store billing, EU3–6%14
Store share of the mobile app economy~31%14
Figures drawn from three underlying sources - Sensor Tower's State of Mobile 2026, RevenueCat's State of Subscription Apps 2026, and legal reporting on four statutes and one court case. Two of the three are vendors selling into the market they measure. That conflict is disclosed on every figure in every feature and it applies to this table too.

What to do about it

Audit your dependencies, not just your roadmap. Write down the five inputs your business runs on that you do not control - identity signal, install supply, model provider, billing system, commission rate - and what happens to you if each one moves 20% against you. Four of the five moved this year.

Move effort to the operational layer. Dunning, cohort analysis, trial configuration and rating review are unfashionable and they are where the recoverable money is. The store commission is the loudest cost in mobile and, as Feature 14 established, not the largest one.

Assume the calendar will move. Three of four statutory deadlines shifted inside twelve months, and a Supreme Court ruling could reset the US commission. Build compliance and pricing as configuration, not as assumptions.

Distrust every blended benchmark, including ours. A median across 115,000 apps, or a 27.1% AI share spanning categories that run from 61.4% to 6.2%, describes no one. Use them to orient, then measure your own.

Ask what is not being argued about. The industry spent five years on a third of the economy and moved single digits. The changes on this desk arrived with no campaign behind them at all. That asymmetry is the most reliable thing in this edition.

How we did this

Where this comes from
This feature introduces no new sourced claims. Every figure is carried from Features 14 and 45–49 of this edition, where its source, tier, conflicts and limits are stated in full.
Underlying
Three source families sit beneath the desk: Sensor Tower's State of Mobile 2026, RevenueCat's State of Subscription Apps 2026, and legal reporting on four state statutes, one Japanese Act and one US court case.
Worth knowing about the source
Two of the three quantitative source families are vendors selling into the market they measure. Both publish panel or customer-base estimates rather than audited platform data. This is the single largest limitation of the desk and it is stated here as well as in each feature.
What's ours, not the source's
The dependency-stack framing, the shop-to-stack comparison and the argument that competence has moved to the operational layer are entirely ours. They are a reading of six features, not a finding from any of them.
Not advice
Nothing here is legal, investment or financial advice.

What this doesn't prove

  • That the five findings are causally connected. They are contemporaneous. The common shape we describe is an interpretive frame, and a different frame would fit the same five facts.
  • That platform dependency is new. Developers have depended on app stores since 2008. The claim is that the number and consequence of those dependencies grew materially in one year, not that the relationship changed in kind.
  • Anything about the majority of apps. Two of our three source families cover subscription apps and store transactions. Advertising-monetised apps are most of the store by volume and are largely absent from this desk.
  • That any of this generalises outside the measured markets. The statutes are American, the MSCA is Japanese, and the market data is dominated by the United States, Western Europe and Japan.
  • That the direction persists. Every trend on this desk is drawn from one or two years of data. Several of them - the AI retention gap, the annual cancellation rate - moved sharply enough in a single year that sample composition is a live alternative explanation.
  • What to build. This desk is about the conditions a product operates under. It says nothing about which products are worth making.

Sources for this feature

  1. Features 14, 45, 46, 47, 48 and 49 of this edition, where all sourcing, grading and conflicts are stated. Another feature in this edition
  2. Jonathan Briskman, 2026 State of Mobile, Sensor Tower, January 2026. sensortower.com From a company that sells into this market - vendor research, panel-derived
  3. Lorelei Whitman, The State of Subscription Apps in 10 minutes, RevenueCat, 19 March 2026. revenuecat.com A named study, reported by someone else - named study, vendor-conflicted
  4. Key Developments With State App Store Accountability Acts, Wiley Rein LLP, 8 June 2026. wiley.law A named study, reported by someone else - named law firm
End of Edition Q1 2026
Seven Desks · Fifty Features
Marketing Legendary publishes quarterly. The next edition follows.
AS
The practice behind this desk

App Legendary

All things mobile apps - discovery, acquisition and store performance. We start with the volume-versus-price question, because it determines every decision after it.