Phil Schiller's App Store exit is a warning for indie devs
Phil Schiller stepped back from the App Store as Apple's new leadership pushes for recurring revenue. Here's what a margin-hungry App Store means for small developers in Sri Lanka.
Phil Schiller's App Store exit reads like a routine succession note until you read the reported reason. TechCrunch, summarising reporting by Bloomberg's Mark Gurman, says Schiller stepped back partly because he expected a push for better App Store margins to worsen Apple's fights with governments and developers.
That is the sentence worth your attention. The person who ran the store is stepping away as the store gets a revenue target.
🔍 What was reported, and what wasn't
Most of the noise around this story is people filling in blanks. Here is the actual shape of it:
| Claim | Status in the reporting |
|---|---|
| Schiller stepped down as head of the App Store | Reported; exit announced 31 August 2026 |
| He stays at Apple as an Apple Fellow | Reported, on unspecified projects |
| CEO John Ternus and services chief Eddy Cue want better App Store margins and more recurring revenue | Reported by Gurman |
| Schiller thought chasing profit would escalate conflicts with governments and developers | Reported as his reasoning |
| Family time and philanthropy also factored in | Reported |
| Any specific commission rate change | Not reported. No figures, no timeline |
| Direct quotes from Schiller, Ternus or Cue | None in the piece |
No numbers exist yet. Nothing has been announced about rates, tiers, or programme eligibility. Anyone showing you a "new App Store fee" table today is guessing.
💰 "Recurring revenue" is a specific ask, not a vibe
When a services organisation is told to increase recurring revenue from a marketplace it already owns, there are only so many levers. None of these are announced. They're just the levers that exist:
- Commission rates — the headline number, and the most politically expensive to touch.
- Eligibility rules — leaving rates alone while narrowing who qualifies for the reduced tier costs nothing in headlines.
- Paid developer services — search placement, analytics, distribution add-ons billed monthly.
- Shifting the mix — nudging one-time purchases toward subscriptions, because subscriptions are recurring by construction.
- Developer programme pricing — the annual membership fee every publisher already pays.
Lever 2 is the one I'd watch. A rate cut announced with a press release gets defended for years; a threshold quietly redefined in programme terms gets a support-forum thread. If you build on the App Store, the reduced-rate programme's eligibility is the part of your P&L that can move without anyone calling it a price increase.
📊 Run your own numbers before you react
Abstract percentages don't land. Concrete ones do. Take a small app grossing $2,000/month — a realistic ceiling for a solo Sri Lankan developer's side product — and apply the publicly published store tiers. (Again: the report contains no figures. These are today's documented rates, not a prediction.)
| Scenario | Effective store cut | You keep, annually on $24,000 | Change |
|---|---|---|---|
| Small-business tier | 15% | $20,400 | baseline |
| Standard tier | 30% | $16,800 | −$3,600 |
| Hypothetical: you lose reduced-tier eligibility mid-year | ~22.5% blended | $18,600 | −$1,800 |
That $3,600 gap is the entire question. In Sri Lankan terms it's the difference between a side project that funds itself and one you subsidise out of salary. If you want the real number for your own revenue, including the Google Play side, our App Store & Google Play commission calculator applies the 15% vs 30% tiers correctly instead of making you guess.
🌐 The regulator angle, seen from a market with no leverage
Schiller's reported worry was about governments, plural. That framing matters here, because the governments doing the pressuring are not ours.
- The EU and US courts and regulators are where App Store terms get renegotiated.
- Sri Lanka is a rule-taker in that fight. We inherit whatever terms are settled elsewhere, with none of the input.
- Concessions won in Brussels or a US courtroom usually arrive here late, or region-locked and never at all.
There's a second cost we pay locally that developers routinely forget. Money flowing out to platform subscriptions and cloud invoices carries Sri Lanka's digital-services VAT, and it lands on the tools you build with, not just the entertainment you consume. If you've never priced that into your runway, the Sri Lanka digital services VAT calculator will show you what an 18% line item does to a $50/month tool stack.
Key takeaway: Your store commission is not a fixed cost. It's a policy decision made by people you'll never meet, in jurisdictions you don't vote in, and the executive who reportedly resisted raising it just left the job.
🛠️ What I'd change in my own build
Not panic moves. Cheap insurance, ordered by how little effort they take:
- Know your exact tier today. Write the number down. Half the developers I've talked to think they're on the reduced rate and have never verified it.
- Model the 30% case now. If your product only works at 15%, you don't have a business model, you have a discount.
- Keep one non-store channel alive. A plain web checkout, even a low-traffic one, is the only leverage a solo developer has.
- Own your customer relationship. Email list, changelog, direct support. Platform-mediated users aren't yours.
- Version your pricing. Being able to reprice new signups without touching existing ones turns a margin shock into a slow adjustment.
None of this requires a rate change to be worth doing. It's the same work you'd do to survive an exchange-rate swing.
💡 What this means for you
If you ship on the App Store from Sri Lanka, nothing changed on 7 September 2026. No rate moved. No programme closed. The only thing that actually happened is that a long-serving executive who reportedly saw margin pressure as a fight not worth picking has moved on, and the people setting the direction have a revenue goal.
That's a signal about direction, not an event. Treat it that way:
- Don't rewrite your pricing this week based on a report with no figures in it.
- Do find out what a 30% cut does to your annual net, in the next hour.
- Do assume the reduced tier is a concession, not a right. Concessions get revisited.
The useful habit here isn't tracking Apple's org chart. It's building products whose economics survive a platform deciding it wants more. Anything you ship on someone else's marketplace has a variable in it you don't control, and the only honest response is to know exactly how big that variable can get before it breaks you.