Design in the UAE: what changes when you build for a Gulf audience

Most products that launch in the Gulf were designed somewhere else. They usually work, in the sense that nothing is on fire, and they usually underperform, because a dozen small assumptions built into the design do not hold here. None of them are hard to fix. All of them are cheaper to fix before launch than after.

This is what we check on every product we build for the UAE and the wider Gulf.

Arabic is not a translation layer

The common plan is to ship in English, get traction, then add Arabic later as a language toggle. That works for a marketing site. It rarely works for a product, because Arabic does not slot into a layout designed around English.

Arabic runs right to left, so the entire interface mirrors. Letters join, so you cannot letter-space them, and there are no capitals, so any design that leans on uppercase for hierarchy loses that tool. Text length changes, often shorter than the English, which leaves buttons and cards looking empty if they were sized to the English string. And Arabic type needs more line height than a Latin face at the same size to stay readable.

If Arabic is on the roadmap at all, design the first screen in both languages. It costs very little at the start and it prevents a rebuild later.

What right-to-left actually changes

Mirroring is not global. Some things flip and some things must not, and getting the second group wrong is what makes an interface feel machine-translated.

• Layout, navigation, alignment and progress direction all mirror. Back arrows point right.
• Numbers, dates, phone numbers, email addresses, URLs and code stay left to right, inside an otherwise mirrored line.
• Icons that imply direction flip. Icons that represent a real object do not, so a play button and a clock stay as they are.
• Charts and timelines usually mirror, but check with real users, because financial audiences in the region often read them the Western way round.
• Latin brand names stay Latin. Do not transliterate a product name unless the client has decided to.

One more that catches teams out: most Gulf interfaces use Western digits rather than Arabic-Indic ones, even in Arabic copy. Check the preference with the actual audience rather than assuming either way.

Names, addresses and forms

Form design carries more Western assumptions than any other part of a product. In this market they surface immediately.

• First name and last name is the wrong shape for Arabic names, which commonly run to four parts including the father's and grandfather's names. A single full-name field avoids the problem entirely.
• Addresses often have no street number or postcode in the way a Western form expects. People navigate by area, building and landmark, and Makani numbers exist in Dubai but are not universally known.
• Phone numbers need to accept several country codes as a matter of course. Your users are Emirati, Indian, British, Egyptian and Filipino, frequently in the same week.
• Do not make postcode required. It is the single most common broken field we see on products entering this market.

Identity and verification

Emirates ID is the anchor of identity in the UAE, and any product touching finance, health, property or government will end up asking for it. UAE Pass, the national digital identity, is increasingly the expected way to sign in and sign documents, and supporting it removes a large amount of friction that competitors still make people suffer through.

For onboarding, that means designing the verification step properly rather than bolting it on. Explain what you need and why before you ask for it, let people pause and resume without losing progress, and never dead-end someone whose document scan fails. We have written about what that sequencing does to activation in our fintech onboarding piece, and it applies to any regulated product here.

How people pay

Card penetration is high and Apple Pay is common, so the basics are covered. What differs is the long tail. Cash on delivery still has a real share in ecommerce and dropping it can cost you customers rather than save you cost. Buy now, pay later is mainstream here rather than niche. And bank transfer remains a normal way to settle a large invoice in a way it is not in the US.

Currency and pricing need care as well. Show AED as the primary currency, and if you sell across the Gulf, be explicit about which country a price applies to rather than assuming the reader will work it out.

WhatsApp is a primary channel

In the UK or the US, WhatsApp is a consumer messaging app. Here it is where business happens, including with people you have never met. A product that offers only email support, or that buries a contact form three clicks deep, is reading as unreachable to a large part of its audience.

This affects design, not just operations. Plan for a WhatsApp entry point that is visible without being desperate, decide what happens when someone messages outside working hours, and make sure the handover from an automated reply to a human is obvious. Half the region's buying conversations start in a thread, not in a form.

The calendar is not the one you designed for

The UAE weekend is Saturday and Sunday, with Friday afternoons quiet for prayers. Some neighbouring markets still run a Friday and Saturday weekend, so a regional product cannot assume one pattern.

Ramadan changes working hours, shopping behaviour and the times people are active in an app, for a month, every year, on a date that moves. If your product has scheduling, delivery windows, business hours or campaign timing in it, that logic needs to handle a shifting calendar rather than a hardcoded one. Hijri dates also appear alongside Gregorian in government and some financial contexts.

Imagery, tone and who you are actually talking to

The UAE audience is mostly not Emirati. It is one of the most international populations anywhere, so imagery that shows only one nationality gets the market wrong in either direction. Photography should reflect that mix honestly rather than defaulting to stock shots of skylines and men in kanduras.

On tone, business communication here is warmer and more formal than the clipped startup voice that plays well in San Francisco. Greetings matter. Bluntness that reads as efficient in London can read as rude here. That is a copy decision as much as a design one, and it belongs in the design system rather than being left to whoever writes the microcopy last.

What we do first on a Gulf product

• Design one core screen in Arabic and English side by side before the design system is locked.
• Audit every form for name, address, phone and postcode assumptions.
• Decide the identity and verification path early, including UAE Pass, rather than treating it as an integration detail.
• Map the payment methods to the actual audience, not to the ones easiest to implement.
• Put a real WhatsApp path into the design and define what happens on the other end of it.
• Check every date, weekend and business-hours assumption in the product against a moving calendar.