惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Microsoft Azure Blog
Microsoft Azure Blog
WordPress大学
WordPress大学
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
The Cloudflare Blog
U
Unit 42
D
Docker
Hugging Face - Blog
Hugging Face - Blog
博客园 - 聂微东
Recent Announcements
Recent Announcements
GbyAI
GbyAI
T
The Blog of Author Tim Ferriss
Last Week in AI
Last Week in AI
V
Visual Studio Blog
I
InfoQ
Google DeepMind News
Google DeepMind News
小众软件
小众软件
L
LangChain Blog
C
Check Point Blog
宝玉的分享
宝玉的分享
Martin Fowler
Martin Fowler
酷 壳 – CoolShell
酷 壳 – CoolShell
博客园 - 【当耐特】
J
Java Code Geeks
罗磊的独立博客

Danb Blog

August 2026: What I've Been Working On · Danb Blog Great Tech: Intel 2500k CPU · Danb Blog July 2026: What I've Been Working On · Danb Blog My Experience with Ubuntu Desktop 26.04 · Danb Blog Thumbnails for Orca 3MF in GNOME Files · Danb Blog Cheaper Sodastream Gas with a Big Tank · Danb Blog June 2026: What I've Been Working On · Danb Blog Running Snyk On Forgejo/Codeberg Actions · Danb Blog Tuta & Proton: An Open Source Client Does Not Result in an Open Source Service · Danb Blog May 2026: What I've Been Working On · Danb Blog 3D Printing Parts for my Greenhouse, Round 2 · Danb Blog Great Devices: Nexus 7 2013 · Danb Blog R36S Console RetroArch Stuck Menu Issue · Danb Blog April 2026: What I've Been Working On · Danb Blog Basic OpenCode Sandboxing with Docker · Danb Blog Games Played in 2025 · Danb Blog March 2026: What I've Been Working On · Danb Blog Shivam Mathur's "node-docker" Images are Awesome for PHP CI · Danb Blog February 2026: What I've Been Working On · Danb Blog Your BookStackApp project was assigned as a project for my Software Architecture course · Danb Blog My Sovol SV08 3D Printer Setup in 2026 · Danb Blog January 2026: What I've Been Working On · Danb Blog Epson Printer: The administrator password you entered was not recognized · Danb Blog Pressure to Follow Process · Danb Blog Online Shopping Email Notifications · Danb Blog My HomeLab Setup in 2026 · Danb Blog Linux Label Printing with the Phomemo D30 · Danb Blog OPNsense & Dnsmasq: Responding with specific DNS servers · Danb Blog An Impromptu Introduction to ZFS Drive Replacement at 1am · Danb Blog Experience with UK Medical Cannabis for Ankylosing Spondylitis · Danb Blog
Reporting to the CMA: Google Android Developer Verificati...
2025-09-18 · via Danb Blog

Recently Google announced a further push of its developer verification, in which it states that all apps on “certified Android devices” will be required to have developer verification. This includes apps which are distributed via other means like F-Droid or manual download, so goes far beyond the scope of their own distribution platform.

To become verified, developers would need to provide their personal details which includes uploading a “government-issued identity document”. They will also need to pay a fee, requiring a Google payments profile. Business will face additional requirements which include a website address, a D-U-N-S number, and to be verified in the Google Search Console.

This is a massive leap in control, further centralising approval power to Google across the entire Android ecosystem while cementing themselves as the ultimate gatekeeper of what users can run on their own devices, all under the guise of security. This is a further step away from an open ecosystem, while being harmful to any platform competition & innovation.

Personally I’ve been going through the process of adding my apps to F-Droid, worried about being able to keep up with the increasingly tricky & burdensome Play store requirements, while allowing an avenue of access that’s not reliant on Google. Yet even then, it would remain reliant on Google for everyone on standard non-modified/rooted/official devices.

As with their Web Environment Integrity a couple of years ago, as a UK resident I feel my best bet to counter this is via the Competition & Markets Authority (CMA).

I have submitted a report to the CMA, the contents of which you can see below. If you’re in the UK, and care strongly about open platforms, I’d advise you to also report this which can be done here.

Report

Note: I wrote this up quite quick, it could be a lot better but I’m not sure how much extra detail actually helps for these kinds of reports. The main thing really is just to bring this kind of thing to the CMA’s attention.

Google are introducing required developer verification for Android applications, including those which are installed outside their own Google Play Store: https://android-developers.googleblog.com/2025/08/elevating-android-security.html

This further centralises control of the wider Android platform to Google, allowing them to act as a gate-keeper even beyond their own means of distribution. These changes also impact the ability for alternatives to innovate and survive since to engage with the existing large Android market they’d still be requirement to interact with Google, and agree to their terms/requirements. I’m also confident these requirements would also play into the integrity checks that are becoming increasingly used by applications, which would further tie a range of applications down to just Google’s approved ecosystems, and thus make it harder for alternatives to thrive.

I believe it’s in the interest of the UK public, business competition, and the UK’s own tech sovereignty that such platforms which are so engrained in society are made more open and diverse rather than being further controlled & monopolised by few US tech firms.