4 ms·
Bluetooth does have privacy issues, but again, that's no different than a native app. If I install a native app, it doesn't get free reign over BT or any other
by hundchenkatze 6y ago
Bluetooth does have privacy issues, but again, that's no different than a native app. If I install a native app, it doesn't get free reign over BT or any other device feature. In order to use any hardware feature a native app has to request permission to use it.
I don't understand how a web app is any different in that regard. A PWA could specify the features it wants to use in the manifest.json just like a native app does with the Info.plist. Then iOS could prompt the user in the exact same way. If the iOS permission system isn't a good design (I think it is) then why do they keep using it and expanding it for native apps but not use it for PWAs.
- zepto 6y agoApple has the ability to remove apps which abuse their permission requests, e.g. by lying to the user about what they are going to use the permission for. Not so with websites. The bar for including new functionality in browsers is way higher than it is for native apis because there is no way to police abuse.
- hundchenkatze 6y agoThere's nothing stopping apple from blocking app installs from specific domains/subdomains.
- zapzupnz 6y agoBlocking on a per-domain basis is nothing short of an eternal game of cat and mouse.