In order to anwer these questions, we decided to choose one hardware platform (STM32H7) and three different MCU-Libraries (Qt for MCU, Embedded Wizard and TouchGFX) in order to implement the same demo-concept on this platform. The basis for the design should be defined by our famous bottling-demo that was already used in previous comparisions (see HTML5 vs Qt here).
At the moment, we prepare a detailed technical report that will contain a comparision map and tell you the individual stories behind the implementation process of each technology. The comparison matrix will contain criterias like possible hardware-platforms, possible runtime environments, IDE features, development language, model-view architecture approach, dynamic contents at runtime, license information and costs. If you are interested, let us know in advance () that we can inform you once the report is ready!
Here we have a short teaser video
We also ported the sequality virtual cockpit automotive application to Qt-for-MCU here: