UI/UX design
UI and UX design for software products
Design you can use within hours of describing the problem. We do not hand over a picture of an application and leave the hard part to someone else.
The problem
A design that has never been used is a hypothesis
Static mockups get approved in meetings and fall apart in use, because nobody can feel a click-through in a slide. The gap between an approved design and a usable one usually shows up during the build, when changing it is expensive and the design team has moved on.
How we work on this
Prototype first, then the build you approved.
Design happens inside the prototype. Within two to three hours of the first conversation there are real screens with your terminology and your workflow, which your people can use and argue with. What they tell us changes the design before any production code exists, and the same team carries it into the build.
What this covers
Capabilities, and where each one stops.
-
Interface design
Screens, states and flows for the workflow that matters, in your terminology rather than generic product language.
-
Usability testing with your people
The prototype put in front of the people who will actually use it, early, when their reaction is still cheap to act on.
-
Design systems
Tokens, components and patterns so the second and third screens stay consistent without a designer in the room.
-
Accessibility
Keyboard paths, contrast, focus order and reduced-motion support treated as part of the design, not a late audit.
-
Redesign of an existing application
Improving the interface of something already in use, without changing the business logic your people rely on.
We do not sell brand identity, logo design or marketing campaigns. Our design work exists to make software usable.
How it is built
Decisions we make the same way every time.
- Clickable prototypes over static mockups
- Mobile layouts designed at the same time, not afterwards
- Respecting reduced-motion and keyboard navigation
- Design handed over as working code, not just files
- One person accountable for the design through to go-live
Where this applies
Industries we have gone deep in, and the rest of the ecosystem.
Questions
The questions people ask about this work.
Do you do design without the build?
Yes, but the deliverable is still a working prototype rather than a static file set, because that is what can be tested. If you take it to another team to build, you keep it.
How do you handle accessibility?
Keyboard navigation, focus order, contrast and reduced-motion support are designed in. They are cheaper at design time than as a retrofit.
All questions, including the ones that might lose us the deal
Show us the interface problem
Describe the screen or the workflow people struggle with, and we will show you an alternative you can click.