Because they end up migrating more and more functionality to their web side? Deprecating desktop or mobile app functionality or entirely.
So you end up with piss poor “web apps” that half the time require a specific browser to work remotely well and have kludged “offline” modes that break every other day.
Do not want. I know I’m probably in the minority but it’s damned irritating. The UX on most is atrocious and you have to deal with a complete hodgepodge of interface styles and ideas and designs and also hope your browser keeps running smoothly after trying to use multiple more advanced webapps simultaneously.
Oh, but all these advancements on wasm and all will continue improving performance and fixing problems!!!
… you mean stuff that was already solved with native programs? “But you can work on your stuff from anywhere with just an account!”
Oh, like a native app’s data synchronization?
But but…
It would be nice if we had both and both were equals. But that isn’t the case. It won’t be the case. And most companies see this as a wonderful way to vendor lock in even more than before and implement more and more IAP and subscription crap.
I’m obviously not talking about programs who’s primary function is some sort of network usage.
But if it’s a desktop app that does desktop things but still requires a network connection for a completely inane reason I don’t use it. I hate that shit. That’s the same sort of awful as a “webapp”.
And I knew people would start with the “that’s actually no different than desktop programs requiring specific versions of the apps or toolkit. Therefore your complaints are invalid.”
Difference here is I can keep my program. And use it via emulation or virtualization if necessary.
Webapps are another trend towards a “you own nothing. You rent everything.” Economy with computer software.
It’s shit.
And I’ll add that webapps /have/ their place. And I obviously use some.
My big gripe is, like with everything with humans, there’s always this push to extremes. It’s not “let’s use webapps where they make sense” it’s “let’s try to convince everyone webapps are perfect and we need everything to be that!!” cough ChromeOS trash
So if it would stay reasonable where traditional and web and even hybrids can coexist that’s fine.
It won’t. It never does. And I am not looking forward to the inevitable future of Always Connected being a requirement for literally everything. And you have to pay monthly fees for every little thing. And you lose access to your supposed data of you let you account lapse briefly. Blah blah.
It’s already happening and if you claim otherwise you are being willfully blind.
But people love the touted “convenience” and eat it up. And poo poo naysayers.
When it is a desktop or even a mobile app I as the end user have a level of control over my environment that I don't with a webapp. In addition, my interface doesn't change at the whim of the company or developer.
So you end up with piss poor “web apps” that half the time require a specific browser to work remotely well and have kludged “offline” modes that break every other day.
Do not want. I know I’m probably in the minority but it’s damned irritating. The UX on most is atrocious and you have to deal with a complete hodgepodge of interface styles and ideas and designs and also hope your browser keeps running smoothly after trying to use multiple more advanced webapps simultaneously.
Oh, but all these advancements on wasm and all will continue improving performance and fixing problems!!!
… you mean stuff that was already solved with native programs? “But you can work on your stuff from anywhere with just an account!”
Oh, like a native app’s data synchronization?
But but…
It would be nice if we had both and both were equals. But that isn’t the case. It won’t be the case. And most companies see this as a wonderful way to vendor lock in even more than before and implement more and more IAP and subscription crap.
No thanks.