Starting in 2027, a silent update, nonconsensually pushed by Google, will block every Android app whose developer hasn't registered with Google, signed their contract, paid up, and handed over government ID.
Every app and every device, worldwide, with no opt-out.
This includes apps shared between friends, distributed through F-Droid, built by hobbyists for personal use.
Independent developers, church and community groups, and hobbyists alike will all be frozen out of being able to develop and distribute their software.
Registration requires:
- Paying a fee to Google
- Agreeing to Google's Terms and Conditions
- Surrendering your government-issued identification
- Providing evidence of your private signing key
- Listing all current and all future application identifiers
If a developer does not comply, their apps get silently blocked on every Android device worldwide.
I understand why you didn't mention it, but there is an opt-out: you enable developer mode and wait 24 hours.
As it runs through Google Play Services, it's pretty likely they'll boil the frog and make it even harder in the future. Moving to an open platform is a good idea.
I seem to recall some apps refusing to run if developer mode is enabled. A workaround that means I can no longer use the apps I use every day isn't much of a workaround.
I've considered this before, but the short software support timeframe given by device manufacturers makes this a costly endeavour. I still have a perfectly functional Galaxy Tab S2 9.7, but even the third party ROMs have dropped it. I have a pixel 4a, and although it works beautifully running a supported version of lineage it's very likely that the modem baseband has a significant vulnerability that Google isn't patching. I don't think running banking or crypto wallet software on those devices is any smarter than running it on my daily driver pixel 8.
Or, we're going to have to start choosing banks without apps or with apps that don't have such ridiculous restrictions. Fortunately, at least in the USA there is an abundance of banks and credit unions, so if one of them treats you like this, just move your account over to a different one. I've changed my primary bank in a single day--It's not hard.
It's not just choosing a bank without an app, existing banks have been neglecting their web sites so that some things are only possible with the app even if an alternative exists. I've had that with my bank, and when I called them to report the problem with their web site their "fix" was that yeah, the web site is kinda broken, just use the app instead and it'll work.
As of Android 17, "Developer Mode" consists of an extra options panel that is enabled through a sort of "Easter egg" process. It's not really even a mode. It's simply a bundle of options that are somewhat dangerous or confusing to twiddle. Users don't need to enter this mode for any practical reason, but entering this "mode" doesn't do anything except exposing more options behind one big toggle.
It doesn't affect the phone's security in any way, unless you specifically tweak a security-related option in that panel. It doesn't degrade the device encryption or Google Play Services. I don't see how any app could balk while it's enabled. There are no apps I have that even run differently. I use the same banking apps and all the other things as normal, whether or not this mode is enabled for me.
Is it Developer mode those apps trip on or USB debugging? I've seen several examples of the latter but haven't come across the former yet. I run Google-free Android (14, 15, 16) devices which run the Swedish and Dutch banking and e-ID apps I use on, some of these only work when USB debugging is disabled while others don't care. Some of them complain about Google Play Services not being available but they run nevertheless, that warning is produced by some part of the SDK which gets imported at build time but it does not (yet...) disable anything.
Although USB debugging (ADB) is arguably the main concern, a lot of apps just lazily check for developer mode - meaning they won't boot even if the menu is enabled. It allows stuff like location faking I suppose?
Yes these days it is. It didn't use to be like that.
In the early days of BYOD, all they could do is delete the device if it would be lost. Which was not really a bother to me because I back it up to my own servers anyway, and in that case it would be lost anyway. And they would enforce a few basic things like setting a decent pincode and device encryption.
But lately the MDM and antimalware solutions have become more intrusive. Recently my work's MDM complained about an app I had on the personal side of my phone, something they should have no visibility of. Also they now want to route all the traffic through their VPN to inspect it which was obviously a non-starter.
Android 5 is where capabilities really took off, including the Device Owner profile which has pretty ultimate control over the device -- they've actually done some work to limit what admins could see across profiles in Android 11+
Android 7 is when always-on-vpn was could be enforced by an admin, in 2016.
Once enabled, it stays enabled even after developer mode is turned back off. It's also associated to the Google account (if any) so later device purchase don't have to wait the 24 hours period
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
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].
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.
NackerHughes 1 day ago
Every app and every device, worldwide, with no opt-out.
This includes apps shared between friends, distributed through F-Droid, built by hobbyists for personal use.
Independent developers, church and community groups, and hobbyists alike will all be frozen out of being able to develop and distribute their software.
Registration requires:
- Paying a fee to Google - Agreeing to Google's Terms and Conditions - Surrendering your government-issued identification - Providing evidence of your private signing key - Listing all current and all future application identifiers
If a developer does not comply, their apps get silently blocked on every Android device worldwide.
rjh29 1 day ago
As it runs through Google Play Services, it's pretty likely they'll boil the frog and make it even harder in the future. Moving to an open platform is a good idea.
Volundr 1 day ago
extraextra 1 day ago
rjh29 1 day ago
mikey2410 18 hours ago
ryandrake 1 day ago
abustamam 17 hours ago
thereforegrin 19 hours ago
Either way, what Google plans to do is absolutely crazy.
extraextra 13 hours ago
MrDrMcCoy 12 hours ago
pseudohadamard 21 hours ago
sam_lowry_ 1 day ago
ButlerianJihad 1 day ago
It doesn't affect the phone's security in any way, unless you specifically tweak a security-related option in that panel. It doesn't degrade the device encryption or Google Play Services. I don't see how any app could balk while it's enabled. There are no apps I have that even run differently. I use the same banking apps and all the other things as normal, whether or not this mode is enabled for me.
hagbard_c 1 day ago
rjh29 19 hours ago
j027 1 day ago
I’m not sure if you would have to re-enable it every time to sideload updates or new apps. You can also install via adb with no waiting period.
wolvoleo 1 day ago
And my work doesn't permit it even with byod, it's so annoying. I've stopped running byod for that reason but now I'm stuck with two phones again.
diggernet 1 day ago
wolvoleo 1 day ago
Besides, I would not comply anyway. I would just delete the device.
jasonm23 1 day ago
again IANAL but be careful.
kube-system 1 day ago
wolvoleo 1 day ago
In the early days of BYOD, all they could do is delete the device if it would be lost. Which was not really a bother to me because I back it up to my own servers anyway, and in that case it would be lost anyway. And they would enforce a few basic things like setting a decent pincode and device encryption.
But lately the MDM and antimalware solutions have become more intrusive. Recently my work's MDM complained about an app I had on the personal side of my phone, something they should have no visibility of. Also they now want to route all the traffic through their VPN to inspect it which was obviously a non-starter.
kube-system 1 day ago
Android 7 is when always-on-vpn was could be enforced by an admin, in 2016.
petcat 1 day ago
Is this confirmed? If so, that largely removes my issue with the 24 hour waiting period for enabling/disabling dev mode.
calciphus 1 day ago
kube-system 1 day ago
https://android-developers.googleblog.com/2026/03/android-de...
martheen 1 day ago
ChrisRR 1 day ago
GrantMoyer 1 day ago
[1]: https://web.archive.org/web/20260312134021/https://developer...
[2]: https://web.archive.org/web/20260328133800/https://developer...
gsich 1 day ago
ChrisRR 1 day ago
superkuh 1 day ago
queenkjuul 1 day ago
Such as...?
0xdde 1 day ago
LtWorf 1 day ago
gnabgib 1 day ago
MinorTom 1 day ago
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.