1184
Language
(lemmy.blahaj.zone)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Aug 2025
1184 points (100.0% liked)
Microblog Memes
9000 readers
2289 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
founded 2 years ago
MODERATORS
Let me answer your question with a question: How many things do you do with your phone that aren't also able to be accomplished with a website already? I'd be willing to bet that the answer is in the single digits. And for most of those, that limitation is likely to be entirely arbitrary, instituted by a developer as an anti-consumer form of lock-in.
Delivering application-like experiences via the web allows users to make accessibility changes to that experience without the developer needing to support it explicitly. It also allows users to implement plugins that extend and improve their experience, by removing undesirable content or adding functionality that you haven't provided. And because browsers are built on open standards, there's no longer any device ecosystem lock-in; I should be able to access all of the websites I want to from any browser on any device. Users could even build their own bespoke applications, without the need to enable a developer mode on their phone or get a certification from a megacorp.
And because downloadable and cacheable progressive web apps are a thing, as well as local storage options for browsers, the experience for an end-user of a browser-only phone wouldn't need to be any different in low-signal or high-latency situations.
The web is a mature and proven platform for delivering arbitrary code and data, plugins make the web more accessible and easier to use, and web standards make the world more open. It's not a perfect platform, of course, but it's the one we've got; I think making it the default rather than the fallback for the devices most people use more than any other would be a great boon for the world at large.
This is kinda begging the question imo. Phones are terrible anti-user devices, so I can't do the things I'd like to do with it that I can't also accomplish on a website. Wasn't that kinda the problem that was initially stated in the OP?
Almost all of this would be equally possible if the phone wasn't just a platform for a browser. I actually think a browser model limits a lot of what you say here, and browsers definitely have ecosystem lock-in problems: what Google says essentially goes these days. The browser isn't the great liberator of phones imo.
I don't hate browsers; a lot of what you said is true and great for users with respect to browsers. I do however think it's a weird way to try to fix the phone ecosystem by replacing a restrictive sandbox with a restrictive sandbox that also ties you to a really terrible development ecosystem.