Theatre

Embedded Development with Qt: Exploring Use Cases Beyond MCUs and MPUs

Veli-Pekka Heinonen

Watch Now

26:52

EOC 2023

Login to Watch

Veli-Pekka Heinonen

Veli-Pekka Heinonen is currently Senior Product Manager at The Qt Company, responsible for embedded platforms, WebAssembly, multimedia and related Cloud projects. He has over 20 years of experience in the IT and hardware industries, and he has been working in various product management and product marketing roles. Before joining Qt, his last position was at Cisco, working with customer projects, support, and security for a communications client. Veli-Pekka holds a master's degree in software engineering from Helsinki University of Technology (now known as Aalto University).

View full profile

The Qt Company

The Qt Company develops and delivers the Qt development framework under commercial and open source licenses. We enable a single software code across all operating systems, platforms and screen types, from desktops and embedded systems to wearables and mobile devices. Qt is used by approximately one million developers worldwide and is the leading independent technology behind millions of devices and applications. Qt is the platform of choice for in-vehicle systems, medical devices, industrial automation devices, and other business critical application manufacturers, and is used by leading global players in more than 70 industries.

Website LinkedIn

Session Slides

Download Slides (PDF)

Topics Covered

GUI/HMI

Theatre

Embedded Development with Qt: Exploring Use Cases Beyond MCUs and MPUs

Veli-Pekka Heinonen

26:52 EOC 2023

Veli-Pekka Heinonen

26:52

You may already be familiar with Qt's ability to support the entire embedded software lifecycle – from design and development to testing and deployment – but Qt can support a variety of use cases beyond the traditional. During this session, we will explore conventional scenarios, as well as newer innovations, such as WebAssembly and other solutions. Additionally, we will provide an overview of piloting Qt usage in the cloud and a Qt angle to Digital Twins.

1 / 4

Please log in or create an account to test your knowledge and see the answers.

According to Veli-Pekka Heinonen, why does Qt significantly simplify building a product portfolio across many embedded device models (e.g., multiple washing machine variants)?

A Qt provides the hardware adaptations and lets you use the same QML/UI and tools across different operating systems and hardware, avoiding repeated hardware adaptation work.

B Qt requires you to write a separate hardware adaptation layer for every new device to guarantee optimal performance.

C Qt forces you to standardize on a single hardware platform for the whole product portfolio, so you never change chips.

D Qt automatically designs the hardware schematics for each new device model so you don’t need hardware engineers.

E Qt only supports high-end MPUs, so low-end product variants must use a different GUI framework.

What primary benefit of Qt's WebAssembly support did Veli-Pekka highlight for C++ applications?

A It enables a "web story" for your existing C++ code so you can use the same team, tools and programming language and offer zero-install browser delivery.

B It makes browsers unnecessary because WebAssembly runs outside browser sandboxes as native processes.

C The main use is server-side only—Qt’s WebAssembly is intended solely to replace container technologies on servers.

D It converts JavaScript apps into C++ automatically for higher performance.

E It guarantees that every app compiled to WebAssembly will be smaller and faster than the native version without any extra work.

What key distinction did Veli-Pekka make between the Qt installer and the new container-based cloud piloting offering?

A The containers provide one Qt version along with a compiler and dependencies to create a standardized development environment; the output is still a native binary for the target device.

B The containers run on the target embedded device so your product executes inside containers at runtime.

C The containers are identical to the installer: many Qt versions but no compiler or dependencies are included.

D The containers are only available for QA tools and cannot be used for normal development or CI/CD.

E Using the containers requires abandoning local development entirely; they can only run in the Qt public cloud.

What is the main advantage of Qt’s digital twin / API simulation approach as described in the talk?

A You can start and continue software development using simulated hardware and sensors so the application does not need to know whether it's running against simulated or real hardware.

B It replaces the need for any physical hardware testing forever—simulations fully substitute real devices in all cases.

C It requires complete, cycle-accurate hardware physics simulation before any UI work can begin.

D It only works for UI mockups and cannot be integrated with UI tests or realistic event sequences.

E It depends on proprietary non-standard APIs, so simulated components cannot mix with real devices or standard protocols.

Formatting help

italics	surround text with asterisks
bold	surround text with two asterisks
hyperlink	[hyperlink](https://example.com) or just a bare URL
inline code	surround text with single `backticks`
code block (multi-line)	wrap on its own lines with three backticks: ``` your code here ```
~~strikethrough~~	surround text with ~~two tilde characters~~
quote	prefix with >

Upvotes Newest Oldest

No comments or questions yet. Be the first to start the conversation!

Partners & Sponsors

STMicroelectronics

Amazon AWS

Golioth

The Qt Company

Memfault

NXP

SEGGER Microcontroller

PE Micro

PX5

Become a Sponsor