Product2 publishers3 min readPublished
Mark Gurman reports that Apple's new chief executive and its services boss want more margin out of the App Store. Nothing is decided, and every lever named so far would be felt by developers before any user notices.
The Product Desk · Product desk

Compiled by The Product DeskSomething wrong?How this is made
For a small studio, App Store review is the one part of shipping you cannot schedule. The build goes up to App Store Connect, the launch email is already written, and someone at Apple decides when it goes live.
What the reporting describes is a goal, not a mechanism. Gurman has Apple looking for ways to raise margins and squeeze additional recurring revenue from the platform [1], with John Ternus and Eddy Cue driving the effort [2]. The list of ways to get there sits in the write-ups rather than in Apple's mouth, and the two outlets differ on whose list it is: Digital Trends presents the options as part of the report [16], while 9to5Mac introduces them as things Apple could potentially do [15]. For anyone budgeting a release next quarter, that difference matters more than the options do.
Sort them anyway, because they do not all hit the same line. Membership pricing is money, currently $99 a year [8]. 9to5Mac argues Apple could charge more because many small developers already spend $200 a month on Codex and Claude subscriptions [12], which works out to $2,400 a year, roughly 24 times the membership fee [13]. That is a fair comparison of orders of magnitude and a weak comparison of obligation, since the AI subscription is one a developer chose and can cancel this month while the membership is the toll on the only door. Nothing in the reporting says how many developers actually carry that $200. A traffic-based subscription for large developers [9] is a different shape again: variable cost that arrives only once an app works.
Review automation is not a line in the budget. Digital Trends notes the report flags that further automation could be unpopular with users, particularly if it affects how effectively apps are reviewed [7]. 9to5Mac's writer makes the case from Apple's side of the ledger, calling manual review likely costly and not very effective in the age of agentic coding [11]. Both can hold. Users never see review; they see the app that got through it, and a miss shows up on a phone rather than on an income statement.
Then Schiller. He took on the App Store as an Apple Fellow after leaving the marketing SVP job in 2020 [4], and per the reporting he believed these moves would further irk developers and governments, wanted no part of them, and there was no internal blowup [5]. Read plainly, that is a preference and an exit [3]. None of these sources says he stopped anything.
The question to carry into your own planning is which line each lever touches and whether you can pass it on. A membership increase is fixed overhead you absorb at renewal or price into a subscription. A traffic fee is variable and lands on your best month. A review change touches neither; it touches the ship date and the appeal, and there is no field on a pricing page for passing a rejection to a customer.
Digital Trends is right that there is nothing to act on yet, and that developers would feel any of this before users do [14]. Worth noting which lever needs no announcement: fees arrive with a number and a date, and review practice can tighten or loosen quietly.
Ranked by verification strength, evidence, and original report placement.
Bloomberg's Mark Gurman, in his Power On newsletter, reports that Apple wants to "figure out ways to raise margins and squeeze additional recurring revenue from the platform" (the App Store).
Digital Trends reports that the App Store revenue effort is being driven largely by new Apple CEO John Ternus and services chief Eddy Cue.
After stepping down as Apple's marketing SVP in 2020, Schiller became an Apple Fellow and took responsibility for running the App Store.
Digital Trends lists three possible approaches: reducing or eliminating parts of the manual app review process to lower costs, increasing the developer membership fee, and introducing subscription fees for large developers based on traffic.
Apple's developer membership fee is currently listed at $99 per year.
One reported option is charging large developers a subscription fee based on traffic, effectively shifting some infrastructure costs to companies operating high-traffic apps.
Follow any of these and your For You feed starts watching them — no settings page required.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
One newsletter, retold twice
Follow any statement here back and it stops at the same place: one edition of Gurman's Power On, which neither publisher reproduces beyond a single quoted phrase about raising margins. Digital Trends contributes structure and consequence rather than a second source, and Apple has said nothing. The one item a reader can verify without the newsletter is the $99 developer fee. Our own record makes the thinness easy to miss, because the 9to5Mac post appears twice word for word.
No fee or policy change to count
There is nothing here to measure. No fee has moved, no review policy has been published, and both accounts say the report carries no timeline, so any adoption number would be invented rather than observed.
Headlines running ahead of the hedges
The bodies are careful; the headlines less so. Digital Trends' 'Apple may have found another way to make the App Store pay up' and 9to5Mac's 'might soon' both promise more than paragraphs ending in 'unconfirmed' and 'only time can tell'. The gap widens slightly where 9to5Mac's own case for a higher developer fee sits in the same run of sentences as the reported levers, reading as though it were part of them.
Affiliate-funded Apple desks on a rival's scoop
Both publishers depend on Apple news traffic, and 9to5Mac's post finishes with a list of affiliate accessory links, a fair indication of what funds the page. The reporting belongs to a competitor, so what these sites add is interpretation, and in 9to5Mac's case the interpretation argues Apple's side of the fee question: developers paying $200 a month for AI coding tools can bear more than $99 a year. On the other side, the Schiller material comes from unnamed internal accounts that Apple has neither confirmed nor disputed.
Legible sourcing, untested substance
The provenance is clear line by line, so reading this story is straightforward; testing it with what we hold is not possible, given two publishers, one of them present twice, both pointing at a newsletter absent from our record. Anything Apple publishes about developer fees or review terms would move this quickly.
product
Eddy Cue's services division reclaims the App Store after 11 years under marketing1 publisher
product
The Mac mini is sold by the gigabyte, which makes its refresh a DRAM story4 publishers
product
Apple cuts at least 60 Vision roles, and the visionOS roadmap gets harder to underwrite2 publishers
product
Apple reportedly scraps stubby Apple Pencil designed for the foldable iPhone3 publishers
Publishers with included, body-backed reporting in this cluster.
2 articles · September 6, 2026
1 article · September 6, 2026