3 ms·

Reasonable, but I can't help thinking that the expectation here is that most users won't do anything about the restriction - the net effect is to discourage dev

Reasonable, but I can't help thinking that the expectation here is that most users won't do anything about the restriction - the net effect is to discourage developers from sideloading altogether.

jeroenhd 3y ago
Most apps don't need these restrictions. It's a bit annoying if you're installing some kind of third party accessibility service, but I can't remember when I last installed an app that needed notification access. These permissions are rarely needed and often abused by stalkerware to do things like read messages and screen contents. If they keep the override button in the settings, I honestly don't mind the change, as long as Google Play and vendor app stores aren't exempted. If you're going to make things difficult for developers, make them difficult for your own developers as well. I'm sure the DMA will affect this feature for EU models, or Google will be subjected to a chunky fine and forced to change it the moment the first signs of abuse pop up.
- kuschku 3y ago
  Google has restricted more and more functionality to their apps only. System signed, that is. The only way for e.g. KDE connect to continue working properly today is using adb, three hacky permissions, accessibility access and notification access. It's just going to get worse. But if I had a Chromebook, Google would give me the same functionality for free.
  - jeroenhd 3y ago
    Yeah, it's rather annoying that I needed to root my phone to fix KDE Connect's clipboard access. That's the only workaround I've needed for years, though. The (relatively recent) changes Google made to the app store API made my life a whole lot easier now that F-Droid can actually update packages without root access. As long as the existing manual overrides (going through the settings and toggling the permission) still exists, I don't see much of a problem.

Reasonable, but I can't help thinking that the expectation here is that most users won't do anything about the restriction - the net effect is to discourage developers from sideloading altogether.

jeroenhd 3y ago

Most apps don't need these restrictions. It's a bit annoying if you're installing some kind of third party accessibility service, but I can't remember when I last installed an app that needed notification access. These permissions are rarely needed and often abused by stalkerware to do things like read messages and screen contents. If they keep the override button in the settings, I honestly don't mind the change, as long as Google Play and vendor app stores aren't exempted. If you're going to make things difficult for developers, make them difficult for your own developers as well. I'm sure the DMA will affect this feature for EU models, or Google will be subjected to a chunky fine and forced to change it the moment the first signs of abuse pop up.

kuschku 3y ago
Google has restricted more and more functionality to their apps only. System signed, that is. The only way for e.g. KDE connect to continue working properly today is using adb, three hacky permissions, accessibility access and notification access. It's just going to get worse. But if I had a Chromebook, Google would give me the same functionality for free.
- jeroenhd 3y ago
  Yeah, it's rather annoying that I needed to root my phone to fix KDE Connect's clipboard access. That's the only workaround I've needed for years, though. The (relatively recent) changes Google made to the app store API made my life a whole lot easier now that F-Droid can actually update packages without root access. As long as the existing manual overrides (going through the settings and toggling the permission) still exists, I don't see much of a problem.