Google has updated its Google Play billing policies for Android app developers, with all new rules taking effect on June 30, 2026. The policies set a 10% service fee for the first $1 million in annual developer revenue, and introduce official support for third-party payment processing for users in the United Kingdom, European Economic Area, and United States per the official Android Developers Blog announcement.
The policy separates Google Play’s platform service fee from payment processing costs for the first time. Developers using eligible third-party billing systems or directing users to external purchase pages can access this split fee structure. All eligible developers in the three initial launch markets can enroll in the alternative billing program immediately, ahead of the June 30 effective date per Google’s published billing policy update.
Google Play 2026 Android Billing Structure Takes Effect June 30
Google first shared details of the policy shift in a March 2026 post on the official Android Developers Blog view the original policy roadmap announcement. The rollout follows a phased global structure, with the US, EEA, and UK as the first supported markets, and additional regions to be announced in later phases per Google’s published roadmap.
Developers serving users in these regions can offer alternative billing systems, link to external purchase pages, or build custom choice screens that meet Google’s published UX guidelines, alongside the default Google Play billing option per the expanded billing choice guidance. The 10% service fee applies to all transaction types, including auto-renewing subscriptions, for the first $1 million in annual developer earnings, regardless of which billing method a developer selects confirmed in Google’s fee structure documentation.
Official Google Play billing interface and fee breakdown for the 2026 policy update
Eligible Third-Party Billing Markets and Developer Enrollment Rules
The initial launch markets for third-party billing support are limited to the United States, United Kingdom, and European Economic Area, per Google’s published rollout roadmap (https://android-developers.googleblog.com/feeds/posts/default). Google has stated that additional regions will be added in later rollout phases, though no specific timeline or list of upcoming markets has been shared publicly. All eligible developers operating in these three markets can enroll in the alternative billing program immediately, with no waiting period required before the June 30, 2026 policy effective date (https://android-developers.googleblog.com/feeds/posts/default).
GrapheneOS Stable Android 17 Build Launches With Critical Security Patches
The privacy-focused open-source Android distribution GrapheneOS released stable build 2026062300 on June 23, 2026, marking its first public stable release built on Android 17 per the official GrapheneOS release notes. The build supports all current Google Pixel devices from the Pixel 6 through the Pixel 10a, specifically including the Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9 series, and Pixel 10a, plus emulator and generic hardware targets. This release covers every consumer Pixel model launched between 2021 and 2026, ensuring compatibility for the vast majority of active GrapheneOS users.
The release includes all security patches from the July through December 2026 Android Security Bulletins per GrapheneOS’s security patch disclosure. Key fixes resolve a critical upstream Android VPN race condition that could disable always-on VPNs during edge cases including VPN app updates, a bug that impacted both GrapheneOS and stock Pixel OS on Android 16 QPR3 and Android 17 confirmed in the build 2026062300 changelog. The update also fixes broken Bluetooth auto-off functionality on secondary user profiles in Android 17, and patches Sandboxed Google Play compatibility issues that disrupted RCS messaging following DroidGuard updates (https://grapheneos.org/releases).
For users upgrading from a pre-Android 17 GrapheneOS build, the release notes mandate using the standard over-the-air update system rather than ADB sideload to avoid triggering the upstream VPN bug per official upgrade guidance. A special Android 16 QPR2 build with a backported fix will be released separately for users who exclusively sideload updates. While stock Pixel OS avoids the VPN bug via a bloatware-triggered fallback path, GrapheneOS opted to patch the root cause of the issue rather than implement a temporary workaround, consistent with the project’s core mission of eliminating unpatched vulnerabilities stated in the release notes.
Frequently Asked Questions About 2026 Google Play Billing and GrapheneOS Updates
When does Google Play’s 2026 billing policy take effect?
All new billing rules, including the 10% service fee and third-party billing support, take effect on June 30, 2026, per Google’s official Android Developers Blog announcement (https://android-developers.googleblog.com/feeds/posts/default).
Which developers are eligible for the 10% service fee on the first $1 million in earnings?
All developers operating in the US, UK, and EEA are eligible for the 10% service fee on the first $1 million in annual earnings, regardless of whether they use Google Play Billing or an eligible third-party payment system (https://android-developers.googleblog.com/feeds/posts/default).
Which Pixel devices support the GrapheneOS Android 17 stable build?
The GrapheneOS stable build 2026062300 supports all Google Pixel devices from the Pixel 6 through the Pixel 10a, including all Pro, a, and series variants in that range, plus emulator and generic hardware targets (https://grapheneos.org/releases).
Why does GrapheneOS require OTA updates instead of ADB sideload for the Android 17 build?
GrapheneOS requires OTA updates for the Android 17 build to avoid triggering a critical upstream Android VPN race condition that disables always-on VPNs during edge cases like VPN app updates, a bug that affects ADB sideload installations (https://grapheneos.org/releases).
Bottom line: Android developers operating in the UK, EEA, and US should enroll in Google Play’s alternative billing program immediately to qualify for the 10% service fee on the first $1 million in annual revenue ahead of the June 30, 2026 effective date. All GrapheneOS users with supported Pixel 6 through Pixel 10a devices should install the over-the-air update for build 2026062300 to resolve critical security vulnerabilities, fix VPN and Bluetooth functionality bugs, and restore RCS messaging compatibility with Sandboxed Google Play.
