Product Design Company in Dubai

The structural cost driver is how much of the product has to work identically in two scripts, and the second is how much research is genuinely needed rather than assumed. A focused product design engagement covering bilingual research, core flows, an interface in both languages, a clickable prototype and a specification package typically runs six to ten weeks. A design system build, meaning a token architecture, a component library with bilingual variants, motion and accessibility documentation and a Storybook handover, is usually a parallel or follow-on engagement of similar length depending on how many components the product actually has rather than how many it wishes it had. A regulated product adds consent and disclosure design, dual-calendar patterns and an accessibility conformance pass. Remediation of an existing product is scoped only after an audit, because the honest answer to what it costs to fix an interface depends entirely on whether it was built on tokens. We quote fixed fee in AED against a written scope with the 5 percent UAE VAT itemised separately, and our rate reflects delivery from Edmonton and Chandigarh rather than a Dubai studio's overhead.

It means the Arabic interface is authored alongside the English one in the same file on the same tokens, and that the harder of the two constraints wins rather than the more familiar one. Direction lives in a token and a document attribute, so logical properties handle inline-start and inline-end and every component built afterwards inherits correct behaviour without a mirrored stylesheet. Icons that carry direction, meaning back arrows, progress indicators, chevrons and anything implying forward motion, get mirrored variants, while icons that do not, such as a clock or a logo, must not be mirrored. Motion direction reverses. The type ramp is set on the Arabic face first because Arabic needs more line height than a Latin-calibrated ramp allows, and the Latin face is chosen to sit with it rather than the reverse. Layouts are sized against real Arabic content, since Arabic strings routinely differ in length from their English equivalents and a component that fits in English can break in Arabic. Bidirectional handling is explicit, because an IBAN, a reference number, a Latin brand name or an email address inside an Arabic sentence renders in the wrong order without it. Numerals may display as Arabic-Indic while storage stays canonical.

As a first-class part of the design system rather than an annual scramble. Dual-calendar date display is the baseline pattern: Gregorian and Hijri shown together, with which one leads depending on the audience and the task, and a date picker that lets a user work in whichever calendar they think in without doing conversion arithmetic themselves. Hijri dates depend on the calculation or sighting convention in use and can differ by a day between sources, so we design the interface to be explicit about the convention rather than presenting a single date as though it were unambiguous, and we treat that as a product decision to be made with you rather than a default we impose. The Ramadan and Eid periods reshape user behaviour substantially in this market, with activity shifting later into the evening and content and promotions changing character, so we build seasonal theming as a token layer with date-driven switching rather than as a parallel set of screens someone has to maintain. Prayer-time-aware behaviour, where a product genuinely benefits from it, is designed as a user preference rather than an assumption applied to everyone.

We work to WCAG 2.1 AA as the baseline standard and treat it as a design requirement rather than an audit performed at the end, because the failures that are expensive to fix are structural. In practice that means contrast checked on the real palette during design rather than on a swatch, a heading and landmark structure that makes sense when read linearly, keyboard operation with a focus order that is correct in both directions, states that do not rely on colour alone, target sizes that survive one-handed use, and motion that respects a reduced-motion preference. Screen reader testing is done in both languages, because Arabic screen reader behaviour differs from English and a component that announces correctly in one may not in the other. One clarification worth making, since it is frequently repeated incorrectly: the Dubai Universal Design Code is a Dubai Municipality code concerned with accessibility in the built environment, and it is not a web accessibility standard. Where a public-facing or government-adjacent product is in scope, the digital accessibility expectations come from the relevant authority's own requirements, and we ask your team for the specific control set they are assessed against during discovery rather than assuming one.

By recruiting to the actual composition of the audience rather than to convenience, and by being honest in the findings about what the sample supports. The UAE population is overwhelmingly expatriate, which means a single English-speaking persona misses most of the people who will use the product. Our discovery typically runs three or more separate research streams: Emirati and wider Arab users, South Asian users, and Filipino and other communities, with the exact split set by your product's real audience rather than a template. Participants are screened for the behaviour that matters rather than for demographics alone, and sessions run in the participant's preferred language with a moderator or interpreter who works in it. Sessions are remote and moderated, recruited through panel providers, and we tell you the sample size, the screening criteria and the recruitment source in the write-up so you can weigh a finding appropriately. Where the data shows genuine divergence between groups we design locale-specific flows; where it does not, we resist the temptation to fragment the product, because divergence without evidence produces variants nobody maintains.

It reaches into the interface more than teams expect, and the first question is which regime applies to you, because that depends on your licence rather than your location. An entity licensed onshore or in a non-financial free zone falls under Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data, which came into force on 2 January 2022, with the UAE Data Office as regulator. An entity licensed in the Dubai International Financial Centre sits under DIFC Law No. 5 of 2020 instead, and an entity in Abu Dhabi Global Market under the ADGM Data Protection Regulations 2021. These are separate regimes and treating them as one is the most common error we correct. On the federal law we add a caveat rather than a deadline: the executive regulations that fill in much of the operational detail should be confirmed with your UAE counsel before you treat any specific compliance date as settled. What we design regardless is honest consent, meaning granular per-purpose choices, nothing pre-checked, refusal as easy as acceptance, and no interface pattern engineered to make the privacy-protective option harder. Data subject rights need a real route in the product, not an email address, and cross-border transfer needs a plain-language notice in both languages.