Arabic-First Software: More Than Flipping the Layout

Most business software sold in the Gulf was designed in English and given an Arabic mode afterwards. It usually works, in the sense that nothing crashes. It also tells every Arabic-speaking user, on every screen, that they were the second audience.

Direction is a property of the layout, not the text

In a proper right-to-left interface the navigation starts on the right, icons that imply direction are mirrored, progress runs the other way and a form's labels sit where the eye lands first. Software that only reverses the text ends up with a back arrow pointing forwards — small, constant and impossible to unsee.

• Numbers, currency and dates formatted for the locale, not the language
• Arabic names sorted the way an Arabic speaker expects to find them
• Search that matches with or without diacritics and across spellings
• Mixed Arabic and Latin in one line without the punctuation jumping
• PDFs and printed documents that keep all of the above

The PDF is where it usually breaks

An invoice that looks correct on screen and prints with reversed letters, or with the total in the wrong column, is a document your customer will not accept. Test the printed output in Arabic on day one of the project, not in the week before launch — the fix is often a font choice that has to be made early.

If the Arabic screens were built last, the users will find out first.

Write both languages at the same time

The practical discipline is simple: no screen is finished until it exists in both languages, and both are reviewed by someone who works in that language. It costs a little more per screen and removes an entire phase of rework later.

For a Saudi company this is not a courtesy. Arabic is the language of the contract, the invoice, the regulator and most of the workforce — the software should be at least as fluent as the business is.