For over a decade, the defining difference between Android and iOS has been openness. While Apple maintained a walled garden, Android users enjoyed the freedom to sideload apps, use third-party stores like F-Droid, and develop software without asking for corporate permission.
That era is scheduled to end in September 2026.
Despite a widely circulated narrative that Google had softened its stance, a coalition of nearly 50 organizations, including digital rights groups, open-source projects, and industry advocates, has published an open letter to Google. Their message is clear: the proposed Android Developer Verification program isn’t a security update; it’s a kill switch for the open ecosystem.
The identity crisis of Android development
Under the new mandate, anyone who wants to distribute an Android app, even those who have no intention of using the Google Play Store, must centrally register with Google. This isn’t just a simple sign-up; it requires:
- A registration fee paid directly to Google.
- Government-issued identification to verify the developer’s identity.
- Submission of private signing keys and a comprehensive list of all current and future application identifiers.
Currently, if you want to share an app you built with a friend or host a niche tool on GitHub, you can simply share the APK file. By late 2026, certified Android devices (which account for the vast majority of the market) will reportedly block the installation of any app from a non-registered developer.
The advanced flow is a myth (for now)
In late 2025, a wave of relief hit the tech community when reports suggested Google was backing down. The company mentioned a potential “advanced flow” that would allow “experienced users” to bypass these restrictions and accept the risks of unverified software.
While security is crucial, we’ve also heard from developers and power users who have a higher risk tolerance and want the ability to download unverified apps. Based on this feedback and our ongoing conversations with the community, we are building a new advanced flow that allows experienced users to accept the risks of installing software that isn't verified. We are designing this flow specifically to resist coercion, ensuring that users aren't tricked into bypassing these safety checks while under pressure from a scammer. It will also include clear warnings to ensure users fully understand the risks involved, but ultimately, it puts the choice in their hands. We are gathering early feedback on the design of this feature now and will share more details in the coming months.
However, the coalition led by Keep Android Open warns that this was a tactical distraction. According to internal findings from the F-Droid team, no such bypass mechanism is currently in development, and no feedback has been sought from outside stakeholders.
As it stands, the official documentation still points toward a total lockdown. Until Google provides concrete evidence of a frictionless bypass, the community is operating under the reality that sideloading as we know it is dying.
Why the resistance is growing
The opposition isn’t just about the inconvenience of a few extra clicks. The open letter outlines several existential threats to the mobile landscape:
- The death of F-Droid: Alternative stores like F-Droid thrive because they don’t track developers or users. Forcing these developers to hand over government ID to Google violates the core principles of the open-source community.
- Censorship chokepoints: By tying every single app to a verified identity, Google creates a centralized database that authoritarian regimes can exploit. If a government wants to suppress a specific communication tool, they no longer need to hunt for it; they just need to pressure Google to revoke the developer’s verification.
- Market stagnation: If Android becomes a carbon copy of the iOS walled garden, there is less incentive for Apple to open up, and less competition to keep Google’s fees and policies in check.
What happens next?
The coalition is calling on developers to refuse to participate in the verification program and is urging users to contact regulators. In regions like the EU, the Digital Markets Act (DMA) was designed to prevent exactly this kind of gatekeeping, and the group hopes to trigger similar scrutiny globally.
For Kenyan developers who have long relied on Android’s low barrier to entry to innovate without high overhead costs, this change could be particularly stifling. If you are a developer or a concerned user, you can view the full list of demands and sign the petition at KeepAndroidOpen.org.
