NewsScams & security

Android starts blocking unverified apps worldwide from January

Google starts rolling out Android developer verification worldwide in January 2027. What it means for apps installed outside Google Play, and the opt-out.

a people-in-action visual metaphor at the door of an Australian suburban pub at night: a burly halftone bouncer in his forties in a black bomber jacket stands at the doorway holding out one hand to check an ID card; in front of him waits a short queue of three halftone cardboard parcels with little legs, each the shape of a square app icon, the first one holding up its ID card; a halftone woman in her thirties stands to one side, watching from under the pub's verandah. the only full-colour element is the green Android robot head logo, drawn faithfully and large on the bouncer's jacket badge; no other logos and no readable words
Illustration: Digital Advisors

If you’ve ever installed an Android app from a website instead of Google Play, that’s about to get stricter. Google will start blocking apps from developers who haven’t verified who they are.

Google announced the timing on its Android Developers Blog on 19 November. The global rollout begins in January 2027. It then gradually expands to all countries and all install sources over several months. Google hasn’t said when Australia’s turn comes.

Every app needs a name behind it

The change covers apps from everywhere: Google Play, other app stores, files downloaded from a website and links someone sends you.

Developers have to verify their identity with Google and register their apps. Once protections are live where you are, a certified Android phone won’t install an app that hasn’t been registered.

It applies to certified Android devices running Android 8 or later. The checks are delivered through Google Play services.

Google started with participating stores in Brazil, Indonesia, Singapore and Thailand on 30 September. The global rollout begins with seven app distributors: Google Play, Galaxy Store, Honor, Oppo, Xiaomi, Transsion and Vivo.

Why Google is doing it

Google’s pitch is scams. Its FAQ describes a familiar trick. A scammer pressures someone into installing an app that is really malware, built to steal personal details and drain bank accounts. Take that app down and an anonymous replacement appears.

Tying every app to a real, accountable identity is meant to break that cycle. “Millions” of apps have been registered since March, covering more than 99% of Android app installs worldwide. So for most people, nothing will look different.

The way around it takes a day

Power users haven’t been locked out completely. Google has built what it calls an advanced flow that lets you install apps from unverified developers, if you accept the risk.

It isn’t a quick toggle. You first turn on Android’s Developer options. Then, in Settings, go to System, then Developer options, and turn on Allow apps from unverified developers.

That starts a one-time, 24-hour security delay. Afterwards, you choose whether to keep the setting on for seven days or indefinitely. Each unverified install still shows a warning, and you have to tap Install anyway.

Google’s own help page warns that scammers pose as bank fraud teams, tech support or delivery services to talk people into installing fake apps. If someone on the phone is walking you through this setting, hang up and call the organisation back on its official number.

Who needs to do something

Most Android users don’t. The apps they use are very likely already registered.

Businesses that hand out their own Android app outside Google Play are a different story. That might be a booking app sent to customers as a download, or a tool shared with staff. Those apps need to be registered before verification reaches Australia.

There are a few exceptions and lighter options:

  • Work phones: apps installed from your organisation’s own store on managed devices don’t need verification. Google still recommends registering them, in case someone installs one elsewhere.
  • Students and hobbyists: a free limited distribution account needs no government ID. It can share an app with up to 50 authorised devices, up from 20.
  • Developers testing their own apps: installs through Android Debug Bridge (ADB), the developer tool, don’t need verification.

Google lists the fee for a full account as $25, similar to Google Play’s registration fee. Developers already on Google Play should check their apps’ registration status in Play Console. Organisations also need a D-U-N-S number, a business identifier from Dun & Bradstreet. Google says getting one can take up to 28 days.

It’s not the only recent change for apps from outside Google Play. In October we covered how registered rival app stores get one-tap installs in Australia. Google has also been adding scam checks to Google Messages.

Checklist

  • Check that apps you install from outside Google Play are registered. Ask each developer: once verification reaches Australia, unregistered apps won’t install by default on certified Android phones.
  • Register your own business app. Use the Android Developer Console, or Play Console if you’re already on Google Play. Registering an app takes less than ten minutes once your identity is verified.
  • Apply for a D-U-N-S number early if you register as an organisation. It’s free from Dun & Bradstreet but can take up to 28 days.
  • Hang up on anyone who asks you to allow apps from unverified developers. Scammers pose as bank fraud teams, tech support and delivery services to get fake apps installed.