Designing for two directions without designing twice
Designing a bilingual UAE site is not a matter of flipping the layout. Arabic type has different vertical proportions and no capital letters, so a hierarchy tuned for English reads flat in Arabic; some elements should mirror and some must not; and a design system built for both directions from the start costs far less than two designs maintained in parallel.
The instinct when a UAE client asks for an Arabic version is to mirror the design. It is the right instinct and an incomplete one. Mirroring handles the direction of the page and none of the things that actually make an Arabic layout feel designed rather than converted, the way the type sits, where the eye enters a composition, which elements carry meaning by pointing and which merely happen to point. Getting this right is a design problem, and treating it as a stylesheet problem is why so many Arabic pages look like an afterthought even when considerable effort went into them.
Arabic and Latin type do not occupy space the same way. Arabic has no uppercase, so the size and weight contrast that carries hierarchy in an English design has to be rebuilt from different materials. Its letterforms sit differently against the baseline and need more line height to breathe, so a layout with vertical rhythm tuned to Latin text produces Arabic paragraphs that feel cramped. Then there is what should and should not mirror: navigation and reading order should, a play button should not, a logo usually should not, and a photograph of a person facing into the page should be considered rather than flipped. A blanket mirror gets some of these wrong every time.
When this work makes sense
Questions worth asking any supplier
Has the designer worked in Arabic before, and can they show you a layout in it? Not a mirrored mockup, an Arabic page where the hierarchy was designed in Arabic.
Does the type scale account for Arabic's vertical metrics, or is it a Latin scale with an Arabic font substituted into it?
Is there a documented rule for which elements mirror and which do not? Without it the decision gets made inconsistently by whoever is building that component.
Do your brand guidelines cover Arabic type at all? Most do not, and that gap becomes a series of improvised decisions.
Is this one design system with a direction setting, or two designs? The second is cheaper today and more expensive every month afterwards.
Deliverables
A single design system with direction as a property, delivered as components rather than two sets of page mockups
Type scale developed against Arabic and Latin together, so hierarchy survives in both
Arabic font selection with fallbacks tested at real sizes rather than chosen from a specimen
A documented mirroring rule, what flips, what does not, and why, for whoever builds the next page
Imagery direction and selection considered for the local audience rather than licensed from a global library and hoped for
Key templates designed in both directions and reviewed side by side before build
Handover that a developer can implement without asking what was meant
Built with
Process
We design the hardest page in Arabic first, before any English mockup is approved. Usually that is a dense one, a property listing, a service page with long headings, a form. Designing it in Arabic first exposes the decisions that a Latin-first process defers until they are expensive: whether the type scale holds, whether the navigation pattern survives mirroring, whether the card layout works when the text is longer and the hierarchy cues are different. Whatever survives that page becomes the system. The English version is then derived from it rather than the other way round.
The standard nine stages, discovery, strategy, UX/UI, development, content and SEO, testing, launch, measurement and continuous improvement, apply to every project. The paragraph above is what differs for this one.
What moves the number
Pricing depends on scope, functionality, integrations and content requirements. These are the factors that change it most:
Three ways to approach a bilingual design
Design in English, mirror for Arabic
Fits: Sites where Arabic is a small subset, a few pages rather than a parallel site
Limits: Hierarchy and spacing are inherited from decisions made for a different alphabet, and it shows on every dense page
One system, both directions
Fits: Most bilingual UAE sites, and the only approach that stays coherent as the site grows
Limits: Slower to the first approved mockup, because the hard decisions are taken at the start rather than deferred
Two separate designs
Fits: Cases where the Arabic audience is genuinely a different proposition, not a translation
Limits: Two design systems to maintain; they drift within a year and the brand stops being one brand
Case studies
No published UAE design case study yet. Our Dubai office is in Standard Chartered Tower, Downtown Dubai. Client work will be published when we have permission to name the business and show the work itself.
MBGDesk operates from 4 offices in India, United States, United Kingdom, United Arab Emirates. We hold no industry certifications and do not imply otherwise.
Frequently asked questions
Can you just mirror our existing English design?
We can, and we will show you what it looks like so the decision is informed. Mirroring handles direction and not hierarchy. On a simple page the result is acceptable; on a dense one the Arabic reads flat, because the size and weight contrast carrying your hierarchy was built on a distinction Arabic does not have.
Why does our Arabic text look cramped?
Almost always line height. Arabic letterforms extend further above and below the baseline than Latin ones, so a line height that looks generous in English is tight in Arabic. It is a small change with a disproportionate effect on whether a page feels considered.
Which elements should not be mirrored?
Media controls, anything showing a real-world direction, most logos, numerals in some contexts, and images where flipping would alter their meaning or make text within them backwards. The list is short, and the point of writing it down is consistency, otherwise each component gets decided separately by whoever builds it.
Do we need a special Arabic font?
You need one chosen deliberately and licensed for the use. Latin fonts with an Arabic companion vary widely in quality, and a mismatched pairing is one of the clearest signals that the Arabic side was an afterthought. We test candidates at real sizes in real layouts rather than choosing from a specimen sheet.
Our brand guidelines do not cover Arabic. Is that a problem?
It is a gap rather than a problem, and it is worth filling once rather than improvising repeatedly. We can extend your guidelines to cover Arabic type, hierarchy and the mirroring rules, which gives everyone who works on the brand afterwards something to follow.
How do you handle imagery for this market?
Deliberately. The UAE audience is genuinely mixed, and stock imagery that reads as generic Western marketing lands poorly with part of it while overtly local imagery can misfire with another part. It is a judgement to make explicitly with you rather than a rule we apply on your behalf.
Do you do the build as well?
Yes, and the design is handed over in a form a developer can implement either way. Our UAE web development page covers the architecture side, which is the other half of getting a bilingual site right.
Services that connect to this
Talk to us about this
Tell us what you are trying to build and we will come back with scope, approach and an estimate.