4 ms·

I would agree if you can't do it all on the device itself, the unlocking/sideloading initial warning bypass. The idea would be to prevent those who can barely w

by gabeio 3y ago

I would agree if you can't do it all on the device itself, the unlocking/sideloading initial warning bypass. The idea would be to prevent those who can barely work their phone from "accidentally" enabling sideloading and then downloading some random app off the internet or other app store by accident or being talked through it with a scammer.

kipchak 3y ago
Maybe requiring approval from the iOS account that manages the device, signed in to some other device? I'm imagining something somewhat similar to the "ask to buy" feature for child accounts. That could also help with child or elder accounts if they're managed by someone else holding the keys. Downside is not everyone would have someone to manage their account for them. Having to call into Apple to confirm maybe?
eli 3y ago
Doesn't the Android process still involving tapping 7 times in a row on the build number in the About Device screen? There's definitely ways to create a feature that can't be found accidentally.
- lxgr 3y ago
  You're probably thinking of activating developer mode. Sideloading doesn't (yet) require that, at least not on my Pixel (Android 12).
  - freedomben 3y ago
    Yes that's what they're thinking of (activating developer mode). Sideloading does require several clicks though. First you download the APK, then you "open" the file in the installer. Then you have to allow "installation from unkown sources," then allow for the app that you downloaded it with (for me that's usually firefox, but for most it's probably Chrome), then you can install it.
lxgr 3y ago
Sure, vetting apps can be quite efficient at preventing malware. But if a sideloaded app can do significantly more harm than just visiting a malicious website (which a scammer can already direct a victim to do), maybe the OS is providing too dangerous (or coarsely-controllable) permissions via its APIs?

by gabeio 3y ago

kipchak 3y ago

Maybe requiring approval from the iOS account that manages the device, signed in to some other device? I'm imagining something somewhat similar to the "ask to buy" feature for child accounts. That could also help with child or elder accounts if they're managed by someone else holding the keys. Downside is not everyone would have someone to manage their account for them. Having to call into Apple to confirm maybe?

eli 3y ago

Doesn't the Android process still involving tapping 7 times in a row on the build number in the About Device screen? There's definitely ways to create a feature that can't be found accidentally.

lxgr 3y ago
You're probably thinking of activating developer mode. Sideloading doesn't (yet) require that, at least not on my Pixel (Android 12).
- freedomben 3y ago
  Yes that's what they're thinking of (activating developer mode). Sideloading does require several clicks though. First you download the APK, then you "open" the file in the installer. Then you have to allow "installation from unkown sources," then allow for the app that you downloaded it with (for me that's usually firefox, but for most it's probably Chrome), then you can install it.

lxgr 3y ago

Sure, vetting apps can be quite efficient at preventing malware. But if a sideloaded app can do significantly more harm than just visiting a malicious website (which a scammer can already direct a victim to do), maybe the OS is providing too dangerous (or coarsely-controllable) permissions via its APIs?