Posted by Matthew Forsythe, Director, Product Management, Android App Safety
Android recently announced developer verification, an extra layer of security that deters bad actors and makes it harder for them to spread harm.
Developer feedback is essential as we build this process. One of the most important themes we hear from the developer community is the need for more lead time to adapt to changes, which is why we announced this requirement more than a year before it takes effect. This extended timeline allows you to ask questions, provide feedback that will help shape the final process, and prepare for the new requirement, ensuring a smooth transition for your workflow.
We’re committed to answering your top questions, which you can find regularly updated in our guides and FAQ, and we’ve compiled the most frequent answers below. For a deeper discussion on developer identification, check out our conversation on Android Developer Backstage.
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.
How does developer verification impact my use of Android Studio?
We are working to ensure these changes don’t have an impact on your day-to-day workflow so you can continue building your apps as smoothly as possible. Participating in developer verification will not affect your experience in Android Studio, the official IDE for Android app development. You will continue to be able to build and run an app even if your identity is not verified. Android Studio is unaffected because deployments performed with adb, which Android Studio uses behind the scenes to push builds to devices, is unaffected. You can continue to develop, debug, and test your app locally by deploying to both emulators and physical devices, just as you do now.
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.
Please let us know if you have any feedback or questions about the verification requirements.
