Keeping Revenue Without App Store Cuts

The App Store Tax: What It Actually Costs

Apple's App Store charges a 30% commission on all in-app purchases, subscriptions (after the first year, this drops to 15%), and premium app sales. The Apple Small Business Program reduces the rate to 15% for developers earning under $1 million per year, but this threshold resets annually and applies only while the developer remains below it. Google Play applies an identical 30% standard commission with a similar 15% small business tier.

These fees apply to every transaction processed through the platform's mandatory billing system. Apple requires all digital goods and services purchased within iOS apps to use Apple's in-app purchase system, meaning developers cannot use their own payment processor for digital content. Google has similar requirements on Android, though enforcement and specific rules have evolved through regulatory pressure and legal challenges.

For a concrete example, consider a game that generates $50,000 in annual player spending on in-game purchases. Through Apple's standard 30% commission, the developer receives $35,000. Through the Small Business Program at 15%, the developer receives $42,500. Through web distribution with Stripe's 2.9% + $0.30 fee structure (assuming an average transaction of $4.99), the developer receives approximately $47,000. The web developer keeps $5,000 to $12,000 more per year from the same amount of player spending.

At larger scales, the savings become transformative. A game generating $500,000 annually keeps roughly $485,000 on the web versus $350,000 through the App Store at 30%. That $135,000 difference funds additional developers, content creation, or marketing that can accelerate the game's growth further.

What Web Payment Processing Actually Costs

Web games use standard payment processors like Stripe, PayPal, and Braintree instead of platform-specific billing systems. These processors charge per-transaction fees that are dramatically lower than app store commissions.

Stripe charges 2.9% plus $0.30 per successful transaction for domestic cards. For a $4.99 purchase, the fee is approximately $0.44, leaving the developer with $4.55, a retention rate of 91.2%. For a $9.99 purchase, the fee is $0.59, leaving $9.40, a retention rate of 94.1%. Higher-priced transactions retain an even larger percentage because the fixed $0.30 component becomes proportionally smaller.

PayPal charges similar rates, typically 2.99% plus a fixed fee that varies by currency (usually $0.49 for USD transactions). PayPal's slightly higher fees are offset by its broad consumer adoption and the trust factor of not requiring players to enter credit card details directly into a game site.

The Payment Request API does not charge any fees itself. It is a browser-native interface that streamlines the checkout process using stored payment credentials. The underlying transaction is still processed by your chosen payment processor (Stripe, PayPal, etc.), so the processing fees remain the same. The value of the Payment Request API is reduced friction and higher conversion rates, not lower fees.

For games processing international transactions, additional fees may apply. Stripe charges an extra 1.5% for international cards and a currency conversion fee of 1% when the payment currency differs from the settlement currency. These fees are still far below the 30% app store commission, but they are worth accounting for in revenue projections, especially for games with globally distributed player bases.

Beyond Purchase Fees: The Full Financial Picture

The platform fee comparison extends beyond just transaction processing. App store distribution includes costs and restrictions that do not apply to web games, but web distribution introduces its own operational expenses.

Hosting and infrastructure costs for web games are borne directly by the developer. A typical web game with moderate traffic costs $20 to $200 per month for hosting, depending on asset sizes and player counts. CDN services for fast global delivery add another $10 to $100 per month. These costs are negligible compared to the app store's percentage-based commission, but they are non-zero and must be budgeted.

Payment fraud and chargebacks are handled by the app store in native distribution but are the developer's responsibility on the web. Payment processors like Stripe include basic fraud detection (Stripe Radar), but chargebacks still occur and cost $15 per dispute regardless of outcome. A chargeback rate above 1% can trigger additional processor requirements or account review. Implementing proper server-side validation, using 3D Secure authentication, and maintaining clear refund policies mitigate this risk.

Tax compliance is significantly simpler through app stores, which handle sales tax collection and remittance in most jurisdictions. Web game developers must manage tax obligations themselves, either by integrating a tax service like Stripe Tax or TaxJar, or by handling it manually. This adds complexity and cost, though automated solutions have made it much more manageable in recent years.

