Skip to content

Notes

Arabic is not a translation layer

On what breaks when Arabic is added at the end of a project.

A product with an Arabic toggle is not an Arabic product. The toggle is the last five per cent of the problem and it is usually the only part that gets budgeted. What breaks is not the words — it is the layout, the matching, the input, and the documents.

Right-to-left is a layout decision, not a stylesheet

Mirroring happens automatically only if the layout was written in logical directions from the beginning. Retrofitted, it produces the familiar tells: a chevron pointing the wrong way, a shadow falling on the wrong side, a progress bar filling backwards, a slide-in panel arriving from the wrong edge. Each is small and together they say the product was built somewhere else and shipped here. We build both directions from the first screen and check both on every one.

Names and matching are the real difficulty

One person's name has several legitimate spellings, with and without the definite article, with hamza written or dropped, transliterated four different ways in four systems. Exact matching produces duplicate customers, and loose matching merges two people who are not the same. This is not a translation problem and no language toggle touches it — it is a data model and a matching strategy, decided early or paid for later.

Real input is mixed

People write Arabic with Latin numerals, English product names inside Arabic sentences, dates in two calendars, and dialect that no formal grammar predicts. Addresses are described rather than numbered: after the industrial square, the building next to the pharmacy, third floor. A system that only accepts clean input pushes the cleaning onto a person, which is exactly the manual step you were trying to remove.

Documents are the last mile

Invoices, reports and receipts are where Arabic support usually collapses: a generic extraction pipeline mangles a right-to-left table, numerals get reordered, and a mixed-script line breaks in the wrong place. Getting this right is unglamorous work — layout-aware extraction, correct shaping in generated documents, and typography chosen for the script rather than inherited from a Latin design. It is also the part a customer notices immediately, because it is the part they print.

Everything we build is Arabic-first and fully bilingual, in both directions, on every screen. It is not a feature we charge for. It is the only way it works.

Where does your system get Arabic wrong?

Send us a screenshot of the worst example. That is usually a fast, satisfying fix.

Our WhatsApp line is being connected. Email reaches us today.