Personally I'm obsessed with efficiency and performance - and platform specific native toolkits are rarely beaten at that. I really don't like seeing wasting many megabytes of (V)RAM and long seconds of CPU time just to display a marquee...

▲

perilunar 2 days ago | parent [-]

True, but it goes both ways.

My bank's mobile app is 200 MB. The website is 10 MB, but most of that is wasted — it could realistically be built in less than a 1 MB. Start-up times and performance are similar.

Why should I lose/waste 200 MB for something that i have to be online to use anyway?

	▲	not_your_vase 2 days ago \| parent [-]
		On one hand, yes, I agree: duplicating the full functionality of a website for the sake of having an app is far from being ideal. On the other hand, I also believe that this 200 MB comes mainly from 2 sources: bad engineering from the application developer, and bad engineering from the platform developer. These are not toolkit dependent, however. Bad engineering will create bad products, regardless of the tools used, even when some tools are harder to misuse to create bad products.