expertise — 04
Software for products that live in the physical world.
Product UX and UI, embedded HMI, companion apps, cloud and fleet tooling — designed from the operator's task backwards and engineered to ship, for devices that can't fail quietly.
who this is for
When the app is half the product.
Device companies whose software was an afterthought and now gates every sale. Teams designing interfaces for gloves, sunlight, latency budgets and safety states — constraints a web agency has never met. Operations groups running fleets that need provisioning, updates and support tooling that actually works. If your software touches hardware, this is the practice built for it.
what we do
The offerings.
Product UX & UI
The applications around the hardware — companion apps, consoles, dashboards — designed from the operator's task backwards. Information architecture, interaction design and a component system tight enough that new screens design themselves. You walk away with a tested design system and flows measured against task success, not taste.
HMI & Embedded Interfaces
On-device screens and controls under real constraints: sunlight, gloves, latency budgets, safety states, a rotary encoder instead of a mouse. We design the full state model — normal, degraded, fault — because devices spend their worst days in the last two. You walk away with a complete HMI specification, motion and sound behaviour included, ready for the embedded team.
Product Software Engineering
We build production software, not just pictures of it: device companion apps, control front-ends, cloud services and APIs, written in your repositories to your review standards. Where AI belongs in the product — assistive features, anomaly detection, natural-language control — we design and ship it with honest limits. You walk away with deployed, tested code your team maintains without us.
Connected Ecosystems
Device, app, cloud and fleet designed as one system: provisioning, pairing, identity, OTA updates, telemetry and the dashboards a support team actually uses. Decisions about what data leaves the device are treated as product decisions, made explicit. You walk away with an ecosystem architecture and interfaces that make a fleet feel like one product.
how it runs
Designed and shipped by the same room.
Interface work runs against the physical product from day one — the HMI review happens with the enclosure on the table, not a Figma frame. Where we write code, it lands in your repositories, passes your reviews and deploys through your pipeline. The measure is task success in the field, not screens in a deck.
- Tested design system and task-measured flows
- Full-state HMI specification: normal, degraded, fault
- Production code in your repos, reviewed to your standards
- Ecosystem architecture: provisioning, OTA, telemetry, fleet tooling
straight answers
Asked often.
Do you hand off designs or ship code?
Both, and we're explicit about which at scoping. Design-only engagements deliver specifications an embedded team can implement without us on the phone; build engagements end in deployed code.
Can you design for gloves, sunlight and hard latency?
That's the job. HMI here is designed under the device's real constraints and tested on hardware, not simulated in a browser.
Where does AI fit in the product?
Only where it survives contact with users: assistive features, anomaly detection, language interfaces — shipped with honest limits and a fallback for the day the model is wrong.
works with
Half of one product.
HMI is designed with the physical controls it lives behind, ecosystems inherit constraints from engineering, and interface motion feeds the motion identity. Sector depth: connected devices, robotics, medical devices.