481–490 of 599 posts
While I sympathize with the author, and feel the same way, I think Apple/Google have some blame here. They make certain simple things only possible in the apps, because the APIs are not exposed via the web. Notifications is a big obvious one. Not sure if they've changed it since I last looked into it, but having an app installed was the only way to send a notification to someone for a long time.
While I sympathize with the author, and feel the same way, I think Apple/Google have some blame here. They make certain simple things only possible in the apps, because the APIs are not exposed via the web. Notifications is a big obvious one. Not sure if they've changed it since I last looked into it, but having an app installed was the only way to send a notification to someone for a long time.
How are you going to get a push notification from a site after the tab is closed?
Earlier quoted context omitted.
It is silly but you have to meet customers where they are. I think the problem is also that PWAs don't have any discoverability, and no standardization. I did some consulting work for a company that had a PWA. They had a 200-line long react component that was intended to determine what modal to show the user depending on what web browser and OS they were using to instruct them how to install PWA depending on the comb…
I actually don't know what you mean by PWA. Is that a mobile web site? And by installing it, do you mean installing a link to it on a phone's launcher?
Earlier quoted context omitted.
Not a single platform require permission from each individual contact in your adress book to access them and that is the real problem.
GrapheneOS allows for this. It's called Contacts Scope.
Earlier quoted context omitted.
Pointers are famously difficult to learn and reason about even though the basic principles are simple. Programming in a style that requires direct manipulation of pointers when it's not actually necessary is usually regarded as unwise because it's so hard to get right.
Pointers aren't hard, it's C/C++ that make them complicated. Addresses and indirection in any assembly language are simple and straightforward, easy and even intuitive once you start actually writing programs.
What most people dont get: Most of folks on HN here are much older than todays "first customers" of 16y/17/18 For them: The "Smartphone is the internet", while for most of us the "Smartphone is an extension of the internet from our desktops" that we were used to (remember the years before dot com bubble, saying: "I will be down in the basement at the computer to surf on the net little bit" ? :-) But today, the very f…
Yes! My zoomer girlfriend tuned her phone to be work ready. Unless she has to, she'd be working on the phone. I would never do that. To me the phone is uncomfortable. To her, it's the small, comfortable thing she knows better than the computer.
What most people dont get: Most of folks on HN here are much older than todays "first customers" of 16y/17/18 For them: The "Smartphone is the internet", while for most of us the "Smartphone is an extension of the internet from our desktops" that we were used to (remember the years before dot com bubble, saying: "I will be down in the basement at the computer to surf on the net little bit" ? :-) But today, the very f…
My company corporate card requires an app because it has an Authenticator to access the website. I tried the ole “but I only have a flip phone” and they said there was no other option. The bastards forced my hand.
This standard of every random website having an app and poorly managing cache and storage needs to stop. My mom can't begin to even understand how to fix it, and worse, she didn't even recognize half the apps I mentioned to her, which probably means she mindlessly clicked install on a bunch of random websites.
We do not need more app bloat on our devices, especially if they are just thin wrappers over your web app.
Earlier quoted context omitted.
Apps can download code too, and often do
Well the idea is that the client should be open source, and audited. If you run a proprietary app, you have to blindly trust it (just like if you access a webapp). In terms of security, the best is an open source app, IMO.
The browser tends to be safer because it has a stronger sandbox than native apps on a mobile OS. It's meant to be able to run potentially malicious code with a very limited blast radius.