Qt Quick : Don't make these mistakes!
summary
basysKom describes rescue work on Qt Quick projects that explode in size and memory: an automotive build delivers 500–600 screens converted from design XML, creating over 50,000 objects per target, dropping performance to ~25 FPS and 5–10 second screen loads. The fixes are concrete: identify heavy screens, hand-rewrite to lightweight custom QML controls, replace large textures with shaders or flat rectangles, add CI and simulation, enforce code reviews/APIs and continuous refactoring so the app actually boots on the target.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:01The embedded transition
- 3:45Communication and spec
- 5:58Project disaster
- 8:35Root cause analysis
- 11:50Lessons in architecture
- 13:57The recovery project
- 17:30Fixing bad code
- 21:22Conclusion
related talks
55mProgramming with Qt Quick 2/6 - Meet Qt Quick Part 2
23mDesigning UIs with Qt Quick 5/6, Animations Part 2
27mSet Yourself up for Success — Lessons Learned from Building 100+ Devices with C++/Qt/QML
20mQt Apps with Nokia - Design, Develop, Distribute 3/7 - Overview (continued)
30mDesigning UIs with Qt Quick, 2/6, Design-Workflow Part 2
49mHow to scale QML based projects an Architecture vision
01h 19mGetting Started - a Qt fast track 4/4 - Application Creation
01h 03mDesigning UIs with Qt Quick 6/6, Practical Sketching