Android's 24-hour sideloading wait hides the bigger change: every developer must register with Google

A campaign site is counting down to 2027, when apps from unregistered developers would stop installing on certified Android devices. The thread argued mostly about the phrase "no opt-out."

In brief

Google's plan requires every Android developer to register centrally, hand over government ID and prove they hold the signing key, even for apps shared outside the Play Store. Power users keep a 9-step escape hatch with a mandatory 24-hour wait.

Commenters split on whether that wait is a fair compromise or the first turn of the screw. One of them brought up tech-support scams.

What the campaign says is changing

Keep Android Open describes a requirement announced by Google in August 2025: every Android developer must register with Google before their software can be installed on any certified device, including apps distributed outside the Play Store. Registration means accepting Google's terms, surrendering government-issued ID, providing evidence of the private signing key, and listing all current and future application identifiers.

The page counts down to the start in 2027 and calls the "advanced flow" for power users a deterrence mechanism. That flow involves enabling Developer Mode, waiting 24 hours, and then allowing an unverified app for 7 days or indefinitely, across 9 steps. The site says over 100,000 people signed its petition and 71 organizations from 23 countries signed an open letter. It is an advocacy page, so its framing is one-sided.

Keep Android Open campaign banner
Keep Android Open campaign banner

The fraud case the page does not engage with

Filippo Valsorda, landed the first big objection:

"This sort of breathless outrage rhetoric would be a lot easier to take seriously if it spent even a minute acknowledging the very real risk to users that this is meant to mitigate: tech support scams where people are walked through installing an app that takes over their phone…"

Replies attacked the premise. Another commenter said many such scams run through AnyDesk, TeamViewer and RustDesk, which are on the Play Store today. Another reader argued that the real problem is not Google doing this, but Google being able to: "The real problem here is not that Google is doing this bad thing. The real problem is that they can do this bad thing."

"Is this really just a 24h cooldown once?"

The side that calls the campaign hyperbolic said the escape hatch exists. The reply from one reply was sarcastic: "This is barely an inconvenience, it's just a 9-step, 24h-long step through a proprietary service." A co-founder of GraphHopper wanted something narrower: let users mark an alternative store such as F-Droid as trusted so the cooldown does not hit every install.

Who is actually exempt

A GrapheneOS moderator answered the question many readers had: GrapheneOS is unaffected, because the enforcing app would not have the privileges to do anything there. For everyone on stock Android, the unresolved point is the one the thread kept returning to: nothing in the plan stops Google from lengthening the wait or removing the flow later.

Get breakdowns like this every day

The top Hacker News stories, unpacked — by email, Telegram, or RSS.

Next story · 4 of 11 Read more
🚀Tech

Kimi K3.1 Pro lands fourth on the Artificial Analysis index, ahead of GPT-6 Astra and Fable 5.1

Moonshot's new open-weight model scores 65.7% on Terminal-Bench 4.0, 0.7 points behind Claude Opus 5.5. The company says full weights arrive by November 4.

★ 731 · 💬 461 · kimi.ai · 2 min