3 ms·
And yet I bet you often use "native apps" that are really just repackaged web views put into the app store. Without even knowing it. > So how can you both wan
by BackBlast 4y ago
And yet I bet you often use "native apps" that are really just repackaged web views put into the app store. Without even knowing it.
> So how can you both want web apps to have more native capabilities and want to avoid apps because they have too many native capabilities?
You seem to totally miss my point.
A native application can do things like sniff local bluetooth devices, track your GPS location, snoop your clipboard. Something a web app can't, because the web APIs have been much more carefully vetted for privacy.
It's this fine grained user tracking that is behind the push towards using the app store. Companies want to know everything your doing, where you are, etc etc. That's much more difficult through a web API as compared to native APIs. This is why they will intentionally cripple their mobile sites and push to use their apps. They want native API level user tracking.
- dmitriid 4y ago> Something a web app can't, because the web APIs have been much more carefully vetted for privacy. Depends. Chrome for example doesn't vet these as much as the other browsers do. Someone in a sibling thread linked to this tweet from a Mozilla engineer: https://twitter.com/denschub/status/1582730985778556931 https://twitter.com/denschub/status/1582730985778556931 "Just a day after shipping an impl to Firefox Nightly, this is the first discovered case of WebMIDI-fingerprinting... Chrome still allows web developers to enumerate attached MIDI devices without user consent or even a notification, btw."