Coding Qt for greater interoperability and portability ...
summary
Modular architecture that wraps JavaScript apps in a Qt WebEngine host to let automakers reuse the same app logic across brands, with an OpenCar platform providing an SDK and simulator, automated certification and W3C telematics profiles. Integration layer exposes websockets HTTP and raw 8bit binary and maps CAN and steering‑wheel inputs; middleware is tiny (middleware ~5MB), framework libs ~12MB, HMI profile ~5.5MB, 40 sample apps ~200KB each. Goal: shorten 18–24 month projects toward SDK downloadable and OTA updates.
AI-written summary · about
chapters (11)
- 0:00Introduction to OpenCar
- 2:10Challenges in automotive software
- 4:00Framework and SDK overview
- 7:10Application logic and HMI profiles
- 10:43Integration layer and runtime
- 14:00Benefits and stack stability
- 16:53Development timeline compression
- 19:03Simulator and HMI creation
- 23:24APIs and middleware layer
- 24:54Future with Qt Quick
- 25:38Q&A and driver interaction
related talks
21mQtinUse - Introducing Qt IVI (1/5)
49mScaling Qt from Desktop to Servers and Micro-controllers
24mDesigning UI Architecture for Embedded Devices with Qt and QML
27mSet Yourself up for Success — Lessons Learned from Building 100+ Devices with C++/Qt/QML
07mQtinUse - Introducing Qt IVI (4/5)
28mModel-based HMI development using Qt
58mHybrid development with QtWebKit
04mQtinUse - Introducing Qt IVI (2/5)