Comment by fareesh
8 hours ago
from what i understand:
- if you compile from source and deploy via adb nothing changes
- if you use a closed source binary, the identity of the owner becomes mandatory
so the issue is anonymously published closed source software?
> if you compile from source and deploy via adb nothing changes
That's not how I understand it. Do you have a source?
"Starting in September 2026, Android will require all apps to be registered by verified developers in order to be installed on certified Android devices."
https://developer.android.com/developer-verification
https://android-developers.googleblog.com/2025/09/lets-talk-...
> Android Studio is unaffected because deployments performed with adb, which Android Studio uses behind the scenes to push builds to devices, is unaffected.
Thanks.
So, simply sending a download link for an APK to a friend is not enough anymore - I now have to teach them how to install and use adb.
EDIT
> we are also introducing a free developer account type that will allow teachers, students, and hobbyists to distribute apps to a limited number of devices without needing to provide a government ID.
Depending on how they implement that, this would at least partially improve the situation. Sounds like no ID is required, but I assume the whole ordeal with registering each app is still mandatory.
> anonymously published closed source software
Yes, like the software for my ebike conversion kit for which I only have the APK. I have vetted the software and would like to install it. If Google blocks that, then fuck them.
> - if you use a closed source binary, the identity of the owner becomes mandatory
So I can't just build an apk and distribute to others? What's the process for providing identity?
Paying Google $25 for the privilege of giving them a picture of your face and license to save in their cloud.