Android Developer Verification: What App Teams Should Know

For most of Android's history, anyone could build an APK and hand it to anyone else. Android developer verification changes that on certified Android devices: an app has to be registered to a developer whose identity Google has verified. On Google Play, most of this has already happened for you. If you sideload builds, ship through another store or send APKs to customers, it needs your attention. This guide covers what verification requires, the two consoles, the free account for students and hobbyists, the flow for power users, and the 2026 timeline. Google's details below come from its own pages as of 3 October 2026.

The short version

• Verification has two parts: a verified developer identity, and registered package names linked to your signing key.
• Google Play developers use Play Console, where Google says it has registered over 99% of Play apps. Developers who distribute solely outside Google Play use the new Android Developer Console.
• Limited distribution accounts are free, need no government ID, and let students and hobbyists share apps with up to 20 devices.
• Power users can still install unregistered apps through a one-time advanced flow, and ADB installs keep working.
• Google scheduled protections to begin on 30 September 2026 in Brazil, Indonesia, Singapore and Thailand, for installs from seven participating stores, with a global rollout in 2027 and beyond.

What verification requires

As of 3 October 2026, Google's developer verification guide says it links real-world individuals and organisations with their apps, and that Android requires apps to be registered by verified developers for users to install them on certified Android devices. Google's FAQ says the requirement applies to certified devices running Android 7 or higher, with the updates delivered through Google Play services.

There are two steps:

1. Verify your identity as an individual or an organisation, with information and official documents. Organisations also provide a D-U-N-S number and a website verified through Google Search Console.
2. Register your package names. In the Android Developer Console you enter the package name and the SHA-256 certificate fingerprint of your signing key. For an existing package name you then prove ownership by signing an APK with your private key, containing a snippet the console gives you to add to the APK's assets folder.

Registration is tied to the package name and the signing key, not to the framework. A Flutter or React Native app goes through the same steps as one written in Kotlin.

Play Console or Android Developer Console?

Sources: Google's guides for Play Console and the Android Developer Console, as of 3 October 2026.

If you are on Google Play

Google's March 2026 rollout post said that developers who have completed Play Console's verification are already verified, and that Google registers eligible Play apps for them. Its June 2026 update said 99% of apps on Play had been registered that way, and asked Play developers to check the Play Console Home page and register any remaining apps by 30 September 2026, to avoid removal from Google Play worldwide. If you have not looked at that page since the summer, look now. Our guide to the Google Play developer account covers Play's own identity checks.

If you distribute outside Google Play

The Android Developer Console is the place for apps that never go near Play: an APK on your website, a build for a customer, a store other than Google's. You sign up with a Google Account and choose a full distribution account or a limited one. Google's guides list the requirements and fees for each account type.

Limited distribution accounts

Google built a separate account type for people who do not distribute widely. As of 3 October 2026, its limited distribution guide says the account:

• Is free, and needs no government ID.
• Can register apps and share them with up to 20 devices that their users have explicitly authorised, through a handshake using QR codes or links and consent on the device.
• Needs a Google Account with 2-Step Verification turned on, a linked Google payments profile for your legal name and address, and a contact email address that Google does not show publicly.

Google aims it at hobbyists, individual learners and classroom projects. The FAQ says a limited distribution account can be moved to a full account later, but not the other way round. Twenty devices is a classroom or a family, not a beta programme for paying customers.

Installing unverified apps: the advanced flow

Google kept a route for power users who want to install apps from developers who are not verified. Its March 2026 post Balancing openness and choice with safety describes the advanced flow, which it said would launch in August 2026:

1. Turn on developer mode in system settings.
2. Confirm that nobody is coaching you to turn off your security.
3. Restart the phone and sign in again, which cuts off remote access or a call a scammer may be using.
4. Wait out a one-time, one-day protective period, then confirm with a fingerprint, face unlock or the device PIN.
5. Choose to allow installs from unverified developers for 7 days or indefinitely. Each install still shows a warning, with an "Install Anyway" button.

Separately, the FAQ says developers can still install apps with Android Debug Bridge (ADB) without verification, for building and testing apps that are not ready for wider distribution. Your own debug builds are not affected.

The 2026 timeline

Sources: Google's developer verification page and its March and June 2026 posts on the Android Developers Blog, as of 3 October 2026. These are Google's scheduled dates. This guide does not report how the 30 September start has gone in practice.

Which stores take part

Google's June 2026 update listed seven stores whose installs it would verify at the start:

• Google Play (Google)
• HONOR App Market (Honor)
• OPPO App Market (OPlus)
• Galaxy Store (Samsung)
• Palm Store (Transsion)
• V-Appstore (vivo)
• GetApps (Xiaomi)

Huawei AppGallery and Amazon's Appstore are not on that list. Our guide to Galaxy Store and AppGallery covers those two stores in more detail.

What it means if you sideload or ship outside Play

As of 3 October 2026, Google's FAQ answers the questions teams outside Play ask most:

• Other stores and direct installs. The 30 September 2026 deadline covers the participating stores. If you distribute through another store, or users sideload your app directly, the new requirements do not apply to your app yet. Google still recommends finishing verification before the global rollout in 2027.
• Form factors. Play developers must register their apps across all form factors. Outside Play, enforcement in the four countries covers phones and tablets, though Google recommends registering every form factor.
• Enterprise apps. Apps distributed through your organisation's store to managed devices do not need verification, because your IT admin has vetted them. Google recommends registering them anyway, in case someone installs them from another source or on an unmanaged device.
• D-U-N-S numbers. Organisations need one. The FAQ says getting one can take up to 28 days, so do not leave it until the deadline.

Google has also described two APIs for teams that ship many apps: the Android Developer ID Status API, to check whether a package name is registered, and the Android Developer Console API, to register and manage package names from a CI pipeline.

A checklist for teams outside Play

1. List every package name you distribute and where it goes: Play, other stores, your website, customers' devices.
2. Find the signing key for each one. Registration needs the SHA-256 fingerprint and an APK signed with the private key.
3. Decide on Play Console (if you also publish on Play) or the Android Developer Console.
4. If you are an organisation, check your D-U-N-S number and Search Console verification now.
5. Register before the global rollout, not after users report failed installs.

How FeedbackKit fits in

Verification decides whether your app installs. It does not change how your app talks to the services inside it. A FeedbackKit board works the same way whether a user installed from Google Play, from Galaxy Store or from an APK you sent them: the SDK reaches FeedbackKit with your project's API key, and every request lands on the same board. That suits teams who run a sideloaded beta alongside a Play release, or a classroom app shared with 20 devices.

On Android the board comes from the Kotlin SDK with Jetpack Compose screens (Kotlin docs), and there are SDKs for Flutter and React Native too. If you also ship on iOS, our Apple Developer Program guide covers Apple's side of identity, and requests from both platforms share one list. Here is how that looks in FeedbackKit, with sample data from a fictional hiking app:

Check your package names, find your signing keys, and get registered before 2027. When your users can install the app wherever they find it, give them one place to ask for what comes next: start free with FeedbackKit.