UI/UX Design in Doha for Arabic-First Digital Products and Bilingual Interfaces

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

Doha's fundamental UX challenge: creating digital experiences that work beautifully in Arabic. A common approach to Arabic UI is mirroring English designs. The result can be interfaces that technically render in Arabic but feel less natural to Arabic-speaking users. Arabic is not mirrored English. Arabic text flows right-to-left, but numbers within Arabic text flow left-to-right. Arabic characters connect to each other, with each character having up to four forms (initial, medial, final, isolated). Arabic line heights differ from Latin. Arabic typographic traditions emphasise calligraphic beauty. Arabic-first design inverts the typical Western agency approach and, for Arabic-targeted products, tends to produce better Arabic interfaces. Our broader capabilities are on the UI/UX design services page, and planning benchmarks are in the UI/UX design cost guide.

Qatar's digital context includes premium expectations (Qatar's national aesthetic, from Hamad International Airport to the National Museum, is modern, elegant and world-class; generic-looking digital products are perceived as untrustworthy), mobile-first reality (Qatar has high smartphone penetration), and government and enterprise formality requirements. Qatar Financial Centre (QFC) registered entities operate under the QFC framework; QFCRA regulates financial activities of QFC-licensed firms. The National ATM and POS Switch (NAPS) operates Qatar's ATM and POS switching infrastructure; QMP (Qatar Mobile Payment) is a separate mobile wallet system.

Doha UI/UX design at a glance

Arabic-first banking and government UX

Banking UX for Doha addresses trust perception (banking interfaces must communicate security through design), complex financial information display (portfolios, transaction histories, statements in both Arabic and English with correct number formatting), Islamic banking product presentation (Murabaha, Ijara, Sukuk presented clearly to customers who may be unfamiliar with Islamic finance terminology while maintaining Sharia compliance in the information presented), and biometric integration (fingerprint and face recognition login flows and transaction confirmation). QFC-registered entities operate under the QFC regulatory framework; QFCRA regulates specified financial activities within the QFC. National banks operate under Qatar Central Bank (QCB) supervision. The specific regulatory requirements depend on the entity's registration/licence status and activities.

Government digital services UX addresses accessible bilingual design (Arabic and English versions that both feel native), complex multi-step workflows (applications, approvals, renewals), form design for extensive government data collection (QID, address, employer, family details), and WCAG 2.1 AA accessibility for Arabic interfaces where screen reader support and keyboard navigation have different requirements than English.

Arabic typography and bidirectional design

Arabic typography for screens uses typefaces optimised for digital readability. Arabic body text typically benefits from larger minimum sizes than Latin equivalents (Arabic characters are visually more complex), taller line height (accommodating diacritical marks and connected letter forms) and careful attention to font rendering. Arabic is a connected cursive script; generic letter-spacing adjustments can break character connections. Actual sizes and spacing should be tested with the chosen Arabic typeface on target devices. RTL layout is designed from the ground up, not mirrored from LTR. Key differences: navigation flows right-to-left, icon positioning follows Arabic reading direction, progress indicators move right-to-left. But elements with universal directionality remain unchanged: media playback controls, mathematical symbols, phone number entry and credit card input remain LTR. Getting mixed-direction elements right is one of the most common failures in Arabic UI design.

Number formatting in financial interfaces must be standardised. Customer research in the Gulf typically confirms that banking customers prefer Western Arabic numerals (0123) for financial amounts even in Arabic mode. Currency positioning adapts per language direction with colour coding and symbols providing redundant visual indication for credits and debits.

How Doha UX design delivery works

Discovery (2 to 3 weeks, illustrative) involves user research with Qatari users (Arabic-speaking, in Arabic to capture natural expressions and mental models), Qatari-specific user personas (not generic Western personas with Arabic names), competitive analysis of comparable GCC digital products, and device and context analysis (smartphone market share in Qatar, usage contexts, connectivity conditions). In-person research sessions can be arranged with agreed researcher availability and client/facility permission.

Design and prototyping (4 to 6 weeks, illustrative) produces Arabic-first design systems: every component designed in Arabic and English variants, Arabic typography tokens separate from English (different font families, sizes, line heights and weights), RTL layout designed from the ground up, colour and visual design matching Qatar's premium aesthetic, and iconography reviewed for cultural appropriateness and directional correctness.

