> Are they actively working against PWAs, or are they refusing to spend resources supporting another technology?
What difference does it make? I'm hardly surprised that they won't dedicate engineering resources to tech that threatens their bottom line. But it is a choice, and it's to the detriment of their users and I. For that, it deserves criticism.
We don't actually disagree, our definitions of 'web app' and 'browser' just differ. Personally, I find it absurd to say that PWAs (progressive WEB APPs) cease being web apps when installed, but whatevs.
The important point is that how OSs should (with user consent) grant installed PWAs access to system APIs like notifications. I'm just trying to condemn Apple's preferential treatment of native apps in this regard.
Wow I had no idea, thank you for your well-reasoned critique! I can tell you're very capable of evaluating the merits of complex socio-technological systems. Your wisdom is unparalleled; now I see we all should just keep using X and GitHub.
Installed PWAs still run in a browser, they just don't show you the address bar so it looks and feels like a native app. (UX)
To all your points about a 3rd party intermediary, fair! Such an intermediary can be valuable. But whether we go through an intermediary is orthogonal to whether our app is running in a browser. Native apps can be installed without intermediaries (if your OS isn't evil) and there's no reason you couldn't build an intermediary for web apps.
As for your ProtonMail example... you got pwned. They just handed you some new code to run and you ran it. You could have ran the old code instead. You could have gotten a message saying "would you like to update?". You could compare the hash of content you received with others, tipping you off if you're being targeted.
To that, I imagine you say "but there's no reasonable way to do that stuff!"
And you'd be right. None of that is practical. Why is that? Is it some inherent difference between native code and code running in a sandbox? I think not.
> If you do it like this, then I count it as a mobile app, not a webapp.
This is pretty funny distinction to make. It's hardly a surprise you find web apps inferior if you define them so.
Whether through a store or browser, your computer is downloading code from the internet and executing it. A browser adds cross-platform ease for devs and a sandbox for security at a slight performance cost. A store adds gatekeeping (for better or worse) and a 30% tax. The other differences are UX choices from browser makers and OS designers, nothing more.
There are many reasons to prefer an app, most of which are ways OS makers have crippled web apps for reasons that TOTALLY HAVE NOTHING TO DO with the fact that they get a 30% cut if the user chooses the native app.
Personally, I really like that my feeds aren't getting that level of granular detail. I prefer the explicit control I have with 'Show more like this' and 'Show less like this'.
Trust is subjective! Let's establish trust in each other rather than rely on one-size-fits-all solutions.
Personally, I trust my friends, family, and some public figures and institutions to varying degrees. I want to see social experiences that reflect that.
It's X, not twitter. That system is directly controlled by a single man for his own benefit; we should use the name that reminds us of that.
He openly promotes himself and those that pay him. If you think Musk doesn't have an admin dashboard where he can demote accounts he dislikes and promote his friends, I have some... unkind words for you.
It's about control. Control over your information intake is partial control over you.
We can do so much better than ceding that power to the highest bidder.
That's unbelievably stupid. But then again, so is not renting out the space at the market rate so you can pretend it's worth more than it really is. So... good luck, I guess?
Sucker for epistemology, systems, and languages.
@7hird.dev