Every iOS developer knows the number: 30%. That is the commission Apple takes on digital goods sold through the App Store, a toll that has shaped the economics of mobile software since the store launched in 2008. For small developers making less than $1M in annual proceeds, the rate drops to 15%, but the majority of app revenue still passes through the higher tier. This fee is not just a revenue stream for Apple; it is the engine behind the company's services margin, which hovers around 70%, more than double the margin on hardware. The platform tax influences every decision a developer makes: which frameworks to use, whether to offer in-app purchases, and even which markets to target.

The 30% Toll That Shapes Every iOS App's Unit Economics

Apple's commission applies to digital goods and services purchased within an app: subscriptions, in-app currencies, premium content. Physical goods and services outside the app are exempt. Google Play's policy is similar, but enforcement is looser; Android users can sideload apps or use alternative stores, bypassing the commission entirely. That difference matters. In 2020, Epic Games sued Apple, alleging anticompetitive practices. During the trial, internal Apple documents revealed that the company targets a services margin above 70%, a figure that depends heavily on App Store commissions. Some estimates put total commissions paid to Apple since 2008 near $85B, according to analysis firms like Sensor Tower.

The response from large developers has been telling. Netflix and Spotify stopped offering in-app purchases on iOS, directing users to sign up on the web instead. This avoids the commission but adds friction. Spotify's CEO has publicly argued that Apple's rules give its own Apple Music an unfair advantage. Smaller developers often cannot afford to redirect users; they rely on App Store discovery and the convenience of in-app payment. The result is a tiered ecosystem where the commission disproportionately affects independent apps and startups with thin margins.

Apple defends the fee as compensation for the App Store's infrastructure: hosting, payment processing, developer tools, and curation. Critics counter that the payment processing alone costs roughly 2–3%, leaving a large gap. Either way, the 30% toll is a fixed cost that every iOS developer must factor into pricing. A $5 monthly subscription yields $3.50 after Apple's cut, before any other costs. That arithmetic drives many of the decisions described in the sections below.

Why Cross-Platform Frameworks Exist: The Cost of Avoiding Two SDKs

Building separate native apps for iOS and Android requires two teams, two codebases, and double the maintenance. For startups conserving capital pre-Series A, that is often prohibitive. Cross-platform frameworks like Flutter, React Native, and .NET MAUI promise a single codebase that runs on both platforms, cutting development costs substantially. The trade-off is abstraction overhead: the framework adds a layer between the developer's code and the platform's native APIs, which can introduce performance bottlenecks and limit access to platform-specific features.

Airbnb famously abandoned React Native in 2018, citing performance issues and a degraded developer experience. The company's engineers found that the abstraction made it harder to debug and optimize, especially for complex animations and gestures. Flutter, developed by Google, has matured significantly since then. As of Flutter 3.x, the framework is stable, but certain native APIs—like advanced camera controls or ARKit features—still require writing platform-specific code. Developers must weigh the cost of hiring two mobile teams against the cost of working around framework limitations.

Framework choice also affects long-term maintenance. A cross-platform app may launch faster, but as the product grows, the abstraction layer can become a liability. Updates to the underlying platform (iOS or Android) can break the framework, requiring urgent patches. Some teams start with a cross-platform framework and later rewrite critical modules in native code. Others commit fully to one platform initially, then expand. The decision is rarely permanent, but it has real financial implications: a rewrite can cost months of developer time and delay feature releases.

The Hidden Cost: App Store Review Delays and Rejection Risk

Beyond the commission, developers face a less visible cost: the time and uncertainty of the App Store review process. Apple reviews every app and update manually, with average review times of 24 to 48 hours. However, during peak periods like WWDC or the holiday season, delays can stretch to several days. For a startup racing to fix a critical bug or launch a time-sensitive feature, a multi-day wait can mean lost revenue and user frustration.

Rejection rates hover around 20% for first submissions, according to developer surveys. Common reasons include missing login credentials for review accounts, placeholder UI elements, insufficient payment disclosures, and vague metadata. Each rejection triggers a cycle of rework, resubmission, and another wait. The cost is not just the developer's hourly rate but the opportunity cost of delayed releases. Some teams budget an extra week per release just for review uncertainty.

Google Play's review process is largely automated and faster, with fewer subjective rejections. However, automated checks can miss issues that later cause policy violations. The trade-off is clear: Apple's manual review provides a higher baseline of quality and security but at the cost of developer agility. For apps in regulated categories like finance or health, Apple's scrutiny can be a benefit, as it reduces the risk of malicious software. But for a small team iterating quickly, the review process feels like a bottleneck that competitors on Android do not face.

How Developer Tools Vendors Capture Margin in the Middle

Once an app is built and accepted, the costs continue. Modern iOS apps integrate an average of 18 third-party SDKs, according to a 2025 industry report. These SDKs provide analytics, crash reporting, payment processing, authentication, and more. Each vendor charges a fee, often based on monthly active users or transaction volume. RevenueCat, a popular subscription management tool, charges from $0 to $195 per month depending on the number of tracked transactions. Firebase, owned by Google, offers a free tier but charges for usage beyond certain limits—cloud functions, database reads, and analytics events all add up.

Payment processors like Stripe take roughly 2.9% plus $0.30 per transaction. For a $5 subscription, that is another $0.45, leaving $3.05 after Apple's commission and Stripe's fee. Hosting and API costs vary widely: a simple backend might cost $0.01 per user per month, while a data-intensive app could cost $0.10 or more. Crash reporting tools like Sentry charge based on event volume, typically $0.02–$0.05 per user per month. Analytics tools like Amplitude or Mixpanel add similar amounts.

