Skip to main content

Android apps installed outside Google Play

Our staff install our Android app outside Google Play. Will it stop working?

Google is starting to require every Android app to be registered by a verified developer. Once that reaches your phones, an unregistered app installed from a link, a file or a vendor's installer cannot be installed or updated on most Android phones without a deliberate workaround. Apps your IT team pushes to company-managed phones are exempt. If you are not sure who holds your app's signing key, start with an $8,000 audit: in 1 to 4 weeks you learn which of your apps are affected and what it takes to register them.

For businesses whose drivers, crews or customers depend on an Android app.Audits are $8,000, in 1 to 4 weeks.

Who this is for

This is for you if

  • Drivers, field crews or warehouse staff install your app from a link, a file or a vendor's installer.
  • Some staff or contractors use the app on their own phones, outside your device management.
  • A former developer or vendor built the app, and you don't know who holds its signing key.

This is not for you if

  • You need a standalone website with no app behind it.
  • Your app is only on Google Play and uses Play App Signing: Google registers it for you.
  • Every phone is company-managed and gets the app from your managed store.
  • You hold the signing key and your company's documents: you can register it yourself, and Google says that takes about 10 minutes.

Right now · Reviewed November 4, 2026

What changed: Android developer verification

Each fact links to Google's own Android Developers pages. The dates are still moving, so this block is reviewed and expires on its own.

Where it starts

Since September 30, 2026, protections apply to installs from participating app stores in Brazil, Indonesia, Singapore and Thailand. Google says it will expand them "globally for all apps on certified Android devices in 2027."

Source: Android Developers (Creative Commons Attribution 2.5)

Sideloaded apps, for now

Google says that if users sideload your app directly, "these new verification requirements won't apply to your app yet", and recommends verifying before the global rollout.

Source: Android Developers (Creative Commons Attribution 2.5)

Company-managed phones

"Apps distributed through your organization store, on managed devices, won't need to complete the verification requirements." Google still recommends registering them, for installs from anywhere else.

Source: Android Developers (Creative Commons Attribution 2.5)

Updates fail, not just installs

Once enforcement applies, an unregistered app can only be installed or updated after a one-time "advanced flow" on each phone, with a 24-hour wait, or by a developer with a cable (ADB). Otherwise "updates to unregistered apps will fail."

Source: Android Developers (Creative Commons Attribution 2.5)

What a company needs

A D-U-N-S number (free, but it "can take up to 28 days"), a website verified in Google Search Console, official company documents, and a $25 fee in the Android Developer Console. It applies to certified phones and tablets on Android 7 and up.

Source: Android Developers (Creative Commons Attribution 2.5)

What to do first

  1. List every Android app your people use that does not come from Google Play.

    Include vendor apps, scanner apps and anything installed from a link or a file.

  2. For each one, write down how it reaches the phone.

    Your managed store on company-managed phones is exempt. Links, files and personal phones are not.

  3. Find out who holds each app's signing key and developer account.

    If a former developer or vendor holds them, fix that first: see "Our developer is gone, and we don't control our code or App Store account."

  4. Get a D-U-N-S number now if your company doesn't have one.

    It is free but can take weeks, and verification cannot finish without it.

  5. Verify your company and register each app.

    In Play Console if you already publish there, otherwise in the Android Developer Console.

  6. Test an install and an update on a phone that is not company-managed.

    That is the case that breaks first.

  7. Make registration part of every release.

    New apps and new signing keys need registering too.

What it costs

Audits are $8,000.

For one app and one codebase, in 1 to 4 weeks. Larger apps are quoted higher. If the audit finds work to do, such as recovering the key, re-signing or moving to Google Play, that work is priced separately; keeping the app registered release after release can be part of maintenance, from $10,000 a month with a three-month minimum. Prices are for remote work. On-site work is quoted separately and priced higher.

How the audit works

What you get from the audit

Which apps are affected

Each Android app your people use, how it is installed, and whether verification applies to it.

A key and account check

Who holds each signing key and developer account, and whether your company can register the app.

A registration plan

The documents, accounts and order of steps, including what to do if a key is missing.

A fixed quote

For any work that follows, if you decide to go ahead.

Common questions

What is Android developer verification?

Google's requirement that every app installed on certified Android phones is registered by a developer whose identity Google has checked. Apps on Google Play are mostly registered automatically; apps installed any other way need registering by whoever holds the signing key.

Does this affect apps on our company-managed phones?

Not if your IT team installs them from your organization's managed store. Google still recommends registering them, because the same app installed from a link or on a personal phone is treated differently.

When does it reach phones in the United States?

Google has not given a date for the United States yet. The current dates are in the Right now block above, and we review them when Google changes them.

What if our old developer has the signing key?

Ask for it, along with the developer account, before anything else. Google says a lost key means you cannot register the app; the fallback is a new version under a new name and key, which every phone must install again.

Can't our staff just use the workaround?

They can, phone by phone: it means turning on developer settings, waiting a day and confirming. For a fleet of drivers or a warehouse, that is a support job every time a phone is replaced.

Tell us what is going on with your app.

A short note is enough. We reply with whether we can help and what the first step costs.

Tell us what is going on