Product · 28 July 2026 · 6 min
Why we ship in seven weeks — and when we say no
Seven weeks is a constraint, not a slogan. Here is what it buys, and the projects we turn down.
Product
11 August 2026 7 min
Most "bilingual" products in the Gulf are English products with an Arabic layer bolted on. You can tell within about four seconds: the layout does not mirror, the type is too tight, and the numbers read backwards.
Doing it properly is not hard. It is just a set of decisions you have to make before you write the first screen, because every one of them is expensive to reverse.
Getting the words right matters, and machine translation is not enough for anything a customer reads. But translation is a solved, purchasable problem.
What breaks products is everything around the words.
Arabic is right-to-left, and that is a property of the layout, not of the text. In an Arabic interface the navigation starts on the right, the back arrow points right, progress runs right to left, and a floating button sits in the bottom-left.
The single decision that makes this cheap: never write a physical direction in your styles. No margin-left, no padding-right, no text-align: left. Use logical properties — margin-inline-start, padding-inline-end, text-align: start — and the browser mirrors the whole interface when you set dir="rtl".
Do this from the first component and Arabic layout costs almost nothing. Retrofit it and you are auditing every stylesheet in the product.
Icons need a decision each. Arrows and chevrons mirror. A clock, a play button, a logo do not.
Latin and Arabic type do not behave the same way and cannot share settings.
dir="ltr".The Gulf uses Western Arabic numerals — 1, 2, 3 — in both languages. So far so easy.
The problem is bidirectional text. Put a number range inside an Arabic sentence and the browser may reorder it. Write "الأسبوع 3–5" and a reader can see 5–3, because the dash between two numbers resolves to the paragraph direction and flips their order.
It is a real bug, it is easy to miss if you do not read Arabic, and it appears in exactly the places that matter: prices, dates, phone numbers, week ranges.
The fix is to isolate the run with Unicode directional isolates, U+2066 … U+2069, or an equivalent <bdi> element. Then test it — not by eye, but by measuring where the glyphs actually land.
dir="ltr" on the input and align it to the start.Adding Arabic to a finished English product is not a translation project. In our experience it lands somewhere between 30% and 50% of the original build, because it touches the stylesheet, the components, the forms, the email templates, the URL structure, and the tests.
Planned from day one, the same work is roughly 10–15%.
That gap is the whole argument. If there is any chance you will need Arabic, build for it now — even if you launch English-only and switch the second language on later.
Send a short brief. We reply within one business day, Sunday to Thursday.
Product · 28 July 2026 · 6 min
Seven weeks is a constraint, not a slogan. Here is what it buys, and the projects we turn down.
Building in the UAE · 14 July 2026 · 8 min
Real 2026 numbers in AED, what drives them, and the costs nobody puts in the quote.