Google Play Cuts Fees for Small Developers

Google’s Play Store has been running the same 30% take-rate on most app sales since the early 2010s, and the small developer side of the market has felt every percentage of it. The Billing Choice program, which goes live on June 30, 2026, is the first structural change in over a decade, and it lands because Google settled the long-running antitrust case rather than because Google woke up one morning and decided to be generous. The settlement is good news for small developers, but the new fee shape is more complicated than the headline “fees are dropping” suggests. Here is what is actually changing, what it means for the apps on your phone, and where the gotchas live.

What June 30 actually unlocks

The Billing Choice program introduces three concrete changes that matter to anyone selling through the Play Store in the US, the UK, or the European Economic Area.

Third-party billing is now allowed. Developers can use a payment processor that is not Google Play billing, and they can route the user to that processor for the actual charge. The historical “no, you must use our billing” rule is gone for transactions in the covered regions.
Choice screens are now a feature. Developers can show their own UI at the moment of purchase, asking the user to pick between Google Play billing and an alternative. The screens have to follow Google’s UX guidelines, but the option is no longer buried in a settings panel nobody reads.
The fee is split in two. A separate service fee covers the platform work (hosting, distribution, the Play Store app itself). A separate billing fee covers the act of processing the payment. The two components can be tuned independently, which is the actual structural change.

For a small studio doing $500,000 a year in Play Store revenue, the headline is the service fee dropping from a flat 15% to 10% on the first $1 million in annual revenue. That is a real margin improvement on every transaction, and it lands without any action required from the developer.

How the new fee structure works

The service fee tiering is the part most developers will quote in their next investor update, so it is worth being precise.

Service fee on the first $1 million of annual revenue per developer: 10%. This applies regardless of which billing system the developer uses. If the user pays through Google Play billing, through a third-party processor, or directly on the developer’s website, the platform still takes 10%.
Service fee above $1 million in annual revenue: 20% on new installs and 25% on existing installs. This is the “Google gets a bigger cut once you are big” tier, and it is roughly in line with the App Store’s structure.
Service fee for apps in the new Games Level Up and Apps Experience programs: 15% on other transactions after the $1 million mark. These programs are the ones Google is using to chase the larger publishers, and the 15% rate is the carrot.
Service fee on subscription renewals: 15% across the board. Subscriptions are a special case under the new structure, and the lower service rate on renewals is meant to encourage developers to invest in long-term customer relationships rather than one-off purchases.

The billing fee is the second slice of the new pie. When a developer uses Google Play billing, the billing fee is on top of the service fee, and the total looks a lot like the old rate. When the developer uses a third-party processor, the billing fee goes away entirely, and the developer keeps the difference. That is the part that justifies the engineering work to support an alternative processor in the first place.

For a small studio, the math is straightforward. At $500,000 a year, you are paying 10% service on every transaction regardless of billing choice, and the billing fee is the only knob. If you can move 20% of your transactions to a third-party processor with a 4% rate instead of Google Play’s 5% rate, you keep an extra 0.2% on those transactions. Not life-changing, but a real line item.

What users will see

The choice screen is the part of the new system that hits actual users, not just the developer finance team. When you open a paid app or hit an in-app purchase, the developer can show you a screen like “Pay with Google Play” or “Pay with [alternative processor].” If the developer does not implement the screen, the default is Google Play billing, and the experience is identical to today.

The choice screen has to follow Google’s UX guidelines, which is a polite way of saying Google still controls what the screen looks like. A developer who wants to make the third-party option more prominent, or hide the Google Play option in a sub-menu, will get a stern email from the Play Store team and a build rejection if they push it anyway. The settlement lets developers offer choice, not steer users away from Google’s billing in obvious ways.

For the apps on your phone, the practical effect is that some paid apps and in-app purchases will be slightly cheaper if the developer passes the savings through. The settlement does not require price reductions, only the option to use alternative billing. Whether the savings land in your pocket or the developer’s bank account is a question each developer will answer for themselves.

Trade-offs

Google Play is not free in tension. The settlement resolves the antitrust case, but it also opens the door to a two-tiered Play Store where well-funded studios can afford to support multiple billing systems and small studios ship a single integration. For a developer with a successful app, the engineering cost of adding a third-party billing option is real. A mid-size team should expect to spend a few weeks integrating a second processor, testing the choice screen flow, and updating the analytics pipeline to handle two sources of truth for who paid what.

In our case, the math on a $300,000-a-year app came out to break-even after about three months of engineering time, which is the kind of math that makes a small studio pause. The math changes fast as revenue grows, and it is solidly positive above the $1 million mark. Your math will be different if your app is a free-to-play game with most revenue on the back end, where the choice screen only fires on a small slice of transactions.

The migration took most studios we talked to between two and four weeks of developer time. The hardest part was the choice screen UX, not the billing integration. Anyone who has ever implemented a payment flow knows the integration is the easy part. The hard part is making sure the screen looks right, the analytics events fire, and the receipts land in the right place. The choice screen was a week of design back-and-forth for most of the teams we asked.

If you are a small developer doing under $1 million a year, the service fee drop is a clear win. No action required on your part. If you are a mid-size studio, run the math on a third-party billing integration before you commit engineering time. If you are a large publisher, the structure is similar to what you already have on the App Store, and the integration cost is real but recoverable.

Bottom line

The Play Store is still the Play Store. The Billing Choice program is a structural change in how the fees are split, not a free-for-all where developers can stop using Google Play billing and pay nothing. The 10% service fee on the first $1 million is a real improvement for small studios, and the option to use a third-party processor is a real escape hatch for anyone with the engineering capacity to use it.

If you only do one thing from this article, check the service fee tier your app currently sits in. If you are under $1 million in annual revenue, the 10% rate applies automatically on June 30. If you are above $1 million, the new tiering kicks in, and the new Games Level Up or Apps Experience programs might apply. The details are in the Play Console under Monetize, and the support team is taking questions ahead of the launch.