The Keep Android Open campaign was urging developers and users to oppose Google's planned verification requirements for Android software distributed outside the Play Store. The campaign framed the policy as a threat to independent apps and alternative stores, and said 71 organizations across 23 countries had signed its open letter.
According to the campaign's account, Google announced in August 2025 that Android developers would eventually need to register before their applications could be installed on devices covered by the program. Keep Android Open says the rollout is due to begin in 2027 and could require identity checks, agreement to terms and, in some cases, payment. The campaign argues that the system would affect not only commercial stores but also hobby projects, community software, internal test builds and apps shared directly between individuals.
These claims come from an advocacy site opposing the policy. The supplied evidence does not include Google's announcement, implementation documentation or response, so the exact scope, schedule and final requirements cannot be independently established from the packet. Claims that every unregistered app would be blocked worldwide should therefore be treated as the campaign's interpretation rather than a settled technical outcome.
The campaign does acknowledge that Google has described a route for "power users" to install software from unverified developers. It objects to the proposed friction, describing a nine-step process and a 24-hour waiting period located behind developer settings. It also says the flow would rely on Google Play Services rather than the open-source Android operating system, giving Google the ability to alter it separately from an operating-system update. The site says that exception had not yet appeared in a beta, preview or canary release at the time of its post.
Keep Android Open's central concern is not merely inconvenience. It argues that mandatory developer identity could deter anonymous open-source participation and expose people distributing sensitive tools, particularly activists, journalists or developers in restrictive jurisdictions. It also contends that existing malware scanning can assess code independently of a developer's identity, challenging verification as the appropriate security control.
Those are policy arguments, not evidence that registration offers no security benefit. A complete assessment would require Google's threat model, enforcement design and final exception process, none of which is included in the supplied material. The campaign's page also uses deliberately forceful language and calls on developers not to enroll.
Even with those limitations, the dispute identifies a real governance question: who decides what software may run on a device after it has been sold? The answer will depend on details still subject to implementation, including which devices are covered, how exceptions work and whether independent distribution remains practical rather than merely possible.
