Google Feedback Form for Android Developer Verification Requirements
Key topics
The cat's out of the bag: Google's plan to require developer verification for direct Android app installations has sparked heated debate, with commenters warning it could give Google and governments the power to ban apps at will. Zak, the original poster, kicked off the discussion by highlighting the potential risks, while others like Ms-J and Pfhortune urged fellow developers to fill out Google's feedback form to voice their concerns. Some submissions, like zb3's diplomatic yet candid response, showcased the diversity of opinions, with Ms-J praising its sincerity and acknowledging the gradual erosion of Android's open-source spirit. As the community rallies to make their voices heard, this thread feels timely and relevant, capturing the tension between open computing and increasing regulatory pressures.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
N/A
Peak period
3
2-3h
Avg / period
2
Key moments
- 01Story posted
Aug 26, 2025 at 3:18 PM EDT
4 months ago
Step 01 - 02First comment
Aug 26, 2025 at 3:18 PM EDT
0s after posting
Step 02 - 03Peak activity
3 comments in 2-3h
Hottest window of the conversation
Step 03 - 04Latest activity
Aug 26, 2025 at 7:37 PM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
===
Let me start by saying that I don't even fully know in WHICH cases those requirements would apply.. would it only apply when "Play Protect" is on [understandable]? Would "adb install" be affected too [completely crazy]? How would that handle personal apps that are not distributed? Further, how would it even handle Android Studio, would we need to show a government ID to run the "hello world" app made in Android Studio, is that what you want Android to be?
Second, it's not fully clear WHAT those requirements are. How come you can cite security concerns yet claim that the contents of the APK are not verified.. then what if I create malware? It makes no sense.
As a "technical" person and a security researcher, I feel disproportionately affected. Not just by these requirements, because like I said above, I don't actually distribute any apps for others to use, I might just share the source code but that's it.
What worries me is that not only does Google not offer any usable system for developers/researchers directly (there are no official "userdebug" builds that we could use as a "daily driver"), but it seems Google is actually making it increasingly harder for others to make such systems..
As others have pointed out, AOSP seems to be getting killed piece-by-piece, more and more vendors are disabling the option to unlock the bootloader.. yet I NEED a version of Android that doesn't impose restrictions on me, I assumed the core feature of Android was that it was open and therefore suitable for technical people like me..
If Android becomes closed - even for expert users and developers - there will be no point in staying on Android, I might as well try iOS, because why would I choose a copycat when I could choose the original?
Sincerely, zb3
I agree that AOSP was deteriorating piece by piece. This was the inevitable next step.
This is the official feedback form linked from https://developer.android.com/developer-verification