On October 23, 2026, an international alliance of 71 civil society organizations and open-source software foundations launched the Keep Android Open initiative, initiating a countdown campaign against Google's planned structural lockdown of the Android ecosystem. Signatories including the Electronic Frontier Foundation (EFF), the Free Software Foundation (FSF), The Tor Project, Proton AG, Brave Software, LineageOS, and Nextcloud published an open letter warning that a looming 2027 policy will permanently dismantle the open sideloading architecture that has differentiated Android from Apple's iOS for nearly two decades.
The controversy centers on a policy originally announced by Google in August 2025 that enters strict enforcement in early 2027. Under the framework, Google will automatically block any application from installing on an Android device unless the developer has centrally registered with Google's Developer Console, submitted government-issued identification, paid registration fees, and provided cryptographic proof of application signing keys. Crucially, the requirement applies not merely to software distributed through the Google Play Store, but to all APK packages worldwide, including hobbyist utilities, community health tools, and open-source applications hosted on alternative platforms like F-Droid.
While Google has defended the measure as an essential security barrier against mobile malware, digital rights advocates argue the rationale collapses under technical scrutiny. Google Play Protect already scans application binaries for known malicious signatures without requiring personal developer deanonymization. Instead, civil liberties advocates contend that mandatory identity collection creates an unprecedented apparatus for international censorship. Because Google regularly complies with local administrative directives to remove apps in authoritarian jurisdictions, forcing developers to surrender legal identities eliminates the ability of dissidents, whistleblowers, and independent journalists to distribute privacy software anonymously.
The coalition also condemned Google's designated 'power user' escape hatch, characterizing it as a deliberate dark pattern designed to suppress alternative software distribution. Bypassing the central block requires users to navigate deeply into system settings, tap build numbers seven times to unlock Developer Mode, acknowledge multiple coercive warning modals, input device credentials, reboot, and endure a mandatory 24-hour cooling-off period before manually confirming installation. Because this enforcement mechanism runs inside proprietary Google Play Services rather than the open-source Android Open Source Project (AOSP) code, Google retains unilateral power to tighten or extinguish the workaround without operating system updates.