Checked on 16 October 2026. This topic has changed since the first 2025 announcement. Dates below come from a June 2026 Android Authority timeline and earlier reports, so confirm with Google’s official developer pages.
What was announced
Google said it would require developers who distribute apps on certified Android devices to verify their identity. The aim, according to Google, is to reduce malware by making it harder for anonymous developers to repeat attacks. Google described the step as confirming who a developer is, not reviewing what their apps do.
The reported timeline
- Earlier coverage pointed to a global start in September 2026.
- The June 2026 timeline reports 30 September 2026 as the start of app registration requirements for users in Brazil, Indonesia, Singapore and Thailand.
- A wider expansion to certified devices is reported for 2027.
What it means for users
- Apps from Google Play and other major stores are expected to be covered through their developers’ verification.
- Installing apps from unverified developers is reported to need a more advanced flow, or ADB.
- Safe habits still apply: install from official stores, check the publisher and avoid apps from links in texts. See Cybersecurity Awareness Month phone habits.
What it means for publishers
- Register and verify your developer identity as soon as the programme is available to you.
- Keep company details consistent across Play Console, your website and your privacy policy.
- If you publish for clients, decide whether each app sits under your developer account or the client’s.
- Keep a clean portfolio: remove duplicated or abandoned apps that could harm trust.
What to watch
Dates and details may move. Check Google’s official Android developer pages and your Play Console messages. Pair this with the API 36 target deadline.