Rogue devs of sideloaded Android apps beg for freedom from Google’s verification regime

Summary

Thirty-seven organisations — including the Electronic Frontier Foundation, Free Software Foundation, F‑Droid, Fastmail, Vivaldi and Article 19 — have signed an open letter urging Google to abandon a plan that will force developers who distribute apps outside Google Play to register with the company and pass identity checks.

The verification proposal, previewed since November 2025, requires apps installed on certified Android devices to be tied to a verified developer account. Developers face identity checks and a one‑time $25 fee for standard distribution accounts. The scheme opens for all developers in March 2026 and will expand in September to countries including Brazil, Indonesia, Singapore and Thailand, with unverified apps blocked from installation on certified devices.

Signatories say the move extends Google’s gatekeeping beyond Play, risks privacy and surveillance, raises barriers for small developers, researchers and academics, and threatens innovation, competition and user freedom. The letter calls for less restrictive alternatives and collaboration with open‑source and security communities. Google had not responded to the request for comment at the time of reporting.

Key Points

Google plans to require verified developer accounts for apps installed on certified Android devices, including sideloaded apps outside Play.
Verification includes identity checks and a one‑time $25 fee for standard distribution accounts.
The scheme has been in preview since Nov 2025, opens in March 2026, and expands to additional countries in September 2026.
37 organisations published an open letter arguing the policy undermines Android’s open nature and imposes undue barriers.
The requirement does not change verification for Google Play (already verified since 2023) nor alternative AOSP builds like LineageOS or GrapheneOS.
Critics warn of privacy, surveillance, antitrust and innovation risks if Google extends its review and control to other distribution channels.
Advocates call for working with open‑source and security communities to find less restrictive security measures.

Context and Relevance

This is a pivotal policy debate about who controls app distribution on Android. Historically Android allowed multiple app stores and sideloading; Google’s plan would centralise accountability by tying installs on certified devices to verified developer IDs. That shifts Android closer to a closed model and could affect alternative stores, small developers, researchers, and privacy‑conscious users.

The dispute also touches wider themes: platform competition, regulatory scrutiny of big tech gatekeeping, and how to balance user safety against openness and developer freedom. If you follow mobile ecosystems, digital rights or platform regulation, this development is worth tracking — it could prompt legal challenges, policymaker interest or changes to device certification rules.

Author style

Punchy: this isn’t just another policy tweak — it could fundamentally reshape how Android remains open. The signatories’ broad coalition underlines the scale of pushback; read the detail if you care about sideloading, alternative stores or developer choice.

Why should I read this?

Short version: if you build, distribute, or use apps outside Google Play (or you care about open Android), this affects you. The change could force ID checks, fees and Google oversight even when developers avoid Play. The letter bundles privacy, competition and developer‑freedom arguments — worth a quick skim so you know what to expect and whether to join the conversation.

Source

Source: https://www.theregister.com/2026/02/24/google_android_developer_verification_plan/