On 24 February 2026 F-Droid published "An Open Letter Opposing Android Developer Verification" and signed the accompanying coalition letter at keepandroidopen.org. It is the project's clearest statement so far about Google's developer verification programme, and it is worth reading on its own terms rather than through headlines. This post summarises the position F-Droid put forward that day. It is a summary of published sources, not a statement by F-Droid.
What F-Droid argued in February 2026
F-Droid's post frames Google's programme as a change to how apps are installed on Android: developers would have to register centrally with Google before their software can be installed or launched on certified devices, no matter which channel distributes it. Their point is that this reaches far beyond Google Play — commercial rival stores, community repositories like F-Droid, and plain direct downloads from a web page are all in scope.
Against that, F-Droid makes several arguments:
- It treats the programme as an existential threat to the community repository model. Under it, maintainers would accept Google's terms, pay a fee, upload government-issued identification, and register every application they distribute.
- It rejects the "advanced flow" that Google floated in November 2025 as vague and undemonstrated. In February F-Droid said it had learned the advanced flow would not exist before the September deadline, and argued it should be disregarded until the community could test and vet it. (That was a February claim — the dated update posts below record what has become checkable since.)
- It advises developers not to enrol in the programme at all: "We unequivocally advise against signing up for this program, now or ever." F-Droid's argument is that the lock-down only works through developer complicity, so it asks developers to become advocates — write about it, post about it, and contact regional regulators.
- It points to existing defences — OS sandboxing and permissions, install-time warnings, Play Protect, and app signing certificates — and argues no evidence has been shown that these are insufficient.
The coalition letter F-Droid signed (addressed to Google's CEO, founders, and head of App & Ecosystem Trust, dated the same day) expands the argument: gatekeeping beyond Google's own store; barriers for individual developers, volunteer open-source projects, regions with limited access to Google's infrastructure, humanitarian and activist software, and researchers; privacy risks of a central database of all Android developers; arbitrary enforcement and account-termination risk; anticompetitive information advantages for Google; and regulatory concerns. The letter's registration checklist — a fee, Google's terms, government-issued ID, evidence of the app's private signing key, and a list of all app identifiers — is what "just paperwork" would mean in practice. Dozens of organisations have signed it, among them the EFF, FS Europe, and the Software Freedom Conservancy (the coalition's site listed 71 signatories from 23 countries when checked on 2 October 2026).
Why this matters for F-Droid users and developers
- The repository model itself is at stake. F-Droid builds thousands of apps from source and distributes them as a community project; F-Droid's reading is that every one of those apps would need a Google-registered developer behind it, whoever publishes it.
- Signing keys. Registration requires signing-key evidence. For an F-Droid-signed build it is genuinely unclear whose identity gets registered — the upstream developer, F-Droid, or nobody. We found no official answer to that question in Google's published materials.
- Anonymity. Government ID and a contractual relationship with Google is the default path under the programme as F-Droid describes it. For pseudonymous maintainers and users in hostile environments that is a structural change, not paperwork.
- F-Droid's advice in the letter is public and direct: do not enrol in the programme; speak up through projects, articles and regional regulators. The project argues that developer participation would make the restrictions effective.
Questions for this thread
1. If you maintain or ship an app: does F-Droid's "do not sign up" advice hold for your case, or do you see a reason to register before the programme reaches your devices?
2. For F-Droid-signed builds, who should register — F-Droid, the upstream developer, or nobody? Has anyone seen an official answer?
3. The coalition letter argues existing defences (sandboxing, install warnings, Play Protect, signing certificates) are sufficient. Do you agree — is there a real security gap that only developer identity can close?
4. At the time of the letter, what would have made the proposed advanced flow workable for you? Is any opt-in friction already the wrong default for a device you own?
5. What should a project like ours document or prepare while the requirements are still moving?
Primary sources
- F-Droid, "An Open Letter Opposing Android Developer Verification", 24 Feb 2026: https://f-droid.org/en/2026/02/24/open-letter-opposing-developer-verification.html
- Keep Android Open coalition letter, 24 Feb 2026: https://keepandroidopen.org/open-letter (campaign site: https://keepandroidopen.org/)
- Earlier F-Droid posts: "F-Droid and Google's Developer Registration Decree", 29 Sep 2025: https://f-droid.org/en/2025/09/29/google-developer-registration-decree.html and "What We Talk About When We Talk About Sideloading", 28 Oct 2025: https://f-droid.org/en/2025/10/28/sideloading.html
Related threads here: /t/67/ (Google's rollout, what actually changes) and /t/68/ (GrapheneOS).
Написать Join — чтобы участвовать в обсуждении.