// 04 — Services
UI/UX design.
Interfaces that feel inevitable. We design systems, not screens — every state, every edge, documented and buildable.
A screen is easy. A system is what stops the product drifting apart by the fortieth screen — the same spacing, the same states, the same behaviour when something is empty, loading, or has gone wrong.
We design every state, not just the happy one, and document it so engineers build it without guessing. Accessibility to WCAG 2.2 AA is part of the work rather than a later audit, and bilingual products are designed in both directions from the first component.
The deliverable is a design system and clickable prototypes your team can build from — not a folder of images that need interpreting.
Common questions.
- Do you design without building?
- Yes. The design system and prototypes are documented for another team to implement. That is a normal engagement, not a compromise.
- How do you handle Arabic and English in one design?
- Both directions from the first component. Right-to-left is not a mirror image — play controls, phone numbers and logos do not flip, Arabic needs more line height at the same size, and the Latin and Arabic faces have to be paired deliberately or the mismatch shows on every screen.
- Is accessibility included?
- WCAG 2.2 AA is part of the standard work. It is far cheaper designed in than retrofitted, and it is the difference between a product that works for everyone and one that quietly excludes people.