These costs scale linearly with the user base. A successful app with 100,000 paying users might spend thousands per month on infrastructure and tools. The cumulative effect is that net margin after all platform costs often falls to 50–60% of gross revenue, before marketing and salaries. Developers must either raise prices or accept thinner margins. Some attempt to reduce SDK bloat by building custom solutions, but that trade-off trades vendor fees for engineering time.

Apple's Services Revenue Target: $100B Annual Run Rate by 2028

Apple's services segment generated roughly $85B in fiscal 2025, growing about 12% year over year. App Store commissions account for an estimated 40% of that revenue, making it the largest single contributor. The services margin—around 70%, according to financial filings—contrasts sharply with hardware margins, which hover near 35%. This margin is the reason Apple pushes services aggressively. The company has publicly stated a goal of reaching a $100B annual run rate for services by 2028, a target that requires continued growth in App Store commissions, iCloud+, Apple Music, and advertising.

Search Ads within the App Store have become a significant revenue line, estimated at over $6B annually. These ads let developers bid on keywords to appear at the top of search results, competing with organic discovery. For many developers, Search Ads are now a necessary expense to maintain visibility, adding another cost to the platform stack. Apple's advertising business is still small relative to Google's, but it is growing fast and benefits from the same captive audience that pays the commission.

To hit $100B, Apple will need to expand services into new markets and raise prices on existing ones. iCloud+ subscriptions have increased in price in some regions. Apple Music and Apple TV+ face stiff competition from Spotify and Netflix, which avoid the App Store commission on their own platforms. The tension between Apple's services revenue goals and developer interests is unlikely to resolve soon. As services grow, the platform tax may become more entrenched.

What Developers Actually Net After Platform Stack Costs

Let's walk through a concrete example. Assume a developer charges $5 per month for a subscription. Apple takes 30%, leaving $3.50. A payment processor like Stripe takes 2.9% plus $0.30, or roughly $0.45 on that $5 transaction, leaving $3.05. Hosting and API costs might be $0.05 per user per month for a typical backend. Analytics and crash reporting add another $0.03. That leaves $2.97 per user per month, or about 59% of gross revenue. Before marketing costs, which can easily double the effective customer acquisition cost.

For a free app with in-app purchases, the math is similar. A $1 purchase yields $0.70 after Apple's cut, then $0.68 after payment processing, then further reductions from SDK costs. Developers targeting lower price points face particularly thin margins. A $0.99 purchase, after Apple's 30% and Stripe's fee, leaves around $0.60—barely enough to cover hosting for a month.

These numbers explain the trend toward higher subscription prices. Many developers have raised prices to $10, $15, or even $20 per month to maintain healthy margins. Users may balk, but the alternative is unsustainable unit economics. The platform tax is not just Apple's commission; it is the entire stack of costs that accumulates between the developer and the user. Each layer takes a slice, and the developer absorbs the remainder.

The Android Escape Valve: Alternate Stores and Sideloading Economics

Android offers alternatives that iOS does not. The Samsung Galaxy Store charges a 20% commission, and the Epic Games Store on Android takes only 12%. Sideloading—installing an APK directly from a website—avoids commissions entirely, but conversion rates drop significantly. Users are less likely to trust an unknown download source, and the friction of enabling sideloading in settings can reduce conversion by 30–50%, according to developer reports. The Amazon Appstore, preloaded on Fire devices, is an option but rarely used for paid apps outside Amazon's ecosystem.

The European Union's Digital Markets Act (DMA) will change the landscape for iOS. By 2027, Apple must allow sideloading in Europe, opening the door to alternative app stores and direct downloads. Developers targeting the EU market may see 10–15% higher net revenue per user post-DMA, as they can avoid Apple's commission entirely. However, the DMA also imposes new requirements on Apple, such as allowing third-party payment processors, which may reduce some of the friction.

The DMA's impact will be limited to Europe initially, but other jurisdictions are watching. Japan and the UK have proposed similar legislation. If sideloading becomes widespread, Apple's services revenue could face pressure. The company has argued that sideloading compromises security and user experience, but developers see it as a necessary escape valve. The outcome will depend on regulatory momentum and Apple's willingness to adapt its business model. For now, the platform tax remains the dominant reality for most iOS developers.

Trade-Offs in App Monetization Strategies

Developers have several options to mitigate the platform tax. One common approach is to offer a freemium model with limited features and a paid subscription for full access. This allows users to try the app before committing, but the conversion rate from free to paid is often low, around 2–5% for many apps. Another strategy is to use advertising revenue instead of in-app purchases. Ads can generate income without Apple's commission, but they often degrade user experience and may drive users away. A third option is to offer a one-time purchase for the full app, but this can limit long-term revenue compared to subscriptions.

Each strategy has trade-offs. Subscriptions provide recurring revenue but require ongoing value delivery to prevent churn. One-time purchases have higher upfront revenue but no recurring income. Ads can supplement revenue but may require a large user base to be meaningful. Some developers combine multiple approaches: a free tier with ads, a low-cost subscription without ads, and a premium one-time purchase for lifetime access. This diversification can stabilize revenue but complicates the user experience and increases development overhead.

An illustrative example is the productivity app Notion. Notion offers a free tier with limited blocks, a personal subscription at $4 per month, and a team plan at $10 per user per month. By avoiding in-app purchases on iOS (users subscribe via the web), Notion bypasses Apple's commission entirely. However, this requires users to visit a website, which adds friction. For a utility app like a weather or calculator app, the friction may be too high, and developers may accept the 30% commission as a cost of convenience.

Ultimately, the choice of monetization strategy is a direct response to the platform tax. Developers must balance user experience, revenue, and growth. The 30% commission is a powerful incentive to steer users toward web-based subscriptions, but not all apps can do so effectively. As the ecosystem evolves, new models may emerge, but for now, the platform tax remains a central factor in iOS app economics.