I'm also aware of those, that's exactly what we're using in my company. It's a power hog, so much so that I had to change my laptop to run the SPA properly. The local experience is absolutely terrible since it has to disable the bundling to use hot reload (at least that's what I guess is happening) and each browser reload takes >1min to load.

Then there's the complexity of the caching in continuous deployment, we literally have a custom metabase dashboard to make sure the caching isn't too bad and lasts a few days.

Then the default config doesn't scale either as you can guess and we have our own.

There's a reason I have this opinion, I know what I'm taking about, I've been using all those tools and they add a lot of complexity to your app.

The reason it works on an native app is because loading a dynamic library is essentially free, it's just stored alongside the binary.