Correction: badly implemented web view vs Flutter
A WebView loads those at runtime. So if you were intercept and track all the requests made by a WebView app, you'd see potentially hundreds of assets loading when you make a search query.
A native app doesn't need all those assets, it can make a simple API request to resolve this.
I can imagine a WebView could be bundled with the assets it needs, tho I doubt most people do this.
Yeah this is it. A well integrated web view works very seamlessly. You only notice the ones done badly.
P.S: ok I guess it's because I don't notice them, lol