01
Consumer-style UI
Define animation, navigation and interaction quality before estimating compute needs.
Smart Appliances & Consumer Electronics
Deliver a polished touch experience without overbuilding the platform.
Smart appliances and consumer devices often combine touch-first UI, visual polish, connectivity and tight product integration. Match the architecture to the real interaction and cost targets.
What matters first
Clarify the product constraints before choosing components.
Use these questions to narrow the HMI workload, then compare compute, display, GUI and engineering paths.
02
Cost & BOM
Balance display, memory, compute and connectivity against the product target rather than optimizing one part alone.
03
Connectivity
Separate local control from cloud, app and wireless requirements.
04
Touch + enclosure
Evaluate the display, cover lens, touch stack and mechanical integration together.
Architecture options
Let the workload decide the architecture class.
A focused serial or MCU interface, a richer RTOS HMI and an application-class Linux system solve different problems. The HMI Selector uses the rest of your brief to narrow the starting point.
Smart Display / Compact MCU
For focused control and status interfaces where integration effort, startup and cost matter strongly.
Performance RTOS HMI
For richer graphics, more pages and broader I/O while retaining an embedded real-time product model.
Embedded Linux HMI
For complex workflows, larger software stacks, networking, media or application-style functionality.
Reference demo
Smart appliance reference demo
The existing smart-home appliance demo provides a concrete reference for touch navigation, mode selection and embedded UI polish.
Planning a product in this category?
Start with the application brief, not a fixed processor.
Use the selector for an initial architecture direction, or share the project constraints for a more specific discussion.