The new Android developer verification requirement starting in 2026 means that all apps installed on certified Android devices will have to come from verified developers who have undergone identity verification with Google. This move is intended to increase app safety measures by confirming developer identities, not content review.
Regarding F-Droid and its apps, this verification requirement poses significant challenges. F-Droid relies on builds and apps that may not have this Google verification, which could effectively block or limit F-Droid apps from being installed on most Android devices under the new policy. The requirement to register and verify developer identity is seen by many as a potential end or heavy restriction on alternative app stores and sideloaded apps like those from F-Droid, unless F-Droid itself becomes an approved and verified developer source under Google’s new system.
In summary, yes, this new policy may “kill” or severely restrict F-Droid and its apps on mainstream Android devices because it curtails the ability to install non-verified apps easily on certified devices. Users could only install those apps by disabling protections like Play Protect or on non-certified devices, which is a high barrier for most users.
I’m assuming they won’t explain the details until the last minute. To me, it shouldn’t include open source because they can scan the code, but you know it will. I’m hoping there will be a class-action suit, but that would require large funds. Hopefully, EFF and/or other orgs will help and f-droid can join in. We’ll see. I’m no expert, so this is all out of my tail. If someone knows better or has more detail, I’d like to know
What these foogle and GAFAM need to be thought is, stop with monopoly. Kick their rear and drop their share prices to make them loose instantly. Daily for months and years. Let them come to their knees. Big time a…
That’s not really practical for most people. Importantly many banking and streaming apps won’t work. These apps rely on hardware-backed Play Integrity checks to verify the device and block anything considered “abuse or malicious.”
afaik, they try to work with some OEM to have a device that’s up to their standards (Frequently Asked Questions | GrapheneOS), as Pixels have become unsupportable
Is my understanding correct this will actually significantly impact F-Droid since it enforces install limits on duplicate package IDs with differing signing keys that are registered after the first?
So basically only apps that the original developer registers and is using reproducible builds are fine.
And the apps that use a unique package ID for F-Droid.org are also maybe fine if they allow F-Droid to be a validator, which is probably unlikely.
The remaining 85% are basically guaranteed to get stuck in limbo?
Google has announced that, starting in 2026/2027, all apps on certified Android devices
will require the developer to submit personal identity details directly to Google.
Since the developers of this app do not agree to this requirement, this app will no longer
work on certified Android devices after that time.
) submit F-Droid’s too