No, I mean slower to run. It takes way too long for widget objects to be created, and you can only do it on the UI Thread, and you have to make most of your widgets when the app opens (otherwise there's nothing to see).
It was also slower to write for me, but I've never had a good time understanding UI toolkits, so I assume that's my own character flaw.
Erm. There's no way the web is faster than Android's native widgets or Flutter's. Your complaint about the UI thread makes no sense for a start - the web only has a UI thread.
I wish you were right. But for a reasonably simple (in my mind) weather UI, constructing the native Widgets on a cold start takes long enough that you get warnings for too much activity on the UI thread. But you can't build Widgets off the UI thread to get parallelism like you would do for other things that are slow, because Widgets have to be built on the UI thread if you want to show them.
A similar HTML layout shows up a ton faster in Chrome or a webview.
It was also slower to write for me, but I've never had a good time understanding UI toolkits, so I assume that's my own character flaw.