Design that survives contact with Arabic.
Design systems, bilingual interfaces, and RTL done properly — research through to a component library your engineers can actually build from.
How we treat this work.
Bilingual design goes wrong in a predictable way. The product is designed in English, looks good, gets built — and then Arabic arrives and the headline collides with itself, the icons point the wrong way, the numbers reverse, and the nav that was elegant at 40 characters is unreadable at 25.
Designing both languages from the first screen costs a fraction of fixing it afterwards. That means Arabic typography with room for diacritics, mirrored layouts and iconography, number and date handling that matches the locale, and copy written in Arabic rather than translated into it.
The deliverable is not a set of screens. It is a component library with states, tokens, and RTL rules that an engineer can build from without asking what happens at 320 pixels or in Arabic — because both are already specified.
What actually lands.
A design system, not a mockup
Tokens, components with every state, and layout rules — the thing engineers build from, versioned alongside the code.
Bilingual and RTL from the start
Arabic typography with room for diacritics, mirrored layout and iconography, and locale-correct numbers and dates.
Research with real users
Interviews, journey mapping, and prototype validation before a line of production code — including with Arabic-speaking users, not only English ones.
Accessibility to WCAG 2.2 AA
Contrast, focus order, target sizes, and screen-reader behaviour designed in — which also matters for government procurement.
Motion with a purpose
Transitions that explain what changed, with reduced-motion honoured rather than treated as an edge case.
Handover engineers can use
Specs that answer the questions engineers actually ask: empty states, error states, long content, narrow screens, and both languages.
The markets we ship into.
- Saudi Arabia — including government-facing products where Arabic is the primary language and accessibility is a procurement requirement.
- Egypt — consumer and marketplace products designed for Arabic-first audiences.
- UAE — bilingual enterprise and B2B interfaces.
- United States — products serving Arabic-speaking communities in an English-first market.
Work we shipped with it.
Arabvesta
Community, experts, and offers for Arabs building a life in the U.S.
Nabd Cardio
Adult and pediatric cardiology across two Egyptian branches, Arabic-first.
Sealife Connect
Egypt's first marketplace for boat owners, renters, and buyers.
What gets asked before signing.
- Can you design without building?
- Yes. Plenty of clients have their own engineering team and need the design system and specs. We build the handover for that case specifically — component states, tokens, RTL rules, and the edge cases engineers hit on day three. It is a common engagement, not a consolation prize.
- We have an existing brand. Do you work within it?
- Yes, and usually that is the job — extending a brand into a product system rather than replacing it. Brands built for print often have gaps for interfaces: no interaction colours, no accessible contrast pairs, no Arabic type pairing. We fill those in and document them back to you.
- Why does Arabic need separate design attention?
- Because more changes than direction. Arabic sets shorter for the same meaning, carries diacritics above the line and descenders below it so tight leading collides, does not take letter-spacing without breaking letter joins, and reverses iconography and progress direction. A layout that was only tested in English will break in ways nobody notices until a user complains.
- How long does the design phase take?
- For a first product release, typically four to eight weeks including research — but it overlaps the build rather than blocking it. We design ahead of engineering by a sprint or two, which keeps both teams working and surfaces the impossible ideas while they are still cheap to change.
- Mobile app developmentMobile apps that pass review and keep shipping.
- Web developmentWebsites and web platforms that load fast and read natively.
- Applied AIAI that moves a number, not a demo.
- Cloud & DevOpsInfrastructure you can hand to an on-call engineer.
- Technical leadershipSenior judgement, for the phase that needs it.
Have an RFP? Have an idea? Let's build it.
We reply to every inquiry within one business day. Tell us about your project, timeline, and what success looks like.