Unless mobile vendors put up artificial barriers on functionality of web apps (Apple).
At a certain hardware level, UX is not perceptibly different between native and Web based, yet development much easier with cross platform target
IMHO, replacing something != proving something. We may have replaced desktop apps with browser-based apps somewhere, but that does not prove anything. I'm looking at a lot of professional software, that just won't perform as a browser app (or work at all) in the near future. And then I look at a lot of crap browser-based software (like MS Teams) that makes me wonder whether this was actually an advancement, because it absolutely does not feel like it. It's UX is just miserable and so slow.
It's enough proof for me, at least.
Native apps continue to exist for areas where browser APIs aren't sufficient yet, that's true. But those will get replaced once a sufficient API supports it
Just because business see that it's cheaper does not make it the better option.
It could also be said that it's a feature that the app does not 100% follow the native UI as the experience will be the same irrespective of which OS you are on.
Is it a feature, that MS Teams (as a default setting) does not use native notifications on OS X? As a user, I have to disable two notifications now, because one does ignore the system setting. I don't know how to sell that "feature"... Imagine having many apps with each having it's own notification setting, layout and appereance.. That's hardly an improvement to the status quo.
Web apps are dreadful, regularly lock up, and are an active step back in computing. But hey, if your startup can spew out a shitty app much faster, good for you.
There’s factors occluding this though I think-the JS/web stack has had millions of dollars of investment thrown at it by parties with a vested interest in seeing it succeed, so a lot of UX issues and friction points have been smoothed over as much as possible.
The wider native UI ecosystem hasn’t had the same investment, so I’m not surprised it’s superficially “easier” for devs to thrash out a UI with web tooling. Doesn’t mean the resulting application is actually any better though.
I actually prefer to run MS Teams in a browser tab instead of installing it to my computer. Same with Slack or Zoom. I'm not losing much since their core functionality relies on an internet connection. Full-blooded browsers are also more likely to stay up to date than the bundled Chromium build, and I can enjoy the peace of mind from a modern browser sandbox.
They did? I mean, I'm forced to use crap browser apps for work (i.e. Slack), but it's very early to be declaring the desktop app dead.
> At a certain hardware level, UX is not perceptibly different between native and Web based ...
Hard disagree.
> ... yet development much easier with cross platform target
Well, yes. There we can finally agree. It's all about cost; hiring cheap web developers to churn out something acceptable, if never good.
Software developers and PM's can generally get by with a browser, but woah boy good luck getting the finance world off of desktop Excel/Bloomberg (as the most prominent example of an immovable force against browser apps).
The only people who seem to think this is any good appear to be in their 20's and not actually experienced with desktop apps.
So it’s just a matter of time until this swing of the pendulum is complete. Then we can rediscover Qt and Tcl/Tk.
Let me know when the power is there for the desktops. My MacBook M1 Pro chokes a lot due to running Teams, Slack, VS Code all wanting to be desktop webapps and are highly inefficient.
I have to use a proper desktop to get everything running smoothly together.
There's a reason software trends towards higher level, less performant abstractions over time. The takes about chrome being a memory hog or electron being inherently slow are very tired at this point
It's just demonstrates a very poor grasp of what actually matters in the world. And the performance gap is greatly exaggerated.
Most people would agree VS Code is very snappy, and it's written in JS and browser based. There's no inherent reason they have to be slow. And we don't double the RAM in computers every few years to leave it unused
I understand why developers like Electron, but like everything it's a tradeoff.
> > Electron apps are slower today than native apps were 10 years ago, despite computers getting faster and available RAM on my machine quadrupling.
Desktop software today seems to be slower than desktop software even 20 years ago, when RAM and hard disks not only had less capacity, but were also slower just as CPUs were slower. As an industry, we have sacrificed so much at the holy altar of Developer Productivity.
Very much this but management are not requesting Electron. They see that JavaScript developers are cheap and plentiful, and JavaScript devs want to use JavaScript, even if it isn't a desktop language.
What..? Many common managed platforms are also garbage collected - .NET and Java, for example.
If I assume you misspoke with “managed” it still is untrue that garbage collection means “slower” because “slower” says nothing about whether you are measuring throughout or latency.
On a point of clarity.
Who is we?
I don't want my browser taking up 14gigs of my 16gigs just to watch a cat meme...thanks.
I would like my experience to be improved and elevated while using less resources. Efficiency.
> It's just demonstrates a very poor grasp of what actually matters in the world.
I find this particular statement...lacks any modicum of humility. One might say it ventures into dangerously callous.
Put simply, outside first world economies, most of humanity does not earn enough money to buy a new macbook pro/ Dell XPS every 2 years nor have access to fast internet...relying on crappy broadband instead.
Even those people deserve efficient software that does its utmost to not hog the little resources so they can get things done yes?
So most of the time people are not discussing the same application experience. VS Code with nothing installed isn't that bad, once you start actually using it for code then performance drops off a cliff.
I'm not sure whether it's that black and white. If you've worked on both platforms you know how much of a different beast mobile is, it's a lot less forgiving in a lot of aspects. The use cases and interaction model is very different.