UX/UI Design

Research, wireframes, prototypes and interface design — including a design system your developers can build from without guessing.

Start a project

Overview

Design that answers a question, not a taste test

The point of UX work is to remove the reasons people give up: a form that asks for too much, a flow that hides the price, a mobile layout where the primary action sits below three scrolls of hero image.

We find those with research and usability testing rather than opinion, prototype the fix, test it on real users in Arabic and English, and hand developers a component system with states and edge cases specified — which is what stops a beautiful design becoming an average build.

What's included

User research & analytics review

Interviews plus a read of where people currently abandon the flow.

Information architecture

Navigation and content structure that matches how people look for things.

Wireframes & prototypes

Clickable prototypes for the flows that carry the revenue.

Usability testing

Real users, both languages, with the findings recorded rather than argued.

Design system & handoff

Components, states, RTL rules and accessibility notes for the build team.

How we work

Research, prototype, test, specify

  1. Learn

    Analytics, session recordings and interviews to locate the real problem.

  2. Sketch

    Wireframe two or three approaches instead of polishing one.

  3. Test

    Prototype and test with five to eight users per language.

  4. Specify

    Final UI plus a component library and written handoff for developers.

What you get

  • Research findings report
  • Information architecture
  • Interactive prototype
  • Usability test results
  • Design system & dev handoff

The outcome

Fewer drop-offs and fewer arguments

A tested interface with measurably better completion on the flows that matter, plus a documented design system that makes every future screen faster to design and cheaper to build.

Related work

Frequently asked questions

Do we need research if we already know the problem?

Often the known problem is a symptom. A week of analytics review and five interviews usually costs less than redesigning the wrong screen, and it changes the brief more often than not.

Can you design for a build we do ourselves?

Yes, and the handoff is the point: components, states, spacing, empty and error cases, and RTL behaviour specified so your developers are not inventing decisions.

How do you test in Arabic?

With Arabic-speaking participants on the Arabic interface. Testing an RTL layout only in English hides exactly the problems RTL introduces.

What if testing says our idea is wrong?

Then it saved you a build. We report what happened rather than what was hoped for, and we bring an alternative to test in the same round.

Explore related services

Users dropping off somewhere?

Tell us which flow leaks. We will find out why before redesigning anything.

Start a project