UX and UI design
We design the screens that go with the systems we build: field apps used one-handed in poor light, operator dashboards, and product interfaces a brand is judged on. Prototypes get tested before anyone writes production code.
Book a 30-minute scoping call See the design work
Design here is not a separate phase you buy. It is how the build avoids being wrong.
| One hand, gloves on Targets, spacing, reach | Tested |
|---|---|
| Bright sun and dim plant room Contrast in both | Tested |
| Interrupted halfway Draft survives, work resumes | Tested |
| First time user, no training Task completed unaided | Tested |
| Signed off by the person who owns it Before production code | Tested |
What kind of design
Two different trades share the word design. Knowing which one you need saves months.
Go to a brand studio for
We will work to a brand system you already have, but we do not create one.
Come to us for
We design what we then build, so the handover between design and engineering does not lose anything.
Plain definitions
Both get asked on almost every first call, and the answers change what you should be buying.
User experience is the decision about what the screens are and in what order somebody moves through them. It comes out of watching the job being done. User interface is what those screens look like and how they behave under a finger or a cursor.
You can have a beautiful interface over an experience that makes people give up, and it happens often. The reverse is rarer and less damaging. Both matter, and on the work we do the experience half is where the money is saved.
A design system is a set of components with the rules for using them, held in one place and shared by design and engineering. Buttons, forms, tables, spacing, states.
You need one when more than one team touches the product, or when the product will outlive the people who started it. For a single app built once it is overhead. We hand over a component library in code either way, because that is what stops the build drifting from the design.
What you get
What people ask us for
Every one of these is an interface that carries work, which is the only kind we do.
Our work
Case study, automotive
Verify Auto needed a safety compliance app whose interface matched the brand as precisely as the logic matched the standard. We designed to exacting standards, validated the direction with their stakeholders through prototypes before production code, and kept the build modular so the look could scale across the range.
Case study, United Kingdom
Hydrajaws had testing software their customers found hard to use, and it showed in the commercial results. The rebuild gave the apps a clearer structure, a free tier that let people try it, and a premium tier that reads instruments directly.
How the work runs
Week 1
We sit with the people doing the job, in the place they do it. Workarounds get written down, because they are the requirements nobody says out loud.
Week 2
Clickable, at real data density, covering the awkward states as well as the happy path.
Week 3
Put it in front of real users, unaided. Fix what fails, then get sign-off from whoever owns the process.
Into build
Component library and specs go to engineering, who are usually us, so nothing is lost in translation.
Tools and deliverables
The file is not the deliverable. The component library your engineers can build against is.
Who does the work
Designers here sit with the engineers who build the thing. That is the whole argument for buying design from a team that also ships code.
You meet the designer before you commit. Ask to see a task map from a previous project, because that document shows how a team thinks better than a portfolio does.
How we work
The models differ in one thing: how much of the management you hand over. Everything else, including who owns the code, is the same in all five.
Changing model later is normal. Augmentation into a dedicated team is the common direction, and the people stay.
Engineers join your team and work inside your process, your board and your code review.
A team that works only on your product, with a lead on our side running delivery.
A long-term engineering site under your standards, where we carry recruitment, HR, payroll and equipment.
04
One price for a scope that is genuinely settled, with the overrun carried by us.
Everything in the centre model, with the whole team moving into your own Vietnamese entity on an agreed date.
FAQs
Yes. You get the task map, the prototype, the screens and a component library, and you can take them to any engineering team. We would rather that than design something nobody builds.
Yes, and we prefer it. We apply a brand system, we do not create one.
Enough to find the blocking problems, usually five to eight per role. The aim is to find what stops people, not to produce statistics.
Then we test with the closest proxy we can get and say clearly what that limits. Designing without any contact with users is guesswork, and we will tell you that rather than proceed quietly.
Whatever your team can pick up. The deliverable that matters is the component library in code.
You do, along with everything else we produce.
A prototype and testing round for one application is typically three to four weeks. Where design leads into a build with us it sits inside the project rather than being priced separately, and the engagement model above decides how that is billed. Design bought on its own is quoted by the scope of the task map and the number of roles being tested, which we agree before starting.
We work to WCAG 2.2 AA as a baseline for contrast, target size, keyboard order and labelling, and on field apps that is practical rather than decorative. A formal accessibility audit against a legal obligation is a separate piece of work by a specialist, and we will tell you when your situation calls for one.
Then we work inside it, and we prefer that. We apply a brand system rather than create one. Where your system has gaps, which is usually in the states nobody remembers to design, we extend it in your own conventions and hand the additions back as components.
The screen everyone avoids, the form finished on paper instead. That is where the design work starts, and thirty minutes is usually enough to find it.
