AI & TechnologyAndroid Developer Verification: Dates and What to Do

Android developer verification means apps installed from participating stores on certified Android devices must be registered to a developer who has verified their identity, and Google's pages say the first protections began on September 30, 2026 in Brazil, Indonesia, Singapore and Thailand. Google plans to expand verification globally to all apps on certified devices in 2027. If you publish on Google Play, most of the work is already done for you. If you distribute outside Play, you register in the Android Developer Console.

The facts below come from Google's developer verification pages and two Android Developers Blog posts, as shown in the sources. I checked each one on October 18, 2026.

Disclosure: App369 is my studio. I build and fix Android and iOS apps, mostly in Flutter, and the last section mentions what I sell. Google doesn't pay me for anything on this page.

What the requirement is

Google's August 25, 2025 announcement says Android will require apps to be registered by verified developers. It says verification confirms who the developer is. It does not review app content or source code.

Google's overview page describes it as an extra security layer to deter bad actors. It applies to certified Android devices running Android 7 or higher, according to the FAQ.

Dates, then and now

Google's plan changed between the first announcement and the current pages. The newer pages win.

One change is worth noting. The 2025 post speaks of requirements for installing apps on certified devices. The FAQ now says the September 30 deadline applies only to the specific participating stores, and that sideloaded apps and other stores are not subject to the requirements yet. The FAQ also says that after the deadline, unregistered apps cannot be installed from participating stores in the selected regions.

What gets registered

Google's guides list three steps for every developer:

1. Sign up. Play developers are registered through their existing account. Everyone else creates an Android Developer Console account.
2. Verify your identity as an individual or an organization. Organizations must also provide a website, which is verified through Google Search Console. The FAQ adds that an organization needs a D-U-N-S number, and that getting one can take up to 28 days.
3. Register your package names. You prove ownership by providing an APK signed with your private key.

Which path you take

If you publish on Google Play

Google's Play Console guide says 99% of apps on Play were registered automatically using information you already provided. It still tells you to check your Play Console Home page. If you use Play App Signing, the FAQ says Google has the information it needs to identify your ownership, and eligible apps are part of the automatic registration.

New apps are registered when you create them in Play Console. If another developer already uses the package name, Play Console asks you to pick a different one.

The FAQ also says that if you distribute on Play, your apps across all form factors must be registered. Enforcement outside Play applies to mobile and tablet form factors in the selected regions.

My advice: open the Play Console Home page this week and confirm every app shows as registered. Also confirm that apps you ship outside Play, such as a direct APK download, are registered too.

If you distribute outside Google Play

The Android Developer Console guide gives these steps for registering a package name:

1. Create an account with your Google Account and complete identity verification.
2. Open the Packages page and enter the package name.
3. Add the SHA-256 certificate fingerprint of your app's signing key. The status becomes In review.
4. For an existing package name, sign an APK with your private key and upload it. Google says the console gives you a snippet to add to the APK's asset folder.
5. When it is registered, you get an email and the status changes to Registered.

The FAQ says the console lets you add and verify multiple signing keys for one package. It also says that if you lose your signing key, you won't be able to register your packages. If a package name is already claimed, Google may tell you your key is not eligible to claim it, and you should consider a different package name.

My advice: find your release keystore backup before you start. Everything else depends on that key.

Fees

The FAQ says the $25 fee for the Full Distribution account in the Android Developer Console helps cover administrative costs, similar to Play's $25 registration fee. It says Google is waiving the fee for developers who qualify for a Limited Distribution account. The Play Console guide mentions no fee.

Students and hobbyists

Google's limited distribution guide describes an account for students, hobbyists and learners who share apps with a small number of people.

• You can share apps with up to 20 devices that users have explicitly authorized.
• The account is free and needs no government ID.
• You need a Google Account with 2-Step verification, a linked Google payments profile for your legal name and address, and a contact email that isn't shown publicly.
• The FAQ says Google supports migrating a limited account to a full account, but not the other way around.

What changes for users who sideload

Google's March 19, 2026 post says it added an advanced flow after hearing from power users who want to install software from unverified developers. According to the FAQ, it is a one-time setup:

1. Turn on developer mode.
2. Confirm you aren't being coached by someone pressuring you.
3. Restart the phone and sign in again.
4. Wait one day, then verify with biometrics or your device PIN.
5. Choose to allow installs for 7 days or indefinitely.

Unverified apps still show a warning, and the user taps Install Anyway. The FAQ also says developers are free to install apps without verification using ADB, and that unregistered apps can be installed or updated only with the advanced flow or ADB. If the advanced flow is off, updates to unregistered apps fail.

What it means for a Flutter app

Nothing on Google's pages is specific to Flutter. Google registers an app by its package name and the key that signs it. In a Flutter project, that means two things to look up:

• The package name, set as the applicationId in android/app/build.gradle or build.gradle.kts.
• The key that signs your release build, which is your upload key if you use Play App Signing, or your own app signing key if you ship a direct APK.

If you use Play App Signing, your Play-distributed apps are covered by the automatic registration described above. If you also ship a direct APK, make sure that APK is signed with a key you have registered. My advice: keep one package name per app across Play and your own downloads, so there is one record to check.

This is a separate track from the Play Store policy changes. If you are also working through those, see the target API 36 guide, the 16 KB page size guide and the Play Billing Library guide.

Developer APIs

The FAQ describes two APIs. The Status API checks package name eligibility and registration status. The Console API registers package names and manages keys programmatically, and Google says both are designed for bulk registration or CI/CD pipelines. The FAQ also says you can check status in Play Console, the Android Developer Console and Android Studio Panda 4 and higher.

Need a hand?

If you're not sure what your Android app needs to register, or an install starts failing on verified devices, the App Fix Ticket covers it in two fixed-price steps. A $450 Diagnosis gives you the root cause with evidence and a fixed repair quote within 3 business days, credited toward the fix. If you go ahead, the $1,200 Fix takes 5 business days and comes as a pull request. Or send me a short description.