Hacker News Reader

Comment by ChrisRR | Hacker News Reader

This keeps getting missed out every time it's reported. I can't figure out whether people genuinely don't know, or they're trying to push a narrative that this is worse than it is

View on HN

Firstly, TFA has a bright red banner describing the opt-out mechanism. It's probably the second most attention-grabbing element on the page, after the countdown. Secondly, initially Google didn't mention any plans for an opt-out at all[1]. That was was only ceded after pushback[2].

[1]: https://web.archive.org/web/20260312134021/https://developer...

[2]: https://web.archive.org/web/20260328133800/https://developer...

Because it's a workaround on Googles control. Next year it will be a week, then a month, then never again.

It's under google's control because it's a Play Protect feature. It doesn't exist on non Play Protect devices

You say, "Play Protect" as if it is a thing that users can choose to avoid. Or as if it justifies the behavior. I don't think either of those is true.

>non Play Protect devices

Such as...?

It's clearly stated and expanded upon in this reporting.

Because apparently banking apps stop working if you do this.

They do not. If you /root/ your device play-protect, and apps that depend on it (many banking, security and 2fa apps) decide you're compromised. If you turn on developer mode - nothing happens... except you get menu options for a developer and can upload your APKs (or any others if you're a scofflaw)

There are certainly apps that stop working (at least in significant part) only because of Developer Mode, on otherwise stock Android, no root, Pixel phone.

Though the only example I’ve encountered is the SumUp Business App’s Tap To Pay feature. If you use e.g. Geto to hide (automatically disable and later re-enable) the developer options, it works fine.

Reply on news.ycombinator.com