Our usual stack: Next.js and React with RTL support, Node.js for backend services, Tailwind CSS with CSS logical properties for bidirectional design.

Cost and timeline benchmarks

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

These are scope-based benchmarks. Arabic-first bilingual projects add to design effort for dual-direction design, Arabic typography, Arabic usability testing and bidirectional component development. See the full cost breakdown.

Choosing a design partner for Doha 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.

When ZTABS is not the right fit

• You need daily in-person collaboration in Doha for the duration of the project. We are remote-first for ongoing design work. Stakeholder workshops can be conducted in person or remotely as agreed during scoping.
• You need Arabic UX content creation or calligraphic design beyond the engagement scope. Professional Arabic UX writing can be separately scoped with qualified Arabic linguists.
• You need QCB or QFCRA compliance counsel. We design regulatory-aware interfaces. Financial compliance should be guided by qualified counsel familiar with Qatar's regulatory framework.
• You need marketing, branding, creative or advertising services. We design product interfaces. Marketing and creative services can be separately scoped; see our digital marketing services.

Risks and how we address them

Accessibility and privacy design patterns

Doha's emerging accessibility expectations align with WCAG 2.1 AA. Arabic accessibility has specific requirements: screen reader navigation in Arabic reading order (right-to-left, top-to-bottom), Arabic accessibility labels that read naturally (not translated from English technical labels), keyboard navigation following RTL conventions, and colour contrast verified for Arabic typography at required sizes.

Qatar's data protection framework applies to organisations processing personal data in Qatar; the national Personal Data Privacy Protection Law and any sector-specific requirements depend on the entity, its data processing activities and the data subjects involved. For QFC-registered entities, the QFC Data Protection Regulations apply to personal data processing within the QFC framework. Interface patterns include clear data collection notices, consent management and data subject rights workflows, assessed for the specific entity and processing activities.

E-commerce, enterprise and healthcare UX

E-commerce UX for Doha addresses Arabic product browsing (RTL product grids, Arabic search with morphological awareness, Arabic filter labels and bidirectional product names with Arabic and English in the same name), checkout optimisation (reducing cart abandonment by addressing address format confusion, payment method presentation and delivery expectation setting), and mobile-first shopping (designing for Qatar's mobile-dominant e-commerce traffic). The specific payment methods, delivery options and consumer protection requirements depend on the merchant's location and the applicable commercial regulations.

Enterprise UX for Qatari organisations addresses data-dense dashboards (enterprise users needing information density with functional, scannable layouts presenting maximum data while remaining usable), workflow interfaces (multi-step business processes including approvals, reviews and submissions designed for efficiency, measured by how few interactions are needed to complete a task) and role-based design (different user roles needing different interfaces, with executive dashboards distinct from data entry screens, each optimised for its specific use case). Arabic enterprise UX uses formal speech register and professional typography matching institutional communication standards.

Healthcare UX for Qatar addresses bilingual Arabic-English health interfaces, patient portals, telemedicine platforms and health information systems. Cultural sensitivity in health UX includes appropriate visual communication of medical information, privacy controls for health data and accommodation of family-centred healthcare decision-making common in Gulf culture. The specific health data regulations and professional standards depend on the healthcare entity, the data types and the applicable Qatar health authority requirements.

Questions to ask any Doha UX design partner

Before selecting a design partner for Qatari products, verify their capability. Ask about Arabic-first: do they design Arabic as the primary language, or design English then translate? Ask about typography: do they select Arabic typefaces for screen readability, not just to match the English typeface? Ask about bidirectional: do they handle mixed-direction elements (numbers in Arabic text, media controls, credit card input) correctly? Ask about testing: do they test with Arabic-speaking users in Doha? Ask about accessibility: do they provide Arabic screen reader support with meaningful Arabic labels?

Post-design considerations

After design delivery, the product moves to implementation. Arabic-first design systems include separate Arabic and English typography tokens, bidirectional component specifications, RTL CSS logical property documentation and Arabic accessibility annotations. For banking products, QCB or QFCRA regulatory disclosures must be maintained as applicable. Ongoing design maintenance can be scoped as a retainer engagement. Phase plans are illustrative and agreed during scoping.