UX and UI design

You know a great deal, and research builds on it. It tests assumptions with the people who do the work, and often reveals steps, workarounds and terms that never reach a requirements document. Even a small round of interviews and prototype tests before the build costs less than changing software after it ships.

The number of user groups and journeys, how much research is needed, whether a design system already exists, and how many platforms and languages the design must cover. Redesigning an established product with many screens takes more than designing a focused new tool. We scope design in stages, so you can review the findings and flows before committing to the full interface.

We design to WCAG 2.2 AA from the first wireframe: enough colour contrast, visible focus, a logical reading order, touch targets large enough to use, and a label for every control. We check designs before handover and test the built product with a keyboard and screen readers. Accessibility designed in costs little. Added later, it costs a great deal.

Yes. Right-to-left design is more than flipping the screen. Navigation, progress indicators, charts and icons that imply direction need mirroring, while numbers, logos and media controls usually do not. Arabic text needs its own typeface, size and line height. We design both directions together and review them with native readers.

A design system is a shared set of colours, type, spacing and components, with guidance on when to use each, kept in step between design files and code. You need one when several teams or products must look and behave consistently, or when a product will grow for years. For a single small tool, a lighter component library is often enough.

In the same team and at the same rhythm. Designers join planning, hand over designs and components with their states and behaviour documented, and review what is built before it ships. Engineers join research and design reviews early, so ideas that are hard to build are caught before they are polished.

Intellectual property in the work we build for you is yours from the first commit — no assignment step at the end. That covers the custom code, documentation and other deliverables made for you. Anything we bring that existed before, such as internal tools or libraries, stays ours, and you receive a licence to use it in your systems. Open-source components keep their own licences, and we list them for you.