Is There Room to Live After the 30% Cut?
Every mini-game team does the same back-of-napkin math: revenue minus 30% equals survival. Then they stop there, as if 30% were a law of physics. It isn't. It's a toll booth on one specific road — and there are other roads. Let's pick apart what the cut actually is, and what's left once you count the things the headline number hides.
Q: Is the 30% store cut fixed?
For a native app distributed through the App Store or Google Play, yes — it's contractual and enforced at the payment layer. But "30%" only describes one distribution path. The moment your game runs inside a runtime or a super-app instead of a standalone native binary, the fee structure changes, because the entity taking the payment isn't the one that owns the device. The tax is a toll on a road, not a tax on gravity.
Q: Can a runtime or mini-game platform really beat the 30%?
It depends what's being charged for. A runtime that hosts your game and handles payments takes a platform share, but that share is negotiated and usually lower than a store's — and, crucially, it often bundles hosting, distribution, and a shared user base you'd otherwise pay user acquisition for. Teams on a runtime commonly keep far more than the 70% survivors of the app-store tax, partly because the runtime's cut replaces both a store fee and a slice of marketing spend.
Q: Is routing payments through webview to dodge the store cut compliant?
This is the line you don't cross carelessly. Stores prohibit steering users to external payment for digital goods inside a native app, and they enforce it. A mini-game living in a runtime is a different animal: the runtime is the distribution surface, so the payment relationship is with the runtime, not a side-channel bolted onto a native app. Building outside the native store's payment wall is legitimate; sneaking around it from the inside is how teams get banned.
Q: How do I actually compute what I keep?
Stop staring at the headline fee and build the full stack: platform share, plus payment processing at 2–3%, plus UA cost — the silent killer — plus chargebacks and refunds. A 30% store cut on a game that then spends 40% of revenue on UA is worse than a 15% runtime share on a game that inherits a warm user pool. Net take is the only number that pays salaries.
Q: Which channel should a small team pick?
The one where the channel's cut buys you something you couldn't afford alone: a user base, a payment rail that clears in your target market, or instant distribution without an app-store review cycle. Small teams die on customer acquisition, not on fee percentage. Pick the channel that hands you players, then optimize the take from there.
| Channel | Typical cut | What you get | The catch |
|---|---|---|---|
| App Store / Google Play | 15–30% | billing, trust, reach | locked payment, review cycle |
| Runtime / mini-game platform | ~10–20% | hosting + shared users + local pay | you're on their rails |
| Web direct (webview) | payment processing only (~3%) | full control | you own all UA |
| Carrier / e-wallet billing | 10–25% | reaches the unbanked | per-market integration |
