On Sept. 30, certified Android phones in Brazil, Indonesia, Singapore, and Thailand will stop installing apps from developers who haven’t registered an identity with Google — and not only from Google Play. As The Hacker News reported in June, the block extends to the stores run by Samsung, Xiaomi, OPPO, vivo, Honor, and Transsion. Same week, a solo developer’s Mastodon post about Play review times “regularly” exceeding a week hit the front page of Hacker News, where it collected 321 points and 306 comments of pure grievance.
Those are the same story, told by two audiences that have never once had to sit in the same room.
A Week Was a Pandemic Emergency in 2020
When Google warned developers in March 2020 that reviews could take “up to a week or even longer,” TechCrunch called the delay unprecedented, and it was: a COVID-era staffing collapse, temporary by definition. Six years later a week is the baseline.
That isn’t a queue-management failure. It’s a liability problem. In 2023 Google began telling new individual accounts to run 20 testers for two weeks before publishing, and warned of slowdowns as it put more money into review. Review stopped being a spell-check and became an underwriting exercise — every submission a candidate for fraud, malware, payment theft, and the sort of thing that puts a general counsel on a plane.
Here’s what the grievance thread skips. The political right spent fifteen years arguing that platforms are publishers, not pipes — that the liability shield was a giveaway and that Google should answer for what it distributes. Fine. Publishers vet. Vetting takes a week, and a week is the discount version.
Samsung’s Store Blocks It Too
The tell isn’t the delay. It’s the four countries.
If verification were a walled-garden play, the escape hatch would stay open: install the APK, use a third-party store, route around the gate. Instead the enforcement runs through the device-maker stores preloaded on certified hardware. That isn’t Google digging a moat. That’s Google building a liability firewall at the border of the markets most likely to make a bad app its problem — and doing it where the political cost is lowest, in countries whose consumers have the least lobbying muscle.
Which brings us to the honest description of the “open Android” era: it was open because nobody was on the hook. Carriers abdicated app certification years ago, partly because the same coalition now mourning Play’s review queue spent a decade telling them to get out of the software business. Antivirus software was supposed to be the backstop. It became a subscription product that mostly narrates what already happened to you.
The Constituency That Isn’t on Hacker News
The people with standing to complain about install restrictions are people who sideload. The people with standing to complain about malware are everyone else in those four markets, most of whom will never open a 306-comment thread and have no idea what an APK is.
A fraud-operations analyst at a mid-size bank in Jakarta, reached in a group chat mid-shift on a Tuesday, described what actually lands on the other end of an unverified install: a surprising number of customers who don’t know they installed anything, followed by a call-center script that begins with the words “I don’t understand how this happened.”
That’s the asymmetry the free-install argument keeps eliding. The cost of an open platform falls hardest on people who never opted into the risk. A market vendor in Jakarta running her business off a payments app doesn’t get a vote in the Hacker News thread, and she can’t roll back a transfer.
What the Right Should Actually Say
The uncomfortable position — the one almost nobody in this fight has taken — is that both halves of the demand are real and they are in tension. Google should be liable for what it ships. Google should also turn apps around in a day. At the scale of the Play catalog you cannot have both, and pretending otherwise is how we arrived at a September deadline nobody likes.
So pick one. If you want faster reviews, you want less vetting, which means accepting that some fraction of installs ends with someone’s rent money gone and nobody to call. Say that out loud, on the record, with your name on it. If you want fewer victims, you want a registry of who built the thing, and a week in the queue is the toll. That is the whole trade.
What you don’t get to do is complain about the queue while insisting the platform meet publisher standards, or defend the hobbyist’s right to install whatever he likes while assuming the fraud victims are somebody else’s constituents. Enforcement starts Sept. 30. The people who notice first will not be the people posting about it.
Sources
- Google Play tightens up rules for Android app developers to require testing, increased app review | TechCrunch
- Android app reviews may slow to over a week due to COVID-19 impacts, Google warns developers | TechCrunch
- Unknown App Developers Expect Longer Android App Review Process – Google
- Google Confirms Timeline for Android Developer Verification
- Google Sets Sept. 30 Deadline for Android Developer Verification in Four Countries
- The Google Play app review process now regularly takes longer than a week