knowgo-vehicle-simulator VS macos_ui

We published our vehicle simulator in the Microsoft store, using the msix package for package preparation. It took a little bit of trial and error to find the right combination for the configuration, but you can look at our pubspec.yaml if you're curious. Happy to answer any questions if you're running into problems.

KnowGo Vehicle Simulator - Connected Car simulator written in Flutter

Source

One of the more glaring limitations at the moment, besides the lack of web- and desktop-ready plugins, is the fact that isolate to web worker mapping was stripped out of dart2, so you're still forced to maintain separate isolate and web worker-based solutions for anything that needs to do background processing (e.g. most real applications that aren't just toy UI mockups). Having different dart:io and dart:html code co-exist in the same codebase is possible, but still quite ugly. The Dart<->JS interaction is also still incredibly clunky, particularly when you can't just push object serialization/deserialization to the JS side for dart:io code. You can see some of the tricks we had to come up with to work around this in our vehicle simulator: https://github.com/knowgoio/knowgo-vehicle-simulator

Well, if I'd go FluentUI or macOS I wouldn't really be cross platform any more, unfortunately.

In light of discussions I've had on Twitter about the lack of a macOS style widget/theme pack, I've started a package for this: https://github.com/GroovinChip/macos_ui. This is a huge undertaking so I'd appreciate any assistance, be it advice, feedback, repo maintenance, code contributions, or simply spreading the word.