Native Apps Should Be Avoided Whenever Possible
nooneshappy.com
Native Apps Should Be Avoided Whenever Possible
1–10 of 33 posts
Re: Native Apps Should Be Avoided Whenever Possible
#2I thought hotkeys were hard to do right in a web app too? Yet the article completely misses that.
Re: Native Apps Should Be Avoided Whenever Possible
#3I thought hotkeys were hard to do right in a web app too? Yet the article completely misses that.
Some hotkeys are hard or unusable (e.g. some of the ones that conflict with the browser itself, like esc and ctrl-l and ctrl-t/w/q). Plenty work just fine.
Re: Native Apps Should Be Avoided Whenever Possible
#4I thought hotkeys were hard to do right in a web app too? Yet the article completely misses that.
This article is about mobile apps.
Re: Native Apps Should Be Avoided Whenever Possible
#5Unfortunately agreed. Browser sandboxing is usually quite a lot better than apps. The table they provide is rather biased though, many of the things they show in PWA's favor are only true in the most trivial sense, and are easily worked around, both technically and widely used in practice.
Also browsers can use extensions to modify pages, and that opens up SO many possibilities. And bookmarks. And history. And tabs. And search. Most apps never implement any of these, much less all.
I do wish we had a more widely supported system for push notifications though. WebPush exists and broadly works quite well, but provides nowhere near the control, reliability, and observability that native apps do. ...which is a good thing when you don't want them, but crippling when you do, and it contributes to the general "few sites do it at all" problem. E.g. Slack doesn't use it, nor does Zulip (particularly painful because their mobile web UI is much better than their app), nor most chat apps in general even though they're an ideal scenario.
Re: Native Apps Should Be Avoided Whenever Possible
#6Native applications should be insisted upon. Web applications are not under the control of the users in any form and what they do can be changed without the users input even as the user is in the middle of a session of using the software. Website applications can also just dissapear and often do. Additionally any given website 'app' will be loading unknown executable code from random arbitrary sites. Usually spyware. This kind of thing is far more easily detected and justifiably blocked when you run a native application. A native application installed on a computer is yours to use as is till you decide to change it or allow it to change.
- Write emails to companies that provide desired services that way suggesting they make an actual application.
- Revoke all JS execution permissions from all domains that are not verifiably in control of only the company running that web app.
- Audit your use cases and try to find native applications that can fulfill them instead of web apps.
- Try not to use web apps on domains that you have no control of.
- Treat every domain trying to get you to execute random code like you would receiving a .exe in the email from a similarly unknown person or address.
The idea that most native applications collect more information than web apps is false. It is only true in the very restricted domain of smartphones. It is obvious to everyone in practice and in law that users of smartphones do not own them or control them and will not be allowed to. The problem is the smartphone, not native applications. Giving up even more control and ceding everything to a remote web service, will make this worse, not better.
And yes, copying this article's structure for my response is intentional parody.
Re: Native Apps Should Be Avoided Whenever Possible
#7Good native apps exist, although rare and getting more so, and for a lot of workflows are better than websites.
That said, all the privacy reasons listed apply just as much to websites as they do apps.
I have to disable noscript a lot when it comes time to fill out what is glorified for a lot of day to day transactions. Especially anything involving a credit card these days.
Re: Native Apps Should Be Avoided Whenever Possible
#8I love using the Twitter web app over the native app. And whenever I think of a product, I think of how I can build a fully usable web app (even when primary access is via phone).
Re: Native Apps Should Be Avoided Whenever Possible
#9Native applications should be insisted upon. Web applications are not under the control of the users in any form and what they do can be changed without the users input even as the user is in the middle of a session of using the software. Website applications can also just dissapear and often do. Additionally any given website 'app' will be loading unknown executable code from random arbitrary sites. Usually spyware.…
I get the feeling this article is just about mobile apps, which you clearly think is an irremediable platform for some reason. Given ths choice between native mobile apps, locked down by two massive tech companies and web apps, I'll take the latter.
Re: Native Apps Should Be Avoided Whenever Possible
#10Native applications should be insisted upon. Web applications are not under the control of the users in any form and what they do can be changed without the users input even as the user is in the middle of a session of using the software. Website applications can also just dissapear and often do. Additionally any given website 'app' will be loading unknown executable code from random arbitrary sites. Usually spyware.…
[deleted]