01
Interaction model
Define modes, settings, timers, status and onboarding before selecting the GUI architecture.
Smart appliance HMI solutions
Turn a touch interface into a product-ready appliance HMI.
Balance visual experience, BOM, boot behavior, connectivity and production constraints before committing to the platform.
Start with requirements
Clarify the HMI workload before choosing the platform.
The goal is not to force every product into one architecture. These are the decisions that narrow the practical options.
02
Visual experience
Animation, assets, transitions and screen resolution determine graphics and memory needs.
03
Connected product needs
Wi-Fi, Bluetooth, cloud onboarding and updates can influence platform and software decisions.
Architecture options
Choose the software and compute class from the real workload.
A focused control UI, a graphics-rich real-time interface and an application-style Linux HMI have different engineering and lifecycle trade-offs.
Compact MCU / RTOS
For focused appliances with cost-sensitive hardware, fast boot and controlled UI scope.
Performance RTOS HMI
For richer touch experiences and more graphics while keeping an embedded real-time architecture.
Embedded Linux HMI
For complex connected workflows, richer frameworks or broader application integration.
Hardware + software stack
Evaluate the complete HMI path.
01
Display & touch
Select size, resolution, touch and module construction around industrial design and UX.
02
Compute
Match graphics performance and peripheral needs to the real UI rather than the demo alone.
03
GUI
Use LVGL, Qt or another workflow that fits the team, asset pipeline and product complexity.
04
Connectivity
Plan Wi-Fi, Bluetooth or cellular only where the product experience needs it.
05
Storage
Budget assets, fonts, logs and update images early.
06
Production
Validate module supply, programming, test and software release flow before MP.
Reference path
Reference demo: Smart Home Appliance HMI
A touch-driven appliance interface with mode selection and timing controls provides a concrete starting point for discussing UI scope and platform needs.
Before hardware freeze
Validate what can become expensive later.
01
Cold boot
Measure the real startup experience on target hardware.
02
Touch UX
Validate hit areas, latency and interaction flow on the final display size.
03
Graphics headroom
Test animations, images and worst-case screen transitions.
04
Connectivity flow
Prototype onboarding, reconnect and update behavior where applicable.
05
BOM fit
Check that the chosen architecture still matches target cost and volume.
06
Manufacturing flow
Define flashing, calibration, test and field update requirements.
Planning a similar product?
Bring a short requirement. Start with the next practical decision.
No complete specification is needed to discuss architecture, evaluation hardware or engineering support.