You are ignoring all of the advantages of writing a web client. Are you really saying that distributing a native app for every platform is better than writing something that uses the browser?

▲

skeezyboy 4 days ago | parent [-]

> You are ignoring all of the advantages of writing a web client. What are they exactly? Youve already mentioned distribution, but what else?

▲

szajbus 4 days ago | parent [-]

Well, distribution is the killer feature. More, it's inherent property of the platform (web).

Web devs are in full control of their whole stack (excluding the browser where you occasionally need to account for incompatibilities), have to maintain only one version of the app (no upgrade needed on client-side), are not constrained by the platform owner's policies (app store tax).

Yes, it's more limited than native technologies in other ways, so it's not an answer for every problem.

	▲	skeezyboy 4 days ago \| parent [-]
		> have to maintain only one version of the app (no upgrade needed on client-side) Except what happens when it doesnt run the same on Firefox as it does on Chrome? Or what about when Edge is run on Win7 and youre app doesnt render correctly? Yes you only code one version of an app, but you are still obliged to consider the underlying platform - which is exactly compile once, run anywhere is it? its more like compile once but make sure you test it on all the different browser/OS combos before you do. Distribution aside, its more likely you only know web languages and THATs why youre coding your project on the web stack. Pick the best tool for the job