- Does this mean sideloading is going away on Android?
Absolutely not. Sideloading is fundamental to Android and it is not going away. Our new developer identity requirements are designed to protect users and developers from bad actors, not to limit choice. We want to make sure that if you download an app, it’s truly from the developer it claims to be published from, regardless of where you get the app. Verified developers will have the same freedom to distribute their apps directly to users through sideloading or through any app store they prefer.
- Making APKs available to your test team
If your team’s current test process relies on distributing APKs to testers for installation using methods other than adb, you will need to verify your identity and register the package. This also applies if you make APKs available to your test teams through Google Play Internal Testing, Firebase App Distribution, or similar solutions through other distribution partners.
- Do I still need to register my apps if I’m only distributing to a limited number of users?
We recommend you register. It’s a simple, one-time process that will allow anyone to download and install your app. However, if you prefer not to, 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.
- What can I do to prepare for developer verification?
The best way to get ready and stay updated is to sign up for early access. We’ll start sending invitations in October.
We recommend you participate in developer verification because, even though verification is not required to develop apps with Android Studio, you will need it to distribute apps to certified Android devices. Apps installed through enterprise management tools on managed devices will also be installable without being registered.
I understand where you’re coming from with this comment. I’m also generally frustrated when I see people commenting on sensationalized headlines without taking the time to learn more.
I, however, have read their published plans for developer ID’s.
Think back, and be objective about how Google has managed Android since AOSP launched. Time and time again, Google has borrowed and adapted code which was submitted to the project by talented, passionate developers who expected no compensation. At each milestone, Google has taken steps to apply additional restrictions on developers- Siding instead with hardware manufacturers to limit the public’s ability to use their purchased hardware as they see fit.
I am aware that there is a balance that must be struck to limit expense, exploitation, and to prevent widespread security incidents and piracy, but how many times in the past have end users and developers been in this precise situation over the years? How long until Google decides that they don’t need the AOSP project at all and fork the entire project? They’ve already taken large parts of the framework private.
Maybe I’m a little jaded, but I can’t see a benefit here for anyone but Google and hardware manufacturers. This is just another step towards locking us out.