3 ms·
So what's the advantage? It looks like all downside to me. From an app developer standpoint, I'd have to deal with multiple platforms and distributors. From a u
by sp332 9y ago
So what's the advantage? It looks like all downside to me. From an app developer standpoint, I'd have to deal with multiple platforms and distributors. From a user standpoint, I'd have to hope the developer made the app available for my platform, and go through some install process before I got to use it. This way, it loads (with a cold cache) in half a second.
- pmoriarty 9y agoThe advantage for the user is that they don't have to open up their browser, computer, or mobile device to being exploited, spied upon, or advertised-to by an ocean of javascript garbage on the web. Their web browsing experience will be tremendously improved and streamlined. If they want a particular app, they can click to download and run it explicitly. It's not a big deal. From the developer and business standpoint, it might be a disadvantage not to have something like javascript available to use. It's more inconvenient, and now they can't spy on, advertise to, or track the user as easily. But I'm for a user-centric web, not a business-centric or developer-centric web.
- sp332 9y agoIf you click the link I posted above, you will get a permissions dialog that asks to access your microphone. You can say no upfront, or revoke permission at any time. It's not open to spying. Edit: to be specific, it's a lot easier to allow access temporarily in a browser than it is using the Android permissions system. Not sure about Apple but I'd bet it's about the same as Android.
- pmoriarty 9y agoJust because you've given permission to an app to access, say, your microphone, doesn't mean that it's not spying on you. That guitar-tuning app that was mentioned earlier might well be spying on you using the microphone it got access to. The guitar-tuning app is a special case that actually has a legitimate need to use a microphone, but I've seen countless apps that need all sorts of permissions that they don't legitimately need. Like calculator apps that need permission to access my microphone or contacts. The sad thing is that most users will just click through a popup asking for permissions, just like they do the "Run as administrator" popups on Windows. Such things are just not very effective safeguards. Even with limited permissions, allowing JS apps to run on my system opens me up to all sorts of JS exploits, tracking, and advertising that just aren't possible or much more difficult with static HTML (which has a much smaller attack surface than JS anyway).
- sp332 9y agoIn response to the tuner app, you said "make it a native app". The alternatives we're discussing are not static HTML vs JS, it's native apps vs web apps. Both kinds of apps can spy on you, both kinds can ask for tons of permissions they don't need, both have exploits, tracking, and advertising.
- jpttsn 9y agoI think the argument is that if the guitar tuner is a native app, there’s one less reason for the user to keep JavaScript enabled in their browser.
- always_good 9y agoI don't get it. Native apps are even worse. At least websites are ephemeral and you can pop open a dev console and inspect/block the traffic. Native apps ask you for permissions and then can access those features for as long as they're installed on your phone, often in the background. Ever see what kind of data Google has on the average Android user? It knows their exact route through town every day. It's crazy. Maybe the world would be a better place if 1999 MapQuest was still the most advanced app on the internet. But your fixation on Javascript in this thread sounds out of touch with the more inconvenient truths of modern technology, probably because Javascript happens to be the one you can live without.
- superkuh 9y agoNative apps are static. You know what is in them from version to version. Javascript changes every time you pull it down and even changes as you use it.
- aaron-lebo 9y agoGood progressive web apps are user friendly. I can't do anything about bad devs, but you've already decided that the path we are on (and will continue to be on because we're not getting rid of JS) is absolutely bad. It's not 1999 anymore. We've gotta figure out how to do things right with today's tech, not a nostalgic view of how things were, because we're never going back.
- dingo_bat 9y ago> I'd have to deal with multiple platforms It's a mistake to assume you don't have to do that for PWAs.