Customer support for billing issues falls on the developer for web games. App stores handle refund requests, payment disputes, and receipt management through their own systems. On the web, you need to provide your own support channel and refund process. While this requires investment, it also gives you direct relationships with your paying players, which can be valuable for retention and community building.

Even accounting for all of these additional costs, web distribution retains a significantly larger share of revenue than app store distribution. The hosting, fraud, tax, and support costs rarely exceed 5% to 8% of revenue in total, compared to the 15% to 30% taken by app stores. The net financial advantage of web distribution grows as revenue increases, because the fixed costs of hosting and infrastructure do not scale proportionally with income.

The Regulatory Landscape

The 30% app store commission has faced increasing regulatory scrutiny worldwide. The European Union's Digital Markets Act requires Apple and Google to allow alternative app stores and third-party payment systems on their platforms. Japan, South Korea, and several other countries have passed or are considering similar legislation. Epic Games' legal battles with Apple, while focused on mobile, have elevated public awareness of the platform fee issue.

These regulatory changes are gradually eroding the app stores' ability to enforce exclusive billing requirements. As alternative payment options become available within native apps, the price advantage of web distribution may narrow. However, the web's structural advantage remains: web games never required platform approval, never paid platform fees, and never depended on platform billing. Regulatory changes that make native apps more competitive with web games validate the same principles that web game developers have always operated under.

For developers making distribution decisions today, the web offers certainty. The 2.9% processing fee through Stripe is a stable, transparent cost that does not depend on regulatory outcomes, platform policy changes, or revenue thresholds. App store fees are subject to policy revisions, program requirements, and compliance obligations that can change at the platform's discretion.

When App Store Distribution Still Makes Sense

Despite the fee advantages of web distribution, app stores provide genuine value that may justify their cost for certain games. App store discovery, where players find games through store search, charts, and featured placements, is a powerful acquisition channel with no web equivalent. The app store's built-in billing system reduces payment friction to a single tap with biometric confirmation, which can produce higher conversion rates than web checkout flows. Push notifications, which native apps can send freely and PWAs have limited support for, enable re-engagement campaigns that drive retention.

The optimal strategy for many developers is parallel distribution: a web version for direct sales and web-native audiences, and an app store version for mobile discovery and convenience. The web version processes payments through Stripe at 2.9%, while the app store version uses platform billing at 15% to 30%. Players who find the game through the app store use the more expensive billing path, but the developer captures players they might never have reached through web-only distribution.

Some developers take this further by directing players from the app version to the web version for purchases. This strategy, sometimes called "reader app" behavior (inspired by Kindle and Spotify routing purchases to the web), can reduce the effective platform fee by moving the highest-value transactions off the app store. Apple has historically resisted this practice but regulatory changes are forcing more permissive policies around linking to external payment methods.

Progressive Web Apps: The Best of Both Worlds

Progressive Web Apps (PWAs) offer a middle ground between pure web and native app distribution. A PWA game can be installed on the player's home screen, work offline through service workers, and present a full-screen, app-like experience, all while running in the browser and processing payments through web APIs. The player gets the convenience of a native app, and the developer avoids app store commissions.

PWA support varies by platform. On Android, Chrome provides full PWA functionality including reliable home screen installation, push notifications, and offline support. Players can install a PWA game directly from the browser without visiting any app store, and the game processes payments through Stripe or PayPal at standard web rates. On iOS, Safari supports basic PWA features like home screen installation and offline mode, but push notification support has limitations and Apple does not allow PWAs to be listed in the App Store.

For web game developers, PWAs represent the strongest technical foundation for app-store-free distribution. A well-built PWA game is indistinguishable from a native app in daily use, loads instantly from the home screen, works without a network connection, and keeps 97% of every transaction. The main trade-off is discovery: PWAs must be found through web search, social media, direct links, or QR codes rather than through an app store's built-in browse and search functionality.