Product Design Company in Abu Dhabi

We price by phase and scope rather than by a headline rate. A discovery and research sprint, including recruiting Abu Dhabi participants across Emirati and major expatriate segments, moderated sessions in Arabic and English, a synthesis report and a prioritised opportunity map, typically runs AED 70,000 to 160,000 over four to six weeks. End-to-end design of a single product surface, meaning one mobile app or one web product with a bilingual design system, full Arabic and English screens, tested prototypes and an implementation-ready handover, typically runs AED 200,000 to 600,000. A multi-surface design system programme covering web, iOS, Android and an internal admin console, with tokens wired to code, a Storybook implementation with RTL variants, accessibility conformance work and a governance model, typically runs AED 600,000 to 1,800,000. Ongoing embedded design capacity is quoted monthly. Delivering from Chandigarh and Edmonton keeps our rate well below the London, Zurich and New York studios that Abu Dhabi enterprises often engage, and below the local rates of the large consultancies, while our Chandigarh team's 1.5 hour offset from Gulf Standard Time removes the review lag that usually makes remote design expensive in rework.

A predictable list, and it is worth knowing before you commit to an English-first build. Layouts hard coded with left and right padding do not mirror, so a retrofit becomes a second stylesheet that immediately drifts from the first. Mixed-direction strings render in the wrong order, which is how you get a phone number reversed or a price showing the currency on the wrong side. Numeral policy is usually never decided, so the product shows Western digits in one place and Arabic-Indic digits in another with no rule. Truncation and ellipsis logic assumes left-to-right, so Arabic strings get cut at the wrong end. Icons mirror indiscriminately, so a back arrow flips correctly and a clock face flips into nonsense. Line height set for Latin clips Arabic diacritics. Fonts fall back to a system Arabic face that has nothing to do with the brand. Form validation messages written for English grammar read as machine translation in Arabic. Focus order in a mirrored layout follows the DOM rather than the visual order. Each of these is cheap to prevent in week one and expensive to fix in month nine, which is why we run the bidirectional audit first.

Deliberately, with quotas, and never with a convenience sample. Abu Dhabi's resident population is roughly 85 percent expatriate, so a research panel drawn from your own staff or from an English-speaking professional network will systematically mislead you about how the product is actually used. We set recruitment quotas across the segments that matter for the product: Emirati nationals, Arabic-speaking expatriates from Egypt, Jordan, Syria and Lebanon whose Arabic dialect and formality expectations differ, South Asian residents from India, Pakistan and Bangladesh, Filipino residents, and Western expatriates. We recruit for device profile too, because a product tested only on recent iPhones will fail on the mid-range Android hardware a large part of the workforce actually carries. Sessions run in the participant's preferred language with a moderator who speaks it, not through a translator, because a translated session loses the hesitation and the misreading that are the useful signal. We also test the Arabic interface with people who habitually use Arabic interfaces rather than with bilingual users who default to English, since the latter will not notice Arabic problems.

It depends on the product, and the wrong answer in either direction causes trouble. Government services, Islamic finance products, HR and leave systems, and anything touching religious observance generally need Hijri dates visible, usually alongside Gregorian rather than instead of it. Consumer commerce, travel and most B2B software generally do not. The engineering detail that trips teams up is that the Hijri calendar is lunar and observational in some determinations, so different Hijri calculation variants produce dates one day apart, and a system that stores a Hijri date as a string rather than storing the underlying instant will eventually produce a mismatch with another system. Our rule is to store the canonical instant and render Hijri as a presentation concern using a documented calculation variant, with the variant recorded so two systems can be reconciled. Design side, a dual date picker needs both calendars visible without doubling the cognitive load, and it needs to handle the case where a user knows the Hijri date but not the Gregorian one. Ramadan also changes working hours and service expectations, which belongs in scheduling and availability design rather than in the date component.

By treating the contract structure as the information architecture rather than as a label on a conventional product. A murabaha is a cost-plus sale, an ijara is a lease, a musharaka is a partnership, and a sukuk is not a bond. If the interface says loan, interest rate and repayment schedule and simply swaps the vocabulary, the product misrepresents itself and the Sharia supervisory board will say so. The design implications are concrete. Profit rate disclosure differs from interest rate disclosure and the comparison the customer wants to make is different. Ownership transfer points in an ijara or diminishing musharaka need to be visible in the journey because they are what the customer is actually buying. Early settlement behaves differently and the screen has to explain it rather than hide it behind a call-us link. Fee structures are itemised differently. And approval flows include a Sharia compliance dimension that has no counterpart in a conventional product. We design these with the institution's product and Sharia teams in the room, and we test comprehension with customers rather than assuming that correct terminology equals understood terminology.

We design and test to WCAG 2.2 level AA as the working standard, which is what most Abu Dhabi enterprise and government procurement documents reference either directly or through an equivalent requirement, and it is the sensible floor regardless. Arabic changes how you verify it more than what the criteria say. Colour contrast is script-neutral, but Arabic letterforms are lighter and more connected than Latin at the same weight, so a contrast ratio that passes technically can still read poorly, and we test with Arabic-reading users rather than trusting the ratio alone. Reading order is the big one: in a mirrored layout the visual order and the DOM order can diverge, and screen readers follow the DOM, so a layout that looks correct can be announced in the wrong sequence. Screen reader testing needs Arabic voices enabled, and behaviour differs meaningfully between VoiceOver and NVDA with mixed-direction content. Target size and spacing matter more on the mid-range Android devices that a large share of Abu Dhabi's workforce uses. Form errors need to be announced, not only shown, and the Arabic error copy needs to be written rather than translated.