[kllrnohj]

My experience with Flutter was it was only really suitable for UI code. Lack of efficient parallelisms among other things really kills the ability to do non-trivial work. If you happen to be able to stay in Flutter's async APIs then the illusion holds up OK, but otherwise you have to just kick over to native code to do anything interesting. At which point the multi-platform story obviously falls apart.

It's really not unlike the web platform. If you're in the semi-narrowly supported "good" path it's great, but if you hit the limits of things you're pretty much immediately out of options.

And also really bad interop with some really critical components like WebView.

[networkimprov]

Maybe Flutter works as a client to a native localhost app? (Analogous to the browser for a localhost web app like Jupyter Notebook[1].)

Does it have a Websocket client?

[1] https://jupyter.org

[kllrnohj]

There's no reason to bother with websocket stuff, you can just call out to native code via platform channels ( https://flutter.dev/docs/development/platform-integration/pl... )

Just that once you do that you're no longer a portable cross-platform app, and there's limits to what you can do with that pipe in terms of data marshaling and the overhead from that.

[networkimprov]

Unless you're porting an existing localhost web app which is accessed via Websockets.

[Hixie]

https://master-api.flutter.dev/flutter/dart-io/WebSocket-cla...