HMI design and UX
Touchscreens, user control panels and live-data dashboards shaped around users, display constraints and physical controls.
DeliverablesUser flows, screen designs, reusable UI components and interaction notes.
Services / Define your scope
HMI design,
development and integration.
Commission a complete HMI or a defined part of the work. If the requirements or platform are uncertain, start with a scope and feasibility assessment.
Embedded software development
Build the interface and supporting application software on the target device, including application logic and agreed data interfaces.
DeliverablesWorking application, agreed project source, build instructions and documented interfaces.
Platform selection and integration
Select suitable display and computing hardware where needed, configure the embedded platform and connect the HMI to your product’s systems.
DeliverablesHardware recommendations, platform configuration, device communication and on-device checks.
Available Linux/BSP support is assessed early. Custom BSP or driver development is a separate scope.
Ways to begin
Start where
your project is.
- Complete HMI project
- Design, software and integration, with agreed milestones and acceptance criteria.
- A defined part
- Refresh the UI/UX of an existing HMI, add a new function, or integrate a new display or computing platform into your product.
- Scope and feasibility
- Assess platform options and constraints, identify key risks, and define a proposed scope and development plan.
A substantive feasibility assessment can be a paid initial engagement.
Describe your product, what is already in place and what you need delivered.
Discuss your projectDelivery
Defined. Reviewed.
Handed over.
Define and design
Agree requirements, responsibilities, interfaces, acceptance criteria and a milestone plan.
Build and prove
Review working software on relevant hardware and test key assumptions.
Integrate, test and hand over
Test the agreed deliverable against acceptance criteria, then complete the handover.
Fit for the product
Requirements guide design and technology. Keep the solution straightforward.
Direct contact
Discuss decisions with the engineer responsible for the deliverable.
A clear handover
A walkthrough of the agreed source and documentation, so your team can maintain and develop the HMI further.
Practical questions
Before we start.
Engineering capabilities
Will we receive the source code?
Yes. You receive all project source code, build instructions and dependency documentation. Third-party libraries and development tools remain subject to their own licence terms.
Can you work with our existing hardware and software?
Existing hardware, software and interfaces are assessed first. Where they suit the requirements, the HMI can build on what is already in place.
How do you choose the technology?
Requirements, existing hardware, supplier support and licensing guide the choice. The aim is a straightforward platform your team can maintain.
How is the HMI tested?
Requirements and acceptance criteria are agreed first. Working software is tested on target hardware against agreed operating and failure scenarios, with results reviewed with your engineers.
Can we test the idea before a full build?
A focused prototype on representative hardware can test key risks, such as responsiveness, display suitability or device communication, before committing to the wider build.