Screens that UAE customers can use with one thumb, in either language.

Most UI/UX briefs we receive in Dubai are not about inventing a product. They are about a website or customer app that already exists and is not doing its job: a booking form people abandon on the second step, a property listing page that loads slowly on a phone, an Arabic version that was translated after launch and never redesigned. Our UI/UX design work starts from that reality. We look at the screens your customers use most, find where they hesitate, and redesign those screens first.

Mobile first is not a slogan here. Most of the traffic we see on UAE consumer sites arrives on a phone, often from an Instagram ad, a Google search or a WhatsApp link shared by a friend. That visitor is usually standing in a mall, sitting in a taxi or switching between apps. We design for a thumb, a small screen and a patchy connection in a car park, then scale the layout up to tablet and desktop rather than squeezing a desktop page down.

Bilingual design changes the work at screen level. An Arabic headline often runs shorter than the English one while the body text runs longer, mixed numerals and Latin brand names sit inside right to left sentences, and icons that point forwards have to point the other way. Phone fields need the +971 prefix handled cleanly, name fields must accept the way people actually write their names, and address forms should allow for community, building and flat rather than a postcode the UAE does not use. We design both languages together so neither feels like a copy.

Conversion and accessibility pull in the same direction more often than people expect. Clear labels, large tap targets, readable contrast in bright sunlight and forms that explain errors in plain words help a customer with poor eyesight and a customer in a hurry equally. We design to WCAG guidance as a working standard, and we place the actions that matter in this market, such as a WhatsApp button, a call button and Apple Pay or card checkout, where a thumb finds them without searching.

The final step is the one that most often goes wrong: handover. A beautiful Figma file that shows only the happy path leaves developers to invent loading states, empty states, error messages and the Arabic layout on their own. We hand over every state, a component library with named tokens for colour, type and spacing, annotated behaviour for anything that moves, and both language versions. If your developers are in house, at another agency or at Codeeo, they receive the same package.

Codeeo works from Dubai Silicon Oasis with a team of 80+ across Dubai, Riyadh and Karachi. You can review screens with our designers in person, or keep the whole project on video calls and a shared Figma file with comments in your own words.