App Store Fees Shape Which Mobile Skills Get Hired

Store commissions decide mobile engineering budgets before anyone writes a job description. Apple's cut on digital goods reduces net revenue per user, and that number, not the gross figure, sets how many engineers a product can carry. The same arithmetic explains why iOS roles often carry a salary premium, why Android teams tend to run larger, and why cross-platform generalists face rate compression even when their output matches a native specialist's.

The 30 Percent Hiring Tax

Apple's standard commission on app and in-app purchase revenue has hovered around 30 percent for most developers, with a reduced rate for smaller businesses and long-running subscriptions. That slice comes off the top before payroll, cloud bills, or contractor invoices get paid. A product earning a dollar per user per month nets closer to seventy cents on iOS digital goods, and the gap compounds across a user base.

Headcount follows net revenue, not download counts. A team forecasting a million dollars in annual iOS revenue is really planning around roughly seven hundred thousand dollars of usable budget. That difference is a couple of senior salaries. It also explains why iOS-first roles command premiums: the platform that generates more net revenue per paying user can justify paying more for the engineer who protects that revenue.

Android teams often run larger and pay less per seat. The addressable device base is wider, average revenue per user tends to be lower, and the work fragments across more hardware profiles. A team shipping to both stores frequently staffs Android with two or three engineers for every iOS specialist, then wonders why the iOS person has more negotiating leverage at review time. The trade is not one-sided: even at lower per-seat rates, the larger Android group can consume more total budget and open more junior and mid-level headcount. A company that has to cover a long device tail will keep hiring Android engineers long after the iOS roster is full.

Where the Money Actually Goes

Commissions fund platform research and development, developer tooling, and the review infrastructure that keeps stores usable. Developers absorb the rest of the payment stack: processing fees, tax handling, refunds, and the engineering hours spent wiring billing into a product. None of that work appears in a feature roadmap, and all of it shows up in a hiring plan as a specialist role.

Subscription margins favor native iOS work because recurring billing on that platform has matured into a relatively predictable pipeline. A subscription product with strong retention can justify a dedicated billing engineer, a growth analyst, and a lifecycle marketing contractor. The same product on Android may need more support engineering for device fragmentation before it needs another growth hire.

Cross-platform stacks trade reach for rate. A single codebase can ship to both stores faster with a smaller team, which is exactly why agencies and cost-conscious product owners like it. The trade is that the resulting app often leans on the lowest common denominator of platform capability, and the engineer who only knows the shared layer has a thinner story at the next contract negotiation. This site has argued that cross-platform stacks narrow what a mobile engineer can specialize in.

The Skills That Get Funded

In-app purchase integration is non-negotiable for anyone touching a revenue-generating app. StoreKit on Apple's side and Play Billing on Google's side are the two APIs that turn a tap into money, and engineers who have shipped real subscription flows, handled restore purchases, and debugged receipt validation are consistently in demand. The work is unglamorous and hard to fake in an interview.

App store optimization specialists have started appearing in engineering org charts rather than only in marketing. ASO is the practice of improving visibility and conversion inside a store, and it now touches metadata pipelines, screenshot generation, and experiment infrastructure. A mobile engineer who can run a store listing experiment end to end is worth more than one who only ships features.

Privacy compliance skills became billable the moment stores started requiring data disclosure labels and consent flows. Engineers who understand what a tracking SDK actually collects, and can remove or replace one without breaking attribution, are doing work that legal teams cannot do alone. That skill sits at the intersection of platform policy and code, which is precisely where budgets are hardest to cut.

Contracts That Lock In Stacks

Enterprise deals frequently specify platform targets in the statement of work. A retail client asking for an iOS app and an Android app is really asking for two delivery tracks, two review cycles, and two sets of store compliance obligations. The contract language determines whether the vendor can use a shared codebase or must staff native teams, and that single clause can swing a project's margin by double digits.

Agency retainers favor one-store expertise because specialization produces faster estimates and fewer surprises. An agency that only ships iOS apps knows its review timelines, its rejection patterns, and its billing edge cases cold. The same agency bidding on a cross-platform project often pads the estimate to cover unfamiliar risk, which pushes the price up and the win rate down.

White-label contracts cap rate ceilings. When the same app ships under a client's brand with minimal customization, the work becomes repeatable and the client knows it. Repeating a template does not build the kind of expertise that commands a premium, and the engineer assigned to maintenance on those accounts tends to plateau.

Ownership of the store accounts is the real leverage in these arrangements, because whoever controls the listing controls the customer relationship and the renewal conversation.

What an Engineer Trades Away

Narrow platform depth limits job mobility. An engineer who has spent four years exclusively on iOS billing internals is exceptionally valuable to a handful of companies and a question mark to everyone else. The objection is real: deep specialists often earn more than generalists in the same market, right up until the platform changes its rules or the employer changes its stack.

Freelance store fees hit solo developers hardest because there is no team to absorb the commission. An independent developer paying a platform cut, a payment processor, and self-employment taxes keeps a smaller share of each sale than an employee would guess. That arithmetic pushes many solo developers toward service work for other businesses rather than consumer products of their own.

Equity rarely survives platform policy shifts. A startup valued on a commission structure that later changes, or on a distribution channel that later closes, can see its engineering headcount plan rewritten in a quarter. Engineers accepting equity in place of salary should read the platform dependency in the pitch deck as carefully as the revenue projections.

Positioning for the Next Contract

Audit your revenue per platform shipped. Pull the numbers from the last two products you worked on and compare net revenue after store commissions, not gross downloads. That single comparison tells you which platform experience is actually worth leading with on a resume or a rate card.

Learn the billing APIs on both stores, even if you only ship on one. StoreKit and Play Billing share concepts but differ in edge cases, and the engineer who can debug a failed renewal on either platform is harder to replace than one who knows a single stack.

Negotiate store account ownership upfront in any contract where you build the product. Access to the developer account, the analytics, and the customer list is leverage that outlasts the engagement, and it is far easier to secure before signatures than after.

Price cross-platform work at native rates when the deliverable carries native complexity. When a shared codebase is quoted below native rates, clients learn to expect the lower number on every subsequent project.

Track commission changes quarterly. Platform fee structures have moved repeatedly over the past several years, and each adjustment ripples into budgets, headcount, and contract terms within a couple of planning cycles. A related piece on how routing contracts favor the largest buyers covers a comparable dynamic in infrastructure pricing.