The short version
In September 2026, Google starts enforcing a new rule in Brazil, Indonesia, Singapore, and Thailand: every app installed on a certified Android device, including sideloaded apps, must be tied to a developer who has verified their identity with Google. Government ID, $25 one-time fee, and registered package names. Global rollout follows in 2027. This is the biggest change to Android distribution in years and it reaches well beyond the Play Store. Here’s what’s actually happening, who’s affected, and why F-Droid is calling it an “existential threat” to open-source Android.
What is actually changing
Until now, Android has worked roughly like this: anyone could write an app, sign it with their own key, and distribute it however they wanted. You could put an APK on a website, share it on Telegram, host it on F-Droid, or list it on alternative stores like Aptoide. If a user trusted the source, they could install it.
That’s changing.
Starting in September 2026, certified Android devices in the first four pilot countries will only install apps from developers who have completed Google’s new verification process. To distribute apps to those devices, a developer needs to:
- Create an account in the Android Developer Console (separate from the Play Console)
- Verify their legal identity with a government-issued ID
- Pay a one-time $25 registration fee
- Register the package names of the apps they ship
The mandate covers Android Certified devices, which is roughly 95% of Android devices outside China. It applies whether the app is distributed through the Play Store, through an alternative app store, or as a direct APK download from a website. The only exceptions are devices running pre-2026 Android versions (which won’t be updated to enforce this) and devices outside Google’s certification program.
If you’ve heard about identity verification for Play Console accounts already, this is different. That existing verification covers Play Store distribution only. The new mandate covers distribution anywhere on a certified device.
The timeline you actually need to know
- March 2026: Developer registration opens
- August 2026: “Advanced flow” launches for sideloading unverified apps (more on this below)
- September 2026: Enforcement begins in Brazil, Indonesia, Singapore, and Thailand
- 2027 and beyond: Global rollout continues
If you’re reading this in mid-2026, you have a few months before the first enforcement starts. If you ship apps in any of the pilot countries, the clock is real.
A concrete example: what happens to NewPipe
If you’ve never used it, NewPipe is one of the most popular sideloaded Android apps in the world. It’s an open-source YouTube client that strips ads, lets you play videos in the background, downloads audio, and works without a Google account. It’s distributed only through F-Droid and direct APK downloads. It’s not on the Play Store because Google’s policies don’t allow apps that modify YouTube’s playback experience.
Millions of users install NewPipe because it solves a real problem. The developers maintain it as a community project, often pseudonymously.
Here’s what verification means for an app like NewPipe in the pilot countries from September 2026 onward:
- The developer behind NewPipe would need to register with Google, hand over a government ID, and pay the $25 fee
- The NewPipe package name would need to be registered in Google’s central directory
- If the developer doesn’t comply, NewPipe installations on certified Android devices in those countries would be blocked
NewPipe’s developers have already publicly said they won’t comply with Google’s verification rules. The app has started showing in-app warnings to users about the upcoming restrictions and is informing them about alternative installation paths.
The same applies to dozens of other popular open-source apps: Aurora Store (a Play Store client that doesn’t require a Google account), Tubular (a NewPipe fork), Fennec (a tracker-free Firefox), various game emulators, modding tools, and ad-blocking utilities. Most are maintained by people who either won’t register, can’t register (pseudonymous contributors), or fundamentally object to a central registry as a condition for distributing free software.
The F-Droid problem
F-Droid is the largest open-source Android app repository in the world. For over a decade, it has hosted thousands of apps under a simple model: developers submit source code, F-Droid builds the app from source, signs it with F-Droid’s own signing key, and distributes it. There are no user accounts. Many contributing developers are pseudonymous. The whole point is that anyone can audit the build, anyone can install it, and no central authority controls the catalog.
Google’s verification mandate breaks F-Droid in two ways:
Problem 1: The signature problem. Under Google’s rules, an app’s package name has to be tied to one verified developer identity. But on F-Droid, apps are signed with F-Droid’s key, not the original developer’s key. That means the same app distributed through F-Droid and through Google Play would have two different signatures, which Google’s system treats as two different ownership claims for one package name. F-Droid’s model literally can’t comply without abandoning either the central F-Droid signature or the original developer.
Problem 2: The identity problem. F-Droid hosts apps from developers who are pseudonymous on principle, including security researchers, dissidents, and contributors from countries where being publicly identified as the author of certain apps (privacy tools, communication apps, VPNs) is dangerous. F-Droid can’t force these developers through Google’s identity verification. It can’t even accurately count how many would be affected because it doesn’t have user accounts to begin with.
F-Droid board member Marc Prud’hommeaux has publicly said that Google’s policy will “kill F-Droid” and called it an “existential threat” to the project. F-Droid estimates that 90 to 95 percent of independent Android developers oppose the policy. The organization has joined with EFF, the Software Freedom Conservancy, and the Free Software Foundation in a coalition opposing the rollout.
Sister projects face the same problem. GrapheneOS and CalyxOS, the privacy-focused alternative Android distributions, rely heavily on the F-Droid model and the broader open-source app ecosystem. If F-Droid’s catalog shrinks dramatically, those custom ROMs become significantly less useful.
The “Advanced Flow” for power users
Google’s response to the backlash is what it calls the advanced flow. The idea: even on a certified Android device in a pilot country, a determined power user can still install an unverified app, but only after going through extra steps.
Specifically, the advanced flow requires:
- The user actively enables the option through Android settings or a debugging tool (ADB)
- An authentication step to confirm the user is doing this on their own
- A one-time, 24-hour waiting period before the unverified install can proceed
Google’s argument is that this protects normal users from social-engineering scams (a fake support agent walking someone through a one-tap malware install) while leaving the door open for users who genuinely want to install unverified software.
Critics call this a fig leaf. A 24-hour waiting period to install a single APK is, in practice, a deterrent against any casual use of sideloading. Stores like F-Droid don’t work in a world where each new app or update requires a 24-hour delay. Custom ROM developers point out that the advanced flow is also exactly the kind of mechanism that future security updates could quietly tighten further.
Android: from open ecosystem to closed garden?
Here’s where this stops being just a technical policy and becomes a philosophical question about what Android is.
Android’s selling point for almost two decades has been openness. You can install whatever you want. You can run custom ROMs. You can develop apps without anyone’s permission. The contrast with iOS, where Apple controls every app, was the whole identity of the platform for users and developers who valued that freedom.
The verification mandate doesn’t technically end any of those things. Sideloading still exists. Alternative stores still exist. Custom ROMs still exist.
But the practical reality shifts a lot:
- Distributing an app, anywhere, requires Google’s permission in the form of identity verification
- A central Google-controlled registry decides which package names map to which developers
- Apps from non-compliant developers become harder to install on most devices over time
- The independence of alternative stores becomes conditional on Google’s continued tolerance
In its open letter, F-Droid put it bluntly: “Android, currently an open platform where anyone can develop and distribute applications freely, is to become a locked-down platform, requiring that developers everywhere register centrally with Google in order to be able to distribute their software.”
That’s the heart of the criticism. Even if every individual technical capability is preserved, the trust model has flipped. Before, you could distribute software without asking anyone. Now you have to register with a single private company that competes directly with the alternative stores and developers it’s regulating.
The comparison to Apple’s App Store model is unavoidable. Apple has always required developer identity, payment of a $99 annual fee, and central registration. Apple controls which apps can run on iOS. Google’s new policy moves Android meaningfully in that direction, even if the specifics (one-time $25 fee, sideloading still possible through the advanced flow) are more permissive than Apple’s.
What indie developers should actually do
If you’re an Android developer reading this, here’s the practical takeaway:
If you only distribute through the Play Store: You’re already in Google’s verification system. The new requirements largely don’t add work for you, though you should monitor the rollout in case Google merges or modifies the existing Play Console verification with the new Android Developer Console.
If you distribute outside the Play Store (direct APKs, alternative stores, F-Droid): You need to decide before September 2026 whether to register with Google’s new system or accept that your distribution to certified devices in pilot countries will be restricted. Registration takes time, requires document upload, and requires you to enumerate every package name you ship.
If you maintain an open-source app that contributors help build: Think about who in your project will hold the verified identity. The model where multiple maintainers all sign apps under different keys breaks under the new system.
If you’re a hobbyist or student: Google has said there will be a lighter-touch version of the Developer Console for non-professional developers, with different requirements. Details are still being finalized.
For everyone: Remember that being a verified developer is the right to distribute. It’s separate from getting an app onto Play production, which still requires clearing Google’s closed testing rule (12 testers running the app for 14 consecutive days). These are two different hurdles, often confused.
The bigger picture
The community response to Google’s verification mandate has been substantial. The Keep Android Open campaign has gathered tens of thousands of signatures. An open letter signed by F-Droid, EFF, Software Freedom Conservancy, FSF, and 55 organizations from 19 countries calls for Google to reverse course. A Change.org petition has crossed 64,000 developer signatures, growing fast. Aptoide, an alternative app store, has filed a fresh antitrust lawsuit against Google citing monopoly behavior.
In parallel, regulators are watching. The EU’s Digital Services Act creates obligations around app distribution transparency. Several jurisdictions are tightening rules around app distribution accountability. The verification mandate sits awkwardly in the space between “legitimate security response to regulatory pressure” and “anticompetitive consolidation of control over a formerly open platform.”
How this resolves in 2027 and beyond depends on three things: whether F-Droid finds a workable technical or legal accommodation, whether regulators (especially in the EU) intervene, and whether enough Android users actually care to push back on the policy through their device choices.
What we know for now: the policy is rolling out, the indie developer community is loudly opposed, F-Droid faces real existential pressure, and the open Android ecosystem that has existed since 2008 is undergoing the most significant change in its history.
For Android developers planning their 2026 and 2027 releases, the practical advice is to understand the timeline now, decide on your distribution strategy early, and don’t get caught flat-footed when enforcement starts. Verification is the new entry ticket. Where you go from there, in terms of Play Store production access, alternative stores, or open-source distribution, depends on what kind of developer you want to be.
Whatever you build and however you distribute it, getting through Google Play’s production access requirement still means passing closed testing (12 testers, 14 days). If that’s the hurdle in front of you, Testers Community helps developers complete the 14-day testing requirement quickly. Join 50,000+ developers using the free community app or get 25 verified testers in 6 hours with the $15 paid service.
