Google is rolling out a new Android Developer Verification process that will apply to all developers, including those with legacy Google Play Developer accounts.
Starting in April 2026, Android will introduce a new system service that checks whether an app is associated with a verified developer. Enforcement begins in September 2026 in select regions (Brazil, Indonesia, Singapore, and Thailand), with a broader global rollout expected in 2027.
In short: if you’re distributing Android apps, whether through Google Play, third-party stores, or direct APK downloads, this is something you’ll want to pay attention to.
Going Through the Process
As an independent Android developer who has been building and distributing apps outside of the Play Store, I recently went through the verification process myself.
For the most part, it was straightforward. I was asked to provide a short description of my Android development experience, verify my identity using a government-issued ID, and pay the standard $25 registration fee.
I have to admit, the developer registration and identity verification process felt a bit alarming, definitely a shift from the more lightweight setup Android developers have been used to in earlier years of Android development.
Registering Y-Corner Apps
After getting verified, I registered all of the apps currently available here on Y-Corner:
- Chrono Maps
- Cid’s Aerial Views
- Dragon Alchenomicon
- Dragon Geo
- Go There Now
- Map of the Nocturne
- Robot Master Database
For apps that I had previously published on the Google Play Store, there was an extra step involved. I needed to generate a new build that included a properties file signed with the same signing key originally used for Play distribution.
These are the following instructions that I encountered when registering previously published Google Play apps:
Sign and upload an APK
To finish verifying ownership of <app package name>, sign an APK with the private key that corresponds to the public key you provided, and upload the APKThe APK you upload is used only for the purpose of verifying your private key. You do not need to upload the actual APK that you distribute. Learn more
Key details
<app package name><public key registered with app>
How to sign an APK
Copy the snippet below. This is an identifier that is unique to your account.<identifier>
In your IDE, navigate to your app’s source tree.
You can use an empty project with the same package name that you’re registering, or your actual app.
Inside the assets folder, create a file named adi-registration.properties.
Make sure to use this file name exactly.
Open the file and paste in the snippet that you copied.
View a sample GitHub project to see the required file structure, and where to paste your snippet.
Build a release APK and sign it with the private key that corresponds to the public certificate fingerprint that you provided in the previous step.
Upload your signed APK here.
Android will check the signature and register your ownership.
Once submitted, the APKs were reviewed and verified surprisingly quickly—within just a few minutes in my case.
Why This Matters
This change goes beyond just the Play Store. It directly impacts sideloading and alternative distribution methods.
Even if you’re distributing apps via direct download (like I do here on Y-Corner), your apps will still need to be associated with a verified developer. Otherwise, they may eventually be blocked or restricted from being installed on Android devices.
For independent developers, this is a pretty significant shift. If you haven’t gone through the verification process yet, it’s worth getting ahead of it now.