Status: operational Projects: 120+ Reply: < 0 to 1 hour

Blog / Design

Modern Arabic / RTL UI Design in Dubai — What "Properly Bilingual" Actually Means

Most "bilingual" Dubai websites just flip the text direction and call it done. What properly bilingual Arabic/English UI actually requires — mirroring, typography, numerals, and the details that separate native from translated.

June 3, 2026 · 4 min read min read · by DevGator Team

Most "bilingual" Dubai websites aren't bilingual — they're an English site with the text translated and the direction flipped, and it shows. Arabic users can tell within seconds when a site was built English-first and bolted Arabic on, because the details are wrong: icons point the wrong way, the layout doesn't mirror, the Arabic typography is an afterthought, and the whole thing feels translated rather than native. Properly bilingual means the Arabic experience is designed, not converted. Here's what that actually involves.

RTL is mirroring, not just text alignment

Right-to-left isn't "right-align the text." The entire interface mirrors. In a proper RTL layout, navigation flows right-to-left, the logo sits on the right, progress steps move right-to-left, "next" and "back" arrows flip direction, sliders and carousels reverse, and visual hierarchy reads from the top-right. A site that only flips text direction but keeps the layout left-to-right feels broken to an Arabic reader — like reading a book where only the words were translated but the page layout stayed foreign.

Directional icons need attention: arrows, chevrons, back buttons, and anything implying direction must flip. But not everything mirrors — logos, media playback controls, and certain universal icons stay as-is. Knowing which is which is the difference between native and amateur.

Arabic typography is its own discipline

You cannot take an English layout's type system and pour Arabic into it. Arabic script has different needs:

  • Line height — Arabic letterforms need more vertical breathing room; English line-heights crush them.
  • Font choice — a good Arabic web font (the script has its own typographic tradition) matters as much as the Latin one. Pairing a quality Arabic font with the Latin font, weights matched, is real design work.
  • Font size — Arabic often needs to be set slightly larger than Latin at the same visual weight to read comfortably.
  • No fake bold/italic — Arabic doesn't italicise the way Latin does; faux styles look wrong. Use proper weights.

Loading both font families also has a performance cost — subset and use font-display: swap so neither language's text stays invisible while fonts load.

Numerals, dates, and mixed content

Arabic uses its own numeral forms in some contexts and Western (Arabic) numerals in others — the right choice depends on audience and content. Dates, currency (AED), and phone numbers need handling that suits the reader. And mixed-direction content — an Arabic sentence containing an English brand name or a number — needs proper bidirectional text handling, or it scrambles visually. This is where rushed bilingual sites fall apart most visibly.

Architecture, not just appearance

Properly bilingual is also a structural concern: parallel URL structure (/ar/...), hreflang tags so Google serves the right version, a clean language switcher that remembers the choice, and translated (not machine-generated) content. Build it RTL-aware at the template level and switching languages is seamless; retrofit it and every page is a fight.

The "feels native" test

The mark of a properly bilingual site: an Arabic-first user navigates it without ever feeling they're using a translated version. The layout reads naturally right-to-left, the typography is comfortable, the icons point the right way, nothing is awkwardly mixed-direction, and the language switch is instant and complete. If an Arabic user can tell it "was originally English," it isn't properly bilingual — it's English with a translation layer.

Why it's worth doing right

In Dubai, a genuinely bilingual site signals you take the local market seriously, and it converts the Arabic-preferring segment that an English-first site quietly loses. It's a competitive edge precisely because so many competitors do it badly. Done right, it's not double the work — it's design that accounts for both audiences from the start.

This is core to how we build for the local market. See our web development, or send your site on WhatsApp and we'll tell you whether your Arabic experience is native or bolted-on.