UX/UI Design services
Screens people can use without training, designed before development starts.
Every screen drawn and agreed before development starts, including the ones where a payment fails or a form is half finished. You receive a component library in both languages, and you keep it whether or not we build the product.
Overview
UX/UI Design, the way we do it
Design is the cheapest place to correct a mistake. Changing a screen in Figma takes an afternoon; changing it after it has been built, tested and released takes weeks. So we draw every screen first, including the error states such as a failed payment or a half-completed form, and agree them with you before development starts.
What you receive is not a picture of a website. It is a set of components with their spacing, states and rules written down, in both Arabic and English, that a developer can build from directly. It is the same set our own developers work from.
What's included
What you actually get
- The journey mapped out before a line of code is written
- Every screen drawn, including the error and empty states
- A component library your developers build straight from
- Arabic and English each laid out the way they read
- Text and buttons sized for use on a phone
UX/UI Design capabilities
How we work
Five steps, no surprises
- 01
We talk
A call or a WhatsApp thread. You tell us what is not working; we tell you honestly whether we are the right people.
- 02
We scope it
A written plan with what you get, what it costs and how long it takes. Fixed, so there are no surprises later.
- 03
We build it
You see it as it goes, not at the end. Changes are cheap while it is still being built.
- 04
We put it live
On infrastructure we set up and secure, tested before the launch date.
- 05
We keep it running
Updates, monitoring and someone who answers. Most clients stay on a monthly agreement.
Questions
About ux/ui design
Can you work with our existing brand?
Yes, and we prefer to. Send us whatever exists: a logo, an old brochure, an existing colour palette. We design within it. If there is nothing, we will propose a direction and get it approved before applying it.
What do we actually receive?
A Figma file you own, with every screen, the components they are built from, and the rules for spacing, type and colour. Plus the Arabic layouts. You keep it whether or not we build the thing.
Do you handle Arabic properly?
From the first sketch, rather than as a translation pass at the end. Arabic reads right to left, which flips navigation, form fields, icons and charts. Retrofitting that into a design drawn for English is where most bilingual products fail.
Can you design something we build ourselves?
Yes. The handover is made for that: components, states and rules written down so another team can pick it up. We are happy to answer your developers' questions during the build.
Tell us what you have in mind.
An engineer reads your message and replies to you directly.
Talk to us