Yeah, exactly. People should recognize that apps are their own form of walled gardens, or maybe they are the walls of gardens, choose your analogy.
When something can be done in a web browser, then you can access it all sorts of ways, from all different browsers. (Ideally)
But accessing via app is accepting that single interface.
Sometimes there is no real choice, and functionality just doesn't work with a browser, and that's fine. The plants in that walled garden are special. Again, choose your analogy :)
But when a browser interface can handle it, let's choose that path, not an app.
@z428
Yeah, everything-in-a-browser has been a longtime coming but recent development as browser tech has improved over generations, both on the frontend and backend.
Browsers have so much more capability now, and heck, so often an app is simply an embedded web browser with handcuffs.
I actually had @jwz in mind with this post of his:
https://www.jwz.org/blog/2022/11/psa-do-not-use-services-that-hate-the-internet/
Funnily enough, that I could share a link from a browser to the post illustrates his point.
@volkris Fully agree at least on the last part. But am a bit torn about that browser predominance and the idea of more and more turning a browser from what it ought to be (a display vehicle for linked documents containing mostly text) into a rich client application platform (which it doesn't seem to be particularly good at, from some perspectives). I have my issues with both perspectives, but safe to say I'd like to use services that leave me with choosing appropriate tools to access them, rather than forcing me down one particular road.🙂
@petrescatraian