UI/UX Design in Dubai for Bilingual Arabic-English Products, Fintech, Hospitality and Government

ZTABS designs digital products for Dubai companies. We are remote-first by design, with an office in Houston, Texas.

Dubai's digital market is distinctive because it combines Arabic-English bilingual requirements, luxury brand expectations, advanced government digitisation and multiple regulatory regimes within one city. Dubai users interact with products from Careem (the ride-hailing platform, designed for Middle Eastern users), Noon (the regional e-commerce platform), Dubai Now (the government super-app), Emirates NBD (one of the largest banking groups in the region) and Talabat (food delivery). These products demonstrate that Arabic-English digital products can be world-class. Our broader UI/UX design capabilities are on the UI/UX design services page, and planning benchmarks are in the UI/UX design cost guide.

Dubai design operates within a unique regulatory landscape. Multiple regulatory regimes: mainland Dubai (UAE federal and Dubai emirate laws), DIFC (DFSA regulation of financial and ancillary activities, with its own data protection framework) and DMCC, JAFZA and other free zones each have specific licensing requirements. Products serving users across these zones must accommodate different compliance patterns. Arabic is a constitutional language of the UAE. Many products serve audiences across the GCC (Saudi Arabia, Kuwait, Bahrain, Oman, Qatar) and broader MENA region, requiring design that scales across Arabic-speaking markets with different dialects and cultural preferences.

Dubai UI/UX design at a glance

Arabic-English bilingual and RTL design

Arabic-English bilingual design is a structural discipline. RTL layout applies directionally per component: navigation direction, form label alignment, table column order and progress indicator direction are adapted for RTL where appropriate. Directional icons (arrows, chevrons, sliders) are mirrored, but non-directional icons (home, settings, search), charts, contextual numbers within Arabic text, Latin strings and media retain their original orientation. Numbers in Arabic text remain LTR (left-to-right), creating mixed-directionality content (BiDi) that requires careful handling. Arabic typography needs different sizing considerations; test actual Arabic strings at target sizes rather than assuming a fixed enlargement percentage. Line height and spacing follow different rules. Professional Arabic type selection matters for brand perception.

Dubai's diverse international population means many products are English-primary with Arabic as a required language for certain audiences. Other products (government services, Islamic banking) are Arabic-primary. Whether a product is designed Arabic-first, English-first with professional translation, or through parallel bilingual design depends on the product's primary audience and content requirements. Language switching must be seamless and preserve user context, scroll position and form state. Professional Arabic linguistic review is separately scoped as part of the engagement.

Fintech and hospitality design

Dubai fintech UX addresses Islamic banking interfaces (products structured under Shariah principles including Murabaha, Ijara and Wakala, which create different transaction flows from conventional banking), conventional banking and wealth management, payment platforms and digital wallets, and investment platforms serving regional investors. DFSA requirements apply to entities carrying on financial or ancillary services activities in DIFC; the SCA regulates mainland securities and commodities activities. The specific obligations depend on the entity's licence, domicile and activities.

Luxury hospitality UX in Dubai demands exceptional production quality. Booking experiences must communicate the property's brand through visual design, typography and micro-interactions. Guest service platforms (room service, concierge, spa booking, restaurant reservations) should support the languages relevant to the property's guest demographics. Loyalty programme UX must make tier progression, points balance and redemption options feel exclusive. Every loading state, error message and empty state must meet the same quality standard as the physical property.

How Dubai UX design delivery works

Our design methodology for Dubai projects combines bilingual design, cultural sensitivity and regulatory awareness.

Discovery (2 to 3 weeks, illustrative) involves user research with representative participants from the target audience (Emirati, Arab expatriate, South Asian, Western expatriate and other demographics as relevant), competitive analysis against regional leaders, regulatory requirements mapping (DIFC, mainland, other free zones as applicable) and Arabic UX content strategy. Research captures insights in participants' preferred language.

Design and prototyping (4 to 8 weeks, illustrative) produces bilingual design systems: component library in Figma with LTR and RTL variants, Arabic and English typography systems, design tokens for both directions, responsive behaviour, and accessibility specifications. Interactive Figma prototypes in both Arabic and English for stakeholder review and usability testing.

Our usual stack: Next.js and React with i18n and RTL support, Node.js for backend services, Tailwind CSS with RTL utilities, and Storybook for component documentation. Technology choices depend on the client's existing stack.

Cost and timeline benchmarks

These are planning benchmarks from our published UI/UX design cost guide in USD.

These are scope-based benchmarks. Arabic-English bilingual design with RTL support adds to design effort for dual-direction design, testing and Arabic content. Dubai's 0% personal income tax environment affects employment cost calculations but not project pricing benchmarks. See the full cost breakdown.

Choosing a design partner for Dubai projects

This comparison is for a 25-screen SaaS application with two rounds of user research, design system, clickable Figma prototype and developer handoff. Rates reflect 2026 generic mid-market US/EU benchmarks from our published cost guide.

RTL design system methodology

Building a bilingual Arabic-English design system requires systematic treatment of directional components. Layout: CSS logical properties (margin-inline-start, padding-inline-end) replace physical properties (margin-left, padding-right) so the layout automatically adapts to text direction. Icons: directional icons (arrows, chevrons, progress indicators, sliders) must be mirrored for RTL; non-directional icons (home, settings, search) remain unchanged. Typography: separate type scales for Arabic and Latin scripts, with Arabic sizing validated through actual string testing at target sizes. Arabic fonts require careful selection for brand consistency and readability across weights. Shadows and elevation: in LTR contexts, light source convention is typically top-left; in RTL, this should be reconsidered for visual consistency.

Form design in RTL contexts: labels right-align where the form language is Arabic, but actual field content follows its own directionality (numeric input, phone numbers, credit card numbers and Latin strings remain LTR even within an RTL form). The logical DOM and focus sequence follows the visual reading order of the active language direction, with tab order validated through testing. Calendar components should support Hijri and Gregorian calendars where the product audience requires both systems. Address forms must accommodate Arabic address structures (which differ from Western address formatting).

Data tables in bilingual applications: column order adapts to the active language direction where columns follow a reading-order sequence, sort indicators mirror directionally, and text alignment within each cell follows the content language of that cell. Mixed-content cells (containing both Arabic and English text or numbers) require careful BiDi handling; numeric and Latin data columns may retain LTR alignment even in an RTL table context. Export and print layouts must respect the active language direction.

Industry-specific design considerations for Dubai

Dubai's real estate and PropTech sector drives demand for off-plan sales platforms (visualising properties under construction with floor plans, renders and payment schedules), tenant portals, property management tools and brokerage platforms. Real estate UX must accommodate international buyers unfamiliar with UAE property ownership structures (freehold vs leasehold, designated areas for non-GCC nationals).

Products designed for GCC-wide distribution from Dubai must accommodate Saudi, Kuwaiti, Bahraini, Omani and Qatari users whose Arabic dialect preferences, payment methods and regulatory contexts differ. The design system should be structured for regional expansion without requiring redesign for each market.

Accessibility and mobile design patterns

Accessibility for Dubai products addresses a diverse user base. Multi-language accessibility requires screen reader support for both Arabic and English content, with proper language attributes on each content block so screen readers switch pronunciation correctly. RTL accessibility: focus order follows the logical DOM sequence, which should match the visual reading order of the active language direction; tab navigation through form fields follows this logical order, and non-directional components (media players, numeric keypads) retain their standard focus sequence. Aria-live regions must announce content changes in the correct language. Colour contrast requirements apply equally in both language directions.

Mobile design for Dubai addresses the high mobile penetration across the UAE's diverse population. Mobile UX considerations include: Arabic keyboard integration (the Arabic soft keyboard layout affects typing speed and common error patterns), thumb-zone optimisation for RTL interfaces, performance optimisation for users on varying network conditions, and offline-capable patterns for applications used in areas with intermittent connectivity. Location-aware design for Dubai: geolocation features (store finders, service areas, delivery zones) must work within Dubai's addressing conventions, which differ from Western street-address systems. Government and regulatory compliance patterns must work seamlessly on mobile, not just desktop, given the mobile-primary behaviour of UAE users.

When ZTABS is not the right fit

• You need daily in-person collaboration in Dubai for the duration of the project. We are remote-first for ongoing design work. Stakeholder workshops can be conducted remotely as agreed during scoping.
• You need Arabic copywriting or editorial services. We design bilingual frameworks; Arabic content creation can be separately scoped or provided by qualified linguists.
• You need DFSA, SCA or mainland licensing legal counsel. We design regulatory-aware interfaces. Compliance should be guided by qualified UAE counsel.
• You need marketing, branding, creative or advertising services beyond product interface design. These can be separately scoped; see our digital marketing services.

Risks and how we address them

Post-design considerations

After design delivery, the product moves to implementation. Bilingual design systems include RTL and LTR component specifications. RTL CSS must be validated during development: common implementation errors include directional icons not mirroring, progress bars not reversing, and margin/padding direction errors. For fintech products, regulatory disclosures must be maintained as requirements change across DIFC, mainland and other zones. Ongoing design maintenance can be scoped as a retainer engagement. Phase plans are illustrative and agreed during scoping.