Designing UI Architecture for Embedded Devices with Qt and QML
summary
Explains a concrete UI architecture using Qt/QML and Qt Automotive Suite: an application manager runs apps in separate processes, UI pieces are split into panels/controls/views with only stores isolate backend depending on generated APIs, and an IDL plus code generator creates a surface layer (Qt Remote Objects) for simulation. Demonstrates UI harnesses and live-reloading to edit and push a panel to a device, shows Neptune 3 reference implemented this way, and reports the demo deploys and updates successfully.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 1:03Challenges in UI development
- 3:20Kiribati automotive suite overview
- 5:49Development workflow with designers
- 8:00Modular UI architecture explained
- 10:16Scaling UI with team collaboration
- 12:12Middleware and API design
- 14:44Testability and simulation
- 15:05Live demo introduction
- 21:29Benefits of clean architecture
related talks
27mHow to Implement an Automotive Infotainment System using Qt Quick
01h 02mAnatomy of real world apps, Qt Quick and C++
27mSet Yourself up for Success — Lessons Learned from Building 100+ Devices with C++/Qt/QML
24mThe Roadmap: Next Generation Qt (part 2/2)
48mBuilding Desktop and Embedded Uis with Qt 3D
53mQt Quick Best Practices and Design Patterns
49mQt Quick Best Practices and Design Patterns
28mModel-based HMI development using Qt