Arabic RTL software development for MENA
Most “Arabic support” is an English product with the text swapped and the layout mirrored. Users notice within seconds and trust drops. I build products where Arabic is a first-class language in the data model, the interface, the search, the emails and the invoices.
Built for these situations
- Companies selling to Arabic-speaking customers whose product still feels translated
- Businesses entering Saudi Arabia, Egypt or the Gulf with an English-first product
- Government and enterprise buyers who require Arabic-first internal systems
- Teams whose Arabic layout, search or printing breaks in production
Not a fit if
- Products whose audience is entirely English-speaking
- Teams looking only for translation of existing strings — that is a translator's job, not an engineer's
- Anyone unwilling to review Arabic copy with a native speaker before launch
What usually goes wrong
Mirrored, not designed
Flipping a layout produces backwards charts, wrong-facing icons, broken number alignment and progress bars that fill the wrong way. It reads as carelessness, and users generalise it to the whole product.
Arabic search does not find Arabic
Without normalisation for alef and hamza forms, taa marbuta and diacritics, a customer searching “احمد” fails to find “أحمد”. The catalogue looks empty when it is not.
The database only speaks one language
When a product name is a single column, bilingual content becomes a manual duplication problem — and one of the two languages is always out of date.
Everything outside the app is English
The interface is Arabic, then the confirmation email, the SMS, the invoice PDF and the error messages arrive in English. Those touchpoints carry most of the trust.
What Makhloof Studio actually delivers
Bilingual data model
Translatable content is modelled as translatable from the start, with a defined fallback rule, so adding or correcting a language is a content task rather than a migration.
Genuine RTL interface work
Logical properties instead of left/right, direction-aware icons and motion, correct numeral and date handling, and Arabic typography that is chosen rather than inherited.
Arabic-aware search and sorting
Normalisation of alef, hamza, taa marbuta, yaa and diacritics, plus sensible Arabic collation — so search results match what a customer actually typed.
Localized everything else
Emails, SMS and push notifications, invoice and report PDFs, validation and error messages, and SEO metadata with correct hreflang — all in the user's language.
Shipped, not theorised
Every claim on this page maps to a case study you can read in full.
Typical modules
A realistic scope for this kind of build. Yours will be a subset — the first call is where we cut it down.
Content & data
- Translatable fields with fallback rules
- Arabic normalisation for search
- Arabic collation and sorting
- Hijri and Gregorian date handling
- Arabic and Latin numeral formatting
- Bilingual admin content editing
Interface
- Direction-aware layout system
- Arabic typography and line-height tuning
- Icon and motion direction correctness
- Forms, inputs and validation in Arabic
- Charts and dashboards that read correctly RTL
- Language switching that preserves context
Beyond the screen
- Arabic transactional email templates
- Arabic SMS and push notifications
- RTL invoice and report PDFs
- Arabic SEO metadata and hreflang
- Arabic support and help content
- Localized app store listings
How this gets built
- 01
Decide the primary language
Arabic-first and English-first lead to different defaults, different typography and different content workflows. Choosing deliberately avoids a bilingual product that is fluent in neither.
- 02
Build RTL from the first screen
Both directions are tested from the beginning. RTL retrofits are consistently more expensive than building both from the start.
- 03
Review copy with a native speaker
Arabic interface copy is written and reviewed as Arabic, not translated from English. Machine-translated microcopy is the fastest way to look foreign to your own market.
- 04
Test on real devices
Arabic rendering, keyboards, fonts and printing behave differently across devices and browsers. That testing pass is part of the plan, not an afterthought.
Typical stack
Worth knowing before you write.
A short, honest filter. It saves both of us a call that was never going to work.
A good fit if
- You have a real business or a funded idea, and a decision-maker in the room
- The product has to handle money, roles, or operations correctly — not just look good
- You want one senior engineer accountable end to end, not a rotating team
- Arabic and English both matter to your market
- You can give a few hours a week to reviews and decisions
Not a fit if
- You need a team of ten starting Monday — that is an agency's job, not mine
- The budget is fixed before the scope exists and cannot move
- You are looking for the cheapest possible quote rather than the right build
- Nobody on your side can answer product questions within a few days
- You want equity-only work or an unpaid prototype
What you get in the first call
Fifteen minutes, free, no deck.- A straight answer on whether this is buildable the way you imagine it
- The two or three decisions that will drive most of your cost
- A rough shape: phases, surfaces, and where the risk sits
- An honest ballpark range — or a referral if I am not the right fit
What to prepare
None of it has to be polished.- One sentence on what the business does today
- The workflow that hurts most, described in plain language
- Who needs to log in, and what each of them does
- Any deadline that is real, and why it is real
- A budget range you are comfortable discussing openly
Answered straight
- Can you add Arabic to our existing product?
- Usually yes. The honest first step is an audit: how translatable content is stored, how the layout handles direction, and how much lives outside the app in emails, PDFs and notifications. That audit determines whether this is a few weeks of work or a structural change — and you get the real answer either way.
- Do you write the Arabic content too?
- Interface copy, error messages and transactional templates — yes, written in Arabic rather than translated. Marketing and legal copy should still be reviewed by someone who owns your brand voice.
- Which Arabic do you write?
- Clear Modern Standard Arabic, which reads correctly across Egypt, Saudi Arabia and the Gulf. Dialect is used only where a specific market and tone call for it, and that is a decision we make together.
- How is Arabic SEO handled?
- Separate indexable URLs per language, correct hreflang pairing, Arabic metadata and structured data, and a single canonical host. This site itself runs that setup across every localized page.
Written for buyers, not for engineers.
Need your product to work properly in Arabic?
Send a link or a screenshot. I'll tell you on the first call whether this is a few weeks of work or something structural.