> Before judging people for their decisions it's worth understanding why they make them. I do understand. I understand it's infinitely cheaper to build a shitt

> Before judging people for their decisions it's worth understanding why they make them. I do understand. I understand it's infinitely cheaper to build a shitty webapp and port it to every platform. I know exactly why this stuff is so ubiquitous. Hell, I've even tried it over a few weekends here and there. There was a time I was looking to get into React simply because everyone and their mother is using it for all the reasons you've outlined here. Eventually though I found a job where a native app is much preferred for exactly the reasons you outline here: It runs better, and our leadership is one that's prepared to lay out a chunk of change to have software they're proud to show off and sell. In short: I know exactly what the tradeoffs are and why they're made. Doesn't mean I'm not going to judge them for it. It's great web tooling but when used this way it results in mediocre garbage applications that are magnitudes larger than they need to be, more often than not by some combination of developers or management that fundamentally don't care that it runs and feels like shit, and that tells me something about their long term product viability.