imBMW VS Caliburn.Micro

Fair enough. BMW seat controls are mounted in the center console and talk to a computer that sends signals to the chair for movement. There is another signal sent from the car's main computer that tells it when certain conditions are met, such as ignition on, daytime lights on, etc. Those signals are needed to keep the controls active and let the seat move. Talking with the author of the code, he was too busy to really explain what was needed but said "It's quite simple, you just need to use this code" and provided this specific link to the page. Specific line

It works with ActivateItemAsync but I don´t know if there is a difference that I should be aware of ? They seem to be a bit slow with updating the documentation so I´m a bit nervous about what else might not be updated yet.

The programming model reminds me of Rob Eisenberg's older attempts at building UI toolkits ([0]). I don't recall if that was fully async or 'just' using a coroutine/generator-style approach, but it feels similar.

I'm not sure the complexity of doing everything using async constructs is worth it, though. Large-scale UI's built in Qt or Javascript are mostly single threaded anyway, but it's still worthwhile to explore so kudos for that. Looking forward to seeing how far you get.

[0] https://github.com/Caliburn-Micro/Caliburn.Micro

Vanilla WPF has a lot of boilerplate and verbose binding expressions. I'd check out an MVVM library like https://caliburnmicro.com/ which has tons of convention-based features and helps maintain the "screens" in your app.

Your UI needs to bind to something that can programmatically notify it about changes, we call these things View-Models. Usually View-Models implement INotifyPropertyChanged interface (another key interface is INotifyCollectionChanged that is responsible for notifying collection views that number of items is changed and they need to update the UI accordingly). You can do that (the implementation of the interface) manually or use some library to do that for you just to cut some boilerplate code (e.g. ReactiveUI + Fody or Microsoft.Toolkit.MVVM or maybe even this or this).

I haven't done WPF/XAML stuff in years but I really liked Caliburn Micro, largely because of the convention-based auto-binding.