Our Doha UI/UX design process covers research, Arabic-first design, prototyping, testing, and design system creation. Research (weeks 1-2): understanding users and context. User research: interviews and observation with actual users (in Arabic — our researchers conducting sessions in Arabic to capture natural expressions, frustrations, and mental models that would be lost in English). User personas: defined with Qatari-specific characteristics (not generic Western personas with Arabic names). Competitive analysis: reviewing comparable Qatari and GCC digital products — understanding the design landscape and identifying opportunities to differentiate. Device and context analysis: understanding how users will interact with the product — which devices (iPhone vs. Samsung vs. Huawei market share in Qatar), which contexts (office, field, home, commuting), and which connectivity conditions (Qatar has excellent 5G coverage but some indoor environments still have connectivity issues). Arabic-first design (weeks 2-4): designing the interface with Arabic as the primary language. Typography: selecting Arabic typefaces that are both beautiful and functional on screens. We prefer: Noto Naskh Arabic (excellent readability, comprehensive character coverage, open-source — consistent rendering across devices), IBM Plex Arabic (modern, professional — suitable for enterprise and government), and custom Arabic typefaces for brands that want distinctive Arabic typography. Type hierarchy: Arabic heading sizes, body text sizes, and line heights optimized for Arabic reading patterns — not Latin metrics applied to Arabic text. Arabic body text typically requires: larger minimum size (16px vs. 14px for Latin — Arabic characters are more complex and need more pixels to be legible), taller line height (1.8-2.0× vs. 1.5× for Latin — Arabic characters have more vertical extent with diacritical marks), and more generous letter spacing (Arabic characters connect, and too-tight spacing makes words difficult to parse). Layout: RTL layout designed from the ground up — not a mirrored LTR layout. Key differences: navigation flows right-to-left, icon positioning follows Arabic reading direction, progress indicators move right-to-left, and tables read right-to-left. BUT: elements with universal directionality remain unchanged — media playback controls, mathematical symbols, phone number entry, and credit card number input remain LTR. Getting these mixed-direction elements right: one of the most common failures in Arabic UI design. Color and visual design: culturally appropriate color choices — avoiding color combinations with unintended cultural associations. Green and gold: positive associations in Qatari culture. Design aesthetic: modern, clean, premium — matching the visual standards Qatari users encounter in their built environment (the Museum of Islamic Art, the National Library, Education City). Iconography: reviewing every icon for cultural appropriateness and directional correctness (an arrow pointing left means "forward" in RTL — the opposite of LTR convention). Prototyping and testing (weeks 4-6): validating the design with real users. Interactive prototypes: built in Figma with actual Arabic content (not placeholder text — Arabic Lorem Ipsum distorts the design because Arabic text has different visual weight and rhythm than Latin text). Usability testing: conducted in Arabic with Qatari users — testing: task completion (can users complete key tasks without help?), comprehension (do users understand the interface elements, labels, and workflows?), satisfaction (do users find the design professional, trustworthy, and pleasant to use?), and Arabic-specific issues (RTL layout confusing? Arabic text legible? Mixed-direction content handled correctly? Arabic input working properly in forms?). Testing with a range of users: tech-savvy young Qataris (who compare your app to the best global apps), older Qataris (who may be less familiar with digital patterns), and expatriate workers (who may use the Arabic interface despite Arabic not being their first language). Design system (weeks 5-7): creating a comprehensive design system for ongoing development. Component library: every UI component designed in Arabic and English variants — buttons, forms, tables, cards, navigation, modals, alerts, and data visualization. Each component: documented with usage guidelines, spacing specifications, and responsive behavior. Token system: colors, typography, spacing, and shadows defined as design tokens — enabling consistent implementation across web and mobile platforms. Arabic typography tokens: separate from English tokens — different font families, sizes, line heights, and weights optimized for each script. Responsive guidelines: how each component and layout adapts across screen sizes — from 320px mobile to 1920px desktop. Mobile-first: the mobile design is the primary specification, with desktop as the responsive adaptation.