01Input
Your starting point
Enough to begin: a sketch, old HMI screen, reference image, requirement notes or an existing product.
Useful contextApplication · users · key functions · display target · important I/O or data.
From sketch to embedded HMI
Have an HMI idea, but only a sketch?
That may already be enough to start a prototype. A hand-drawn screen, an old HMI screenshot, a rough UI concept or a few notes can give us enough context to begin.
You do not need a complete specification before the first discussion. Start with the product idea and the information you already have.
What we can start from
Give us what you have. We help turn it into something real.
The goal is not to sell you another design tool. The goal is to understand the product, make the HMI behavior concrete, and get to a prototype that can be discussed on real embedded hardware.
02UX
Screen & interaction
We clarify: screens, navigation, controls, feedback, operating states and important exception paths.
OutputA clearer HMI definition instead of disconnected screen drawings.
03UI
Working prototype
We prototype: the visual direction and key interactions using a practical embedded GUI workflow.
ValidateUsability · screen flow · behavior · graphics complexity · performance assumptions.
04HW
Reference hardware
Then: map the prototype to a suitable MCU, HMI SoC or Linux/Android platform when hardware validation is needed.
Next stepDisplay · touch · compute · memory · connectivity · BSP · production path.
A practical first review
We do not need everything decided on day one.
The first pass is simply to understand what the HMI should do, what information you already have, and which unknowns matter most. We can then decide whether the right next step is a UI prototype, an architecture review, reference hardware, or a combination.
SketchScreen FlowStatesDisplayHardware
HMI Prototype Brief
Send your sketch, idea or current HMI requirement.
Fill in only what you know. When you submit, your email app will open with the brief prepared. You can attach your sketch, screenshots or requirement files before sending.
Not sure what architecture you need?
Start with the HMI requirement, not the processor.
The right hardware path can be selected after the UI, system workload and product constraints are clearer.