Slint
We have been working with Slint since its early days, building strong expertise in developing responsive, reliable and maintainable HMIs for embedded products.
Slint and C++, cleanly separated.
Slint has evolved significantly over the years and has become a compelling choice for developing modern embedded UIs. Our combination of Slint and C++ expertise lets us turn UI requirements into production-ready interfaces that integrate seamlessly with complex application logic.
We use Slint's C++ interpreter integration, keeping presentation in declarative .slint files and all business logic in native C++. This clean separation keeps the UI easy to evolve while giving us full control over performance, state handling and integration with the rest of the system.
Our experience extends well beyond UI development, from state-driven interfaces to integrating multimedia and live video, so Slint works in demanding real-world HMI applications.
What Crossware brings to a Slint programme
A complete HMI runtime, in C++
A full HMI runtime for Slint written in C++, giving any application or device backend a clean, stable way to connect to the Slint UI.
Configurable UIs, any resolution, at runtime
UIs built to scale to any screen resolution at runtime, so the same Slint application adapts across display sizes without a rebuild.
Hot swap of Slint files
Slint UI files can be swapped at runtime, without rebuilding or restarting the application behind them.
One backend, many UIs
A configuration tool that points the same backend at different UIs, so product variants can each carry their own interface on shared backend code.
Where Slint work stands today
Touch door intercoms on i.MX8
A new generation of scalable touch-based door intercoms, built on Slint and running on i.MX8, developed for a leading Norwegian communication device maker in a multi-year partnership.
See the programme →A lightweight, native alternative for touch UI
Slint gives a lightweight, natively-compiled UI toolkit for touch-based embedded Linux devices, an alternative to Qt where a smaller footprint or tighter hardware integration matters.
Alongside Qt, Qt for MCUs, Flutter and LVGL
Part of the same HMI toolkit range Crossware works across, so the framework decision is based on the product's actual constraints, not just what a team already knows.
See Digital Cockpits →Frequently asked questions
How long has Crossware worked with Slint?
Since Slint's early days, predating most of the ecosystem's production adoption.
How do you structure a Slint and C++ application?
Using Slint's C++ interpreter integration, presentation stays in declarative .slint files and all business logic stays in native C++. The separation keeps the UI easy to evolve while giving full control over performance, state handling and system integration.
Can Slint handle live video and multimedia?
Yes. Crossware's Slint work goes beyond UI development to integrating multimedia and live video into demanding real-world HMI applications.
Does Crossware provide the full application, or just the UI?
Both. Crossware builds the Slint UI itself and a complete HMI runtime in C++ that lets any application or device backend connect to it.
Can the UI be updated without reflashing the whole application?
Yes. Slint UI files can be hot-swapped at runtime, without rebuilding or restarting the application behind them.
We have multiple product variants on the same hardware, does that mean multiple backends?
No. A configuration tool points one shared backend at different UIs, so each variant carries its own interface on the same backend code.
Does the UI need to be redesigned for different screen sizes?
No. Crossware builds Slint UIs that scale to any screen resolution at runtime, so the same application adapts across display sizes without a rebuild.
Contact us to learn more about our Slint and C++ expertise.
If you are planning an HMI or embedded UI project and want a team with hands-on Slint and C++ experience, we would love to talk.