3 ms·
With native apps, it's at least possible to preserve some semblance of privacy and control over your own data. Granted, most native apps are just thin UI layers
by ThJ 8y ago
With native apps, it's at least possible to preserve some semblance of privacy and control over your own data. Granted, most native apps are just thin UI layers on top of a REST API, but certain things aren't possible to implement like that without putting sensitive data in the cliud. OTP generators and password managers, for example. The native app data sandbox offers a level of security not possible in a webapp.
- Jyaif 8y ago> The native app data sandbox offers a level of security not possible in a webapp. I call BS :-) Can you share an example of something that can be done more securely in a native app than in a webapp? On iOS the opposite is true: apps can't spawn processes, so you can't isolate your native code, so if some part of your app is compromised the whole app is compromised. With websites you can have iframes on different domains which (assuming your browser is decent) will run in different processes.
- SahAssar 8y agoI don't get this at all. You seem to allude that the "native app data sandbox" gives some sort of security or privacy not possible in a webapp, but webapps are restricted by default, able to run without being installed on your system and are run in a much stricter sandbox than a native app is. If you value privacy and security I don't see anything that would favor a native app over a webapp. I do understand the performance and native integration arguments for a native app, but saying a native app by definition offers more privacy or security seems odd.
- craftyguy 8y ago'web apps' can be even further restricted by using browser plugins (e.g. privacy badger, noscript, ublock origin, etc). You don't get that kind of control with native mobile apps unless you have access to the source code and can modify/build it.