A UX design partner in the UAE, with the work to prove it.
We have delivered seven luxury property experiences in Dubai, including for Omniyat. That means Arabic RTL done properly, an understanding of how Gulf buyers actually evaluate, and a working timezone rather than a nine-hour lag.
What working in the UAE actually requires
Arabic is not a translation task
RTL mirrors layout, but numerals stay left-to-right, directional icons each need a decision, and the visual centre of gravity shifts. A mirrored English site is instantly recognisable to a native reader — and in a trust-driven purchase, that is disqualifying.
The audience is genuinely multilingual
A Dubai product may serve Emirati, South Asian, European and Chinese users in one session mix. Designing for a single assumed reader — in either direction — quietly excludes a large part of the market.
Regulated finance has its own perimeter
DIFC and ADGM operate distinct regulatory regimes with their own onboarding and disclosure expectations. Fintech flows built for an Indian or US regime need genuine rework, not relabelling.
Premium is the baseline, not the aspiration
In Dubai's property and luxury segments, competitors are already presenting at a high standard. Adequate design reads as a downgrade rather than as neutral.
What you actually get
Arabic RTL design
Genuine bidirectional design — layout, numerals, iconography, typography and reading gravity handled correctly rather than flipped with a stylesheet flag.
Luxury property experiences
Immersive project sites and qualification journeys for developers and brokerages, built on the system behind seven Dubai properties.
Regulated fintech flows
Onboarding, KYC and payment journeys designed around DIFC and ADGM expectations, worked through with your compliance team rather than around them.
Multi-market design systems
One system serving Arabic and English without maintaining two parallel design efforts — the difference between a manageable product and a doubling of cost.
Enterprise and government-adjacent standards
WCAG 2.1 AA accessibility and the documentation standards that surface in UAE enterprise and semi-government procurement.
Same-day collaboration
India to Gulf is a 1.5-hour offset. Full working-day overlap, live calls at normal hours, and no waiting overnight for an answer.
How the engagement runs
Market and language scoping
Week 1. Which languages, which audiences, which regulatory perimeter. Getting this wrong is the most expensive mistake available in a UAE project.
Structure
Weeks 2–3. Architecture and flows designed bidirectionally from the start, because retrofitting RTL is substantially more expensive than designing for it.
Design
Weeks 3–8. Visual design in both directions, reviewed against the standard the local competitive set is already setting.
Handover
Ongoing. Specs covering both language directions, with the RTL rules documented so your engineers are not guessing.
Proof
Rcentric — seven Dubai properties
Digital experiences for Omniyat, LIV Residences, Orla Infinity, Opus, Anwa Aria, Ela and Vela Viento. Qualified leads rose 3x, with 100% client retention across the portfolio. Read the full case study →
Related work
See the Rcentric case study, our PropTech practice, and our guide to Arabic RTL design.
What it costs
How UAE engagements run
Quoted in USD or AED. Bilingual projects carry genuine additional scope — roughly a third more design work than a single-direction equivalent — and we scope for that upfront rather than raising it midway. See the pricing page.
Typical timeline
A single property experience runs 6–8 weeks; bilingual product work is typically 10–12.
Common questions
Actual experience. We designed seven luxury property experiences in Dubai through Rcentric, including work for Omniyat, with a 3x increase in qualified leads across the portfolio. That is the only UAE claim we make — we are an India-based studio serving UAE clients, not a Dubai-registered agency, and we would rather say that plainly than imply a local office we do not have.
By designing bidirectionally from the start rather than mirroring at the end. Layout flips, but numerals remain left-to-right, directional icons each need an individual decision, Arabic typography has different vertical rhythm and line-height needs, and the visual entry point of every screen moves. We document these rules in handover so engineering is not making judgement calls.
Yes. Both operate distinct regulatory regimes with their own onboarding, disclosure and record-keeping expectations, so fintech flows designed for another jurisdiction need genuine rework rather than relabelling. We work directly with your compliance team from week one, because designing first and seeking approval later is how these projects overrun.
India is 1.5 hours ahead of Gulf Standard Time, so we share essentially the entire working day. Live calls happen at normal hours for both sides, and you are not waiting overnight for a response — which is the practical difference between a Gulf-adjacent partner and a US or European one.
Yes. Our delivered work is concentrated in Dubai, but the design considerations — bilingual audiences, RTL, premium expectations, Gulf regulatory context — carry across Abu Dhabi, Saudi Arabia and the wider GCC. Market-specific conventions differ and we scope for that.
That is the efficient approach and what we recommend. A single bidirectional system with direction-aware tokens and components costs meaningfully less to build and far less to maintain than two parallel design efforts, and it prevents the two language versions drifting apart over time.
Building for the UAE market?
Thirty minutes. Tell us what you're launching and we'll tell you what we'd tackle first — including the RTL and localisation work most teams underestimate.