We need to fight Google's new ID requirement for app developers. It isn't like showing ID at the airport. More like showing it at the printing press and only IDed authors are allowed to print books.
What Google doesn't talk about is that they build this ID system to ban developers and their apps.
People saying "But I use a degoogled custom ROM, so I won't be affected" are missing the point. Apps not on Google Play are already a niche. Banning them on most people's devices is a big issue, even if some people can still escape.
Also the general trend of Google becoming more closed may make even custom ROMs impossible eventually.
Under-reported detail: If you don't pay a fee to Google, they limit how many people can install your apps and how many apps you are allowed to have.
Source: https://developer.android.com/developer-verification/guides/android-developer-console
Google asks what we think of their plans to block Android app installs outside of Google Play (unless the developers let Google verify their identity and pay a fee).
Want to tell them your opinion, just submit this form:
Use this form to submit questions or feedback about the new Android developer verification requirements announced in August 2025. You can learn more about the requirements in the Android developer verification guide. Sign up for early access here.
The documentation also talks about a "developer verification policy" that may allow "the user to bypass a verification failure caused by network issues".
Also, there will be a "lite version of the developer verification", but what this means is still unclear.
Android "hobbyist developers can get a free account [for developer verification] but will face strict distribution limits, requiring them to manually authorize each device installing their app."
Having to get a device identifier from each of your potential(!) users and then manually allow-list them is an impractical limitation making this account type useless for most use-cases while allowing bad actors to exploit it.
Source: https://www.androidauthority.com/how-android-app-verification-works-3603559/
Google is now "building a new advanced flow that allows experienced users to accept the risks of installing software that isn't verified." https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html
But hasn't shared any details on how this would look like. Also, it wouldn't be the software that is verified, but the developer's identity.
Google is otherwise continuing to push ahead with developer verification.
@grote that is #literally #malware and I hope you intent to collect said #evidence and seek legal advice re: pressing charges against them...
@[email protected] thanks for the info. Personally, I use @[email protected] / #Fdroid *exclusively* and think that their approach for their own repo (pull the #git sources for n #App and compile the release version before signing it with Fdroid's key) is sufficiently secure. - OFC one can add 3rd party repos to it *and* those could be malicious as similar to #Linux package managers like `apt`, they've to provide their own signatures and knowingly adding malicious repos *will enable #malware*… Personally, I hope @[email protected] and other #regulators will tell #Google that this is unacceptable and I hope developers will instead file charges for #blackmail and #extortion against Google rather than #SelfDoxxing!