App Store Fees Set the Floor Under Every Mobile Studio's Budget

Every mobile budget starts with a subtraction. Before a studio pays a developer, a designer, or a cloud bill, Apple or Google takes a cut of the revenue that funds all three. The rate is roughly 15 to 30 percent depending on the program and the size of the seller, and it applies to the transaction that matters most. This piece is about what that floor does to the rest of the plan.

The commission floor under every budget

Apple's App Store and Google Play both operate as the primary distribution channel for consumer mobile software. Developers publish through the stores, and the stores handle payments, delivery, and a large share of discovery. In exchange, the platform takes a commission on paid apps and in-app purchases. The standard rate has hovered around 30 percent for years, with a reduced tier near 15 percent for smaller sellers and for subscriptions after the first year.

That percentage is not a line item a studio can trim. It comes off the top of gross revenue, which means a five-dollar monthly subscription does not deliver five dollars to the business. The gap between gross and net is the first number a finance-minded founder learns to watch, and it changes what a sustainable price looks like. A product that looks profitable at list price can be marginal once the platform's share is removed.

Small studios feel the floor hardest because they cannot spread fixed costs across a large user base. A team of four paying rent and salaries needs a certain net revenue per month, and the commission raises the gross target needed to hit it. Larger publishers absorb the same percentage, but they negotiate better ad rates, get more organic installs, and have the leverage to run multiple revenue lines.

Consider a two-person team building a note-taking app that sells for US$ 3 a month. At a 30 percent commission, each subscriber delivers roughly US$ 2.10 before payment processing, hosting, and support. If the app needs US$ 4,000 a month to cover two modest salaries and infrastructure, the team needs nearly 2,000 paying subscribers, not the 1,333 the list price implies. That gap is the commission floor in concrete terms, and it explains why so many indie apps raise prices or add a higher tier within the first year.

Why the floor is not negotiable

Alternative distribution remains niche for consumer apps. Web sideloading on Android exists, and the web itself can deliver a progressive web app, but the user behavior and payment infrastructure are not there for most categories. People install from the store they already have open, and they pay through the account already attached to it.

Discovery compounds the problem. Store ranking algorithms drive the majority of organic installs, and a listing that lives outside the store does not appear in those results. A studio that abandons the stores loses the discovery channel along with the payment rail. For a game or a consumer utility, that trade is rarely worth making, which is why the commission holds even when developers complain about it publicly.

Alternative billing options have expanded in some markets following regulatory pressure, but adoption has been slow. The mechanics vary by region, the checkout flow is less familiar to users, and the savings are often smaller than the headline suggests once processing and support costs are counted. A related piece on this site, App Store Review Delays Reshape Indie Studio Runway Math, covers how the review timeline interacts with the same budget pressure.

What this does to a studio

Pricing has to absorb the cut, which pushes list prices higher than the underlying cost of the software would suggest. A tool that costs two dollars a month to run might need to sell for five to clear a meaningful margin after the platform's share, payment processing, and refunds.

Founders who set prices by intuition rather than by net revenue math tend to discover the error a quarter later, when the bank balance does not match the growth chart.

Runway math also changes per platform. A studio shipping on both iOS and Android carries two review processes, two sets of store assets, and two release calendars. The commission is similar on both sides, but the operational overhead is not, and the overhead lands before any revenue arrives. Cross-platform frameworks reduce duplication, but they add a layer of abstraction that occasionally costs a week of debugging when a native API changes.

Margin lives in retention, not in the first sale. A subscription that survives twelve months generates far more net revenue than a one-time purchase at the same price, partly because the reduced commission tier for long-running subscriptions kicks in on some platforms. That makes onboarding, support, and update cadence into financial decisions rather than purely product ones.

Hiring reflects the same pressure. A studio that expects to net 70 percent of gross has less room for a senior engineer than one that nets 85 percent, and the difference shows up in how teams staff QA, support, and localization. A single localization contractor might cost more per month than the incremental net revenue from a small market, which is why many studios delay expansion until retention in the home market is proven.

The tools that shift the math

Cross-platform frameworks such as Flutter and React Native cut the cost of shipping the same feature twice. A single codebase can target both stores, which reduces the engineering hours per platform and shortens the path from idea to release. Heavy graphics work, background services, and platform-specific integrations still need native code, and the framework's plugin ecosystem is not always current with the latest OS release.

Build pipelines matter more than they look. Continuous integration that produces signed builds, runs automated tests, and uploads to both stores removes a recurring manual cost that quietly consumes senior developer time. A studio that automates its release process can ship more often, and more frequent releases tend to improve retention because fixes reach users before they churn.

Subscription billing changes the cadence of revenue, which changes how a studio plans. Recurring revenue is more predictable than one-time purchases, and predictable revenue supports longer hiring and product cycles. Analytics closes the loop by showing which cohorts retain and which acquisition channels bring users who stay. Without that data, a studio spends on installs that never convert to net revenue.

The trade-off in tooling is real. A framework that saves three weeks of engineering can cost a week of debugging when a platform SDK changes, and the net gain depends on how often the studio ships and how much of the app relies on native APIs. Teams that measure the cost per release rather than the cost per feature tend to pick the right abstraction level.

Working inside the platform constraint

Store rules are part of the specification, not an afterthought. Review guidelines cover payment flows, data collection, account deletion, and content standards, and a build that violates them does not ship regardless of how good the product is. Experienced teams read the guidelines before writing the feature, because retrofitting compliance after a rejection costs more than designing for it upfront.

Release cadence is externally gated. A studio can finish a build on Monday and still wait days for review, and the wait is not predictable across submissions. That uncertainty makes launch dates softer than they look in a planning document, and it makes hotfix procedures a real operational concern. Teams that treat review time as a fixed cost in the schedule handle it better than teams that treat it as a surprise.

Platform shifts reset the plan. A new OS version, a changed privacy requirement, or a revised commission structure can invalidate assumptions that a roadmap was built on. A studio that plans for these resets by building modular features and keeping a web fallback can absorb the change without restarting the roadmap. The stores put software in front of billions of devices, and that reach is hard to replicate.

Practical moves for the next cycle

Model fees at the gross level before setting a price. Run the numbers at both 15 and 30 percent, then check whether the product still clears its costs at the lower end. If it only works at 15 percent, the business depends on a tier the studio may not keep.

Prototype on one platform first. Shipping a single-store build proves the product and the payment flow before the team spends months on parity work. Add the second platform once retention data justifies the duplication.

• Track net revenue per install, not gross, so acquisition spend reflects what actually arrives.
• Keep a web fallback path for onboarding and account management, even if payments stay in the store.
• Review the commission structure each planning cycle, since tiers and regional rules change.