Android & App Freedom ThatGuy[A]

Google's Android developer verification announcements: a dated record

Google's Android developer verification policy has changed shape since its first announcement. This thread keeps the official announcements in date order, so an older promise is not mistaken for the rule in force today. It is our reading of Google's published documents, not a statement by Google. For the practical guide to installing apps, see /t/67/; for F-Droid's response, see /t/192/.

The starting point — 25 August 2025

Google announced that apps installed on certified Android devices would need to be registered to a developer whose identity it had verified. Its stated reason was accountability for repeat malware and scam publishers. The distinction matters: Google described this as an identity check, not a security review of each app. A verified developer can still publish unsafe software.

The announcement said the requirement would begin in selected countries in September 2026 and expand globally from 2027. It also said developers could keep distributing through their own sites or other stores. That was an early programme outline, not the final description of the first enforcement phase. Later Google posts narrowed and clarified that phase; the dated entries below record those changes.

There is a real policy argument here. Verifying publishers may raise the cost of repeat abuse, but putting registration in one company's hands can also burden independent stores, small developers and people who need to publish pseudonymously. The identity check alone does not resolve that trade-off.

What to watch next: exactly which stores and devices are covered; whether direct downloads remain outside the initial checks; what a developer must hand over to register; whether the documented alternatives for unverified apps work as described; and what Google actually announces for 2027. We will add a dated entry when a primary source changes one of those answers.

Source for the original announcement (25 August 2025): https://android-developers.googleblog.com/2025/08/elevating-android-security.html
Current Google programme page: https://developer.android.com/developer-verification

If you build or distribute an Android app, which requirement would change your plans? If you install outside Play, which path have you actually tested? Please link what you observed and say which device and region you tested it in.

Actualizaciones

ACT.

19 March 2026: Google describes an advanced flow for unverified apps

Google responded to feedback from people who want to install software from unverified developers. Its March post introduced an 'advanced flow' for that choice: a one-time setup designed to slow coercion scams, followed by an explicit install decision. This was a design announcement, not evidence that the flow was already available on every device in March.

The significance is straightforward: Google's first outline could be read as a hard gate for an unregistered app. The later design leaves a path for a user willing to take the extra steps. Whether that path is convenient enough for ordinary independent distribution is a separate question, and F-Droid's objections do not disappear because a bypass exists.

Google's post: https://android-developers.googleblog.com/2026/03/android-developer-verification.html

ACT.

30 March 2026: developer registration opens more broadly

Google announced that verification and app registration were rolling out to developers through both Play Console and the new Android Developer Console for apps distributed outside Play. This was preparation for user-facing enforcement, not the day installation rules changed. Google also listed the power-user advanced flow and ADB as routes for unregistered apps.

If you develop an app, the relevant distinction is where you distribute it. A Play account may already have passed identity verification, while a developer working only outside Play needs the Android Developer Console. Google's post later gained a 29 September clarification; the latest scope belongs to the dated entry below, not to a broad reading of the older March wording.

Official announcement: https://developer.android.com/blog/posts/android-developer-verification-rolling-out-to-all-developers-on-play-console-and-android-developer-console

ACT.

18 June 2026: Google names seven stores and four countries

Google's June announcement made the initial enforcement scope much more specific. From 30 September it said checks would begin for participating stores in Brazil, Indonesia, Singapore and Thailand. It named Google Play, HONOR App Market, OPPO App Market, Galaxy Store, Palm Store, V-Appstore and GetApps. The programme applies on certified Android devices; the current guide specifies Android 7+ and, for distribution outside Play in this first phase, phones and tablets.

The post also described limited distribution accounts for students and hobbyists (up to 20 devices without government ID or a fee), developer APIs for registration workflows, and the advanced flow plus ADB for unregistered apps. These are Google's announced options, not proof that registration is painless for a public repository.

Google still says the requirement will expand globally in 2027. It has not given a precise global start date in these documents.

Official post: https://developer.android.com/blog/posts/android-developer-verification-building-a-safer-ecosystem-together
Current guide: https://developer.android.com/developer-verification/guides

ACT.

29 September clarification; checked 2 October 2026: the first phase is narrower

Google added a 29 September note to its March rollout post saying its details had changed: on 30 September protections would begin for participating stores in selected regions, with global expansion in 2027. The current official guide names the four countries and seven stores above. The FAQ is more explicit: direct sideloading and distribution through stores outside that list are not subject to this initial phase yet. That is not a promise about the shape of the 2027 expansion.

The FAQ also says ADB installs keep working without registration. The advanced flow for unverified developers is documented separately. Neither a developer ID nor a successful installation is an audit of the APK's safety.

This is why 'Google has banned APK installation outside Play' is an inaccurate description of the September 2026 phase. Equally, saying 'nothing changes' ignores the checks at the participating stores and Google's stated global direction. Check the live FAQ before acting on an old article: Google has amended this rollout more than once.

Google's dated correction: https://developer.android.com/blog/posts/android-developer-verification-rolling-out-to-all-developers-on-play-console-and-android-developer-console
Current FAQ: https://developer.android.com/developer-verification/guides/faq
Programme timeline: https://developer.android.com/developer-verification

↑ 8

Debate

Comentarios

1

Los comentarios más recientes aparecen primero en cada nivel; las respuestas siguen bajo su comentario principal.

Escribir Únete para participar en la discusión.

Keep this thread pinned. Having the dated record is the only way to catch the goalposts moving.
↑ 0 Responder