Apple's App Store revenue just fell for the first time in four years — what it means for app monetisation strategy

Morgan Stanley reported Apple's App Store net revenue down 0.6% year-on-year in August 2026, with US commission revenue off 18% since January as more apps route payments around Apple's cut — a signal that in-app monetisation design now needs deciding at the commissioning stage, not bolted on after launch.

Apple’s App Store net revenue dropped 0.6% year-on-year as of mid-August 2026 — the first decline in four years — according to Morgan Stanley’s analysis of monthly App Store data. The bigger number is underneath it: US App Store commission revenue is down 18% since the start of the year. The cause is a court injunction, in force since April 2025, that forces Apple to let developers point users to external payment pages without paying Apple a cut on those transactions. Revenue is also softening in Brazil and Japan, both of which introduced similar steering rules this year, alongside weaker demand for games and currency effects.

For four years, “put it on the App Store and pay the 30%” was simply how in-app monetisation worked. That assumption no longer holds. Developers can now legally build a payment flow that never touches Apple’s checkout at all — provided they’re willing to build and maintain that flow themselves, handle the compliance and UX tradeoffs, and accept that Apple still gates how the link to it can be presented in-app.

Why this matters for anyone commissioning an app

This isn’t a story about Apple’s balance sheet — it’s a story about a decision that used to be an afterthought becoming a genuine build-time choice. Whether to route payments through Apple’s IAP, an external checkout, or a hybrid of both changes your margins, your app’s approval risk, and how much backend work is needed before launch. Get it wrong and you’re either giving away 30% you didn’t need to, or you’re rebuilding your payment flow mid-flight once the revenue math becomes obvious.

So what

If you’re planning a subscription or in-app-purchase product for iOS, monetisation architecture belongs in the initial technical scope, not a post-launch retrofit. We build this decision into the plan from day one — see our iOS & Android services or get in touch to talk through what payment routing makes sense for your product.

← All research

More research.

GitHub's Copilot metrics now count OpenCode and Claude Code traffic: who really uses which AI coding tool

On 23 October 2026 GitHub added a per-tool breakdown to the Copilot usage metrics API, so tools such as OpenCode and Claude Code are counted even without editor telemetry. It shows how mixed the AI coding tool stack inside software teams has become.

Read ›

GitHub Copilot retires Claude Opus 5 and GPT-5.6 Terra on 16 November: the model-churn bill for buyers

GitHub has announced that Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra leave every Copilot experience on 16 November 2026. For anyone commissioning AI-assisted development, model retirement is now a monthly event to plan around.

Read ›

GitHub Copilot now benchmarks how 'agent-first' your developers are against your industry

On 22 October 2026 GitHub added opt-in industry comparisons to its Copilot impact dashboard, ranking firms by share of agent-first developers and by the merge rate of agentic pull requests. Here is how to read the numbers when you are buying software.

Read ›

Apple's new bait-and-switch rule 2.5.19: what it means for AI-built and fast-shipped apps

On 16 October 2026 Apple updated its App Review Guidelines: apps that change after approval can be removed from the App Store and the Developer Program, and AI-generated intimate imagery is now explicitly covered. Here is what founders commissioning an iOS app should check.

Read ›

GitHub Copilot agentic autofix is generally available: AI now fixes security alerts, and bills for it

GitHub made agentic autofix for code scanning alerts generally available on 15 October 2026. Copilot can now fix up to 25 security alerts in one pull request, using AI credits your supplier or your team pays for.

Read ›

GitHub AI Scan for pull requests goes GA: AI security checks for PHP, Terraform and Dockerfiles

GitHub's AI Scan for pull requests became generally available on 15 October 2026, checking languages the standard scanner misses. Findings are advisory and cannot block a merge, which matters when you buy software.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work