google

Google Just Cracked Open the Play Store: What the New Billing Rules Mean for Developers

Google Just Cracked Open the Play Store: What the New Billing Rules Mean for Developers
Image Credit: getty Images

For years, Google's 30% commission on the Play Store was one of the most contentious realities in the app economy. Developers, particularly smaller indie creators, had little choice but to accept it or walk away from the world's largest Android marketplace. That era is now officially over. Starting June 30, 2026, Google is rolling out one of the most sweeping overhauls of its Play Store business model since the platform launched, and the implications ripple far beyond Silicon Valley courtrooms.

What Triggered This?

This change did not happen in a vacuum. It stems from Google's settlement with Epic Games, formally ending an antitrust battle that began when Epic tried to bypass Google's billing system back in 2020. After a years-long legal fight, Google was found to have operated an app store monopoly, forcing real structural changes to how the Play Store runs. The result is a new model that opens the door to competition, lowers fees, and most importantly, gives developers genuine flexibility in how they handle payments.

The Old Model vs. The New One

Previously, Google charged a flat 30% commission on all in-app purchases. Google is replacing this with a new "decoupled" fee system that separates charges for app distribution from payment processing. This is a meaningful shift because the old bundled approach meant you paid for both services whether you wanted them or not.

Here is how the new structure actually breaks down:

Service Fee (charged on all transactions regardless of payment method):

The base service fee is 10% on the first $1 million in annual earnings. Above $1 million, it rises to 20% for new installs and 25% for apps that were installed before the new rules take effect, which are referred to as "existing installs." Auto-renewing subscriptions are an exception and stay at 10% across all revenue levels.

Billing Fee (only charged if you use Google's own payment system):

For developers who use Google Play Billing, an additional billing fee applies. In the US, UK, and European Economic Area, that billing fee is set at 5%. If you use a third-party payment processor, you skip this fee entirely, though your external processor will have its own processing charges.

Special Programs for Lower Rates:

Developers can unlock a reduced 15% service fee by joining the Apps Experience Program or the updated Google Play Games Level Up program, which reward apps that meet certain quality benchmarks around performance and user experience. These programs go live in September 2026.

What Does This Mean in Practical Terms?

Let's put the numbers in perspective. For smaller developers, the 10% rate is genuinely good news. An indie app earning $500,000 a year was previously handing Google $150,000. Under the new structure, that bill drops to $50,000, which is a $100,000 swing that changes the economics of building and maintaining apps on Android entirely.

For subscription-based apps, the math is similarly encouraging. The financial implications are most immediate for subscription-based apps, which now face a 10% commission rather than the previous 30%. Developers who adopt alternative billing can further reduce their platform costs, potentially passing savings to users through lower subscription prices or fewer in-app price increases.

However, the savings are not uniform for everyone. The developer profile that benefits most is specific: high-revenue, subscription-driven, with an existing payments relationship and the engineering capacity to integrate a parallel billing path. Larger apps with established user bases installed before June 30 face the 25% tier for in-app purchases above $1 million in annual earnings, which is less dramatic than the headline figures suggest.

Developers Can Now Use External Payment Gateways

Perhaps the most meaningful change is not the fee reduction itself, but the freedom to route payments entirely outside Google's system. Developers can now offer their own billing system alongside Google Play Billing within their app, or direct users to their website to complete purchases. Previously, this kind of setup would get your app pulled. Now it is an official, supported option.

This matters deeply for African developers and startups in markets like Kenya, where local payment solutions such as M-Pesa are more relevant to users than a credit card-based Google checkout flow. The ability to offer locally preferred payment options within your app without fear of being delisted is a real, practical win for the continent's growing app economy.

That said, there are trade-offs. Developers who use their own billing system still owe Google a reduced service fee. They also take on the complexity of managing payments, refunds, fraud, tax compliance, and subscription lifecycle themselves, which are things Google Play Billing handles out of the box.

When Does This Reach Kenya and Africa?

This is where Kenyan and African developers need to manage expectations. The new fees and alternative billing options go live on June 30 in the US, UK, and European Economic Area. Australia, Japan, and South Korea follow by end of 2026, with the rest of the world adopting the rules by September 2027.

That means Kenya, along with most of Africa and the Global South, will not see these changes until late 2027 at the earliest. For now, local developers remain under the existing fee structure. It is still worth understanding these changes today, both to plan ahead and because they signal a broader shift in how platform gatekeepers are being held accountable globally.

A New Era for Third-Party App Stores Too

Beyond billing, Google is launching a "Registered App Stores" program that gives alternative Android storefronts an easier, officially sanctioned path to operating on Android devices. Previously, installing apps from outside the Play Store required users to navigate security warnings and manual settings changes, a friction that effectively disadvantaged rival stores. This could eventually open the door for regional African app stores to operate with far less resistance.

The Bigger Picture: Apple Is Watching

Apple and Google have long operated in near-perfect parallel on fees. Both historically charged 30%, both reduced to 15% for developers earning under $1 million annually, and both fought against any external mandate to allow alternative billing. That symmetry is now breaking down. Apple is still fighting Epic in the courts and appealing to the US Supreme Court, while Google has moved decisively to set a new global benchmark. How Apple responds to this competitive and regulatory pressure is one of the most important stories in tech to watch over the next two years.

What Should Developers Do Now?

If you are building on Android, this is a good time to review your payment architecture and understand where your users fall in the new install classification system. The smart move right now is to start auditing your install base data, understanding what proportion of your active users will be classified as "existing installs" versus "new installs" after June 30, and modeling out the fee impact across both Google Play billing and external billing scenarios.

For Kenyan developers specifically, the September 2027 global rollout gives you time to prepare rather than scramble. Start thinking now about whether integrating a local payment gateway alongside Google Pay makes sense for your user base, and watch how developers in the US and EU navigate the transition over the next 12 months. The mobile commerce landscape is shifting, and this time, developers have more cards in their hands than ever before.

Sandra Safari
ABOUT THE AUTHOR

Sandra Safari

Software Staff Writer,Sandra Safari serves a unique dual role at TechInKenya as both a Software Engineer and a Tech Journalist. Operating at the intersection of infrastructure engineering and media, s...see full bio

Comments

to join the discussion.