feedback VS knowgo-vehicle-simulator

In another, I use https://pub.dev/packages/feedback + feedback_gitlab (which will open an issue on GitLab).

Hi, I have tried it, I like it but it is too basic now. I think it is ok now because you are more in an MVP stage, but I have some feature requests. It would be cool to have them in the future: - a feedback to the user when he submits a wish(in the ui kit) - different labelling for the features - How to create a web version like this https://demo.wishfly.dev/. And embed this on your website to showcase it more - The possibility to show a roadmap based on the wishes - Sync wishfly with backend accounts of the app - The possibility to add comments - The possibility to submit without reviewing for users - Show more clearly that the pricing is 5$ per month, it does not show per month. - The possibility to merge two wishes adding the number off upvotes - Add images to the feature request - Integrate with https://pub.dev/packages/feedback

I would recommend to use feedback.

feedback and feedback_gitlab - together, these are amazing. Your users can file bugs with annotated screenshots, from within your game

Is it something like this : feedback

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