Arabic-first software: what it actually takes
Arabic-first software is designed and tested in Arabic as a primary language, not translated afterwards. In practice that means five things: mirrored right-to-left layouts, Arabic-aware search and sorting, documents that are bilingual from one record, a deliberate choice of numerals and calendars including Hijri, and testing with real Arabic data. If any of the five is missing, users run into it in daily work.
What does right-to-left support involve?
Right-to-left is more than aligning text to the right. The whole layout mirrors: navigation, the order of columns in tables, progress indicators, and the direction of arrows and back buttons. Icons that show direction have to flip; icons that show an object, such as a clock or a phone, must not.
The harder part is mixed direction. An Arabic sentence that contains an English product name, a phone number, an email address or an invoice number mixes two directions on one line. Without explicit handling, punctuation jumps to the wrong side and numbers appear reversed. Good software marks those runs as left-to-right inside the Arabic text.
Why do Arabic search and sorting need extra work?
Arabic letters have variants that people treat as the same letter when they search. A name can be typed with different forms of alef, with taa marbuta or haa at the end of a word, with alef maqsura or yaa, and with or without short-vowel marks and the stretching character kashida. A search that matches only identical characters misses customers and employees that are on record.
Sorting has the same problem: lists must follow Arabic alphabetical order, not the order of character codes. This is set in the database and the application, and it is easy to get wrong if nobody tests it. Digits add one more variant, because a user may type 123 or ١٢٣ in the same search box.
How should bilingual documents work?
A bilingual invoice should not be two files that someone keeps in step by hand. It should be one record rendered in two languages. That means every customer-facing field stores an Arabic value and an English value, labels come from a translation set that finance can review, and either version can be issued from the same data.
Documents also need fonts that shape Arabic letters correctly, so that they join, and a PDF generator that handles right-to-left text. In the Kingdom, invoices need to be in Arabic and a second language may be added; confirm what applies to your documents with your adviser.
Which numerals and which calendar?
Two numeral sets are in daily use in Saudi business: Western digits (0 to 9) and Arabic-Indic digits (٠ to ٩). Neither is wrong. Make it a setting per document type or per user, and keep amounts and tables aligned either way.
Dates work the same way. Saudi Arabia's official Hijri calendar is Umm al-Qura. Contracts, residence documents and many official deadlines are expressed in it, while invoices and accounting periods run on the Gregorian calendar. Good software stores one date, can show it in either calendar, and says which one a document uses, because Hijri and Gregorian months do not line up and a one-day difference is common.
What breaks when Arabic data meets exports and integrations?
- A CSV file opened in a spreadsheet shows garbled Arabic unless it is saved with the right encoding, usually UTF-8 with a byte-order mark.
- Email notifications must go out in the recipient's language, with the right direction.
- Integrations with systems that hold only English names need a rule for which name wins.
- Label and slip printers need Arabic fonts loaded, or the text prints as boxes.
How do you test whether software is really Arabic-first?
- Enter a customer with a name that includes hamza, then find it by searching without the hamza.
- Sort a list of fifty Arabic names and check the order against an Arabic dictionary order.
- Issue an invoice in Arabic and open the PDF: letters must join and the amounts must align.
- Type an Arabic sentence with an invoice number in the middle and check that it reads correctly.
- Export a report to CSV and open it in a spreadsheet.
- Switch language in the middle of a task and see whether the work in progress survives.
- Print a label or a slip and read it.
Does Arabic-first mean English is second-class?
No. Arabic-first means Arabic is designed in from the start. A business with an English-reading head office, auditors or regional managers needs the same record in English, equally complete. Each user chooses a language, and nothing should exist in only one of them.
This is how our own products are designed: one record, two languages. The home page lets you flip a sample invoice between Arabic and English.
Short answers.
Is machine translation of the interface enough?
No. A translated interface fixes labels, not layout, search, sorting, documents or dates. Business terms also need review by someone who uses them: the word for a purchase order or a delivery note in a Saudi company is not always the textbook one.
Can an English-only system be made to work in Arabic?
Sometimes for display, rarely for everything else. If the database sorting rules, search, document engine and fonts were not built for Arabic, adding a language file does not fix them.
Why does Arabic text look disconnected in some PDFs?
The PDF generator is placing letters without shaping them. The fix is a generator and a font that support Arabic shaping. It is a defect worth rejecting at acceptance.
Do we need Arabic-Indic digits?
Not necessarily. Western digits for amounts are common, with either set in letters. The point is that the choice is yours, per document type.
Want this applied to your company?
Tell us what you run today. A consultant from our Riyadh team replies with next steps, and a written proposal follows before any work starts.