Android developer verification is live. Here’s what every indie developer must do now

For most of Android’s history, anyone could build an APK and anyone could install it. That is changing. Google now requires apps on certified Android devices to come from developers who have verified their identity, and the rule covers apps installed from outside Google Play too.

The change has been controversial in developer communities, and a lot of what is shared about it is wrong. Here is what Google has actually announced, what it means for you, and what to do this week.

What changed on 30 September 2026

According to Google’s developer verification page, protections began on 30 September 2026 “for all users who install apps from participating stores in Brazil, Indonesia, Singapore, and Thailand on certified devices running Android 7+.” Google says the capability “will be expanded globally for all apps on certified Android devices in 2027.”

“Certified Android devices” are the phones and tablets that ship with Google Play Protect and Google’s apps preinstalled, which is almost every Android phone sold outside China.

30 Sep 2026

protections start in 4 countries

2027

global expansion, per Google

99%

of Play apps registered automatically

20

devices on a free limited distribution account

Why Google is doing it

Google’s stated reason is scams and malware. When the plan was announced in August 2025, Google said it had found over 50 times more malware from internet-sideloaded sources than from apps on Google Play. Google has compared verification to an ID check at the airport: it confirms who the developer is, separately from the security scanning of the app itself.

Which path are you on?

1. You publish on Google Play

This is most readers of this blog. Google says Play “automatically registers 99% of apps”, and developers who already completed Play Console identity verification have likely met the requirement. Use Play Console to register any remaining apps, or apps you also distribute outside Google Play.

2. You distribute outside Google Play

If you ship APKs from your own website, GitHub releases or another store, you register through the new Android Developer Console, which Google built for developers who distribute exclusively outside Google Play.

3. You are a student, teacher or hobbyist

Google’s limited distribution accounts let you share apps with up to 20 devices without a government-issued ID or registration fee. That covers classroom projects, betas for friends and personal tools.

Your 15-minute checklist

1. Open Play Console and confirm your developer account shows identity verification as complete.
2. Check that every app you distribute, including ones only shared outside Play, is registered to your account.
3. If you have apps that live only outside Play, create an Android Developer Console account and register them.
4. If you ship test builds to friends or students, move them to a limited distribution account.
5. Keep your contact details current. Verification ties your apps to a real identity, and outdated details can block updates.
6. Watch for Google’s regional rollout announcements before 2027 if most of your users are outside the first four countries.

Does this affect your Play Store rankings?

There is no indication that verification itself changes search rankings on Google Play. What it can affect is distribution: if an app outside Play is not registered, users on certified devices in participating regions may be blocked from installing it. For Play-only developers who are already verified, rankings continue to depend on relevance, conversion and quality as before.