Arabic mobile app development is usually scoped as a translation step at the end of the project — ship the English app, export the strings, send them to a translator, paste them back. That order is what produces the expensive version. Arabic changes layout direction, typography, numerals, input handling and content length, and every one of those touches code written on the assumption of left-to-right English.
What Arabic mobile app development actually involves
The distinction that decides your budget is between localisation and mirroring. Localisation is translated strings. Mirroring is the interface itself flipping: navigation moves to the right, back arrows point right, progress bars fill right-to-left, a list row's chevron sits on the left, and swipe gestures reverse. Text direction and layout direction are two separate problems, and a mixed string such as iPhone 15 جديد 500 د.ك has to render correctly under the bidirectional text algorithm without the number or currency jumping to the wrong side of the line.
Both iOS and Android support this properly if you build with it in mind. The platforms give you leading and trailing layout attributes instead of left and right, automatic asset mirroring, and locale-aware number and date formatting. The failure mode is almost never the platform — it is a codebase that hard-coded left and right for eighteen months and now has to be audited screen by screen. Microsoft's own right-to-left layout guidance is a good baseline checklist for what has to mirror and what must not.
Six things that break when Arabic arrives late
- Hard-coded spacing. Every left padding, right margin and absolute position has to become leading or trailing. This is mechanical work, but it is spread across every screen you have already shipped.
- Numerals. Arabic-Indic digits and Western digits are both correct in the Gulf. Pick one rule and hold it: most GCC apps use Western digits for prices, phone numbers, OTP codes and quantities, because that is what users type and read on receipts.
- Typography. A Latin-only font has no Arabic glyphs, so the system silently falls back to something that does not match your brand. Arabic also needs more vertical line height than the same text in English, and it has no uppercase, so your all-caps button and label styles lose their visual hierarchy.
- String length. Arabic translations are often shorter in characters but longer in individual words, so fixed-width buttons, tab bars and table cells clip or wrap in ways your English layout never did.
- Images and icons with embedded text. Onboarding illustrations, empty states and marketing banners all need Arabic versions, and asymmetric imagery often needs mirroring to still point the right way.
- Search and name matching. Users type alef, hamza and ta marbuta variants inconsistently, and often skip diacritics entirely. Exact-match search fails constantly unless you normalise both the query and the indexed data.
Then there is everything outside the app binary: Arabic App Store and Play Store listings, push notification copy, SMS and WhatsApp templates, invoices and receipts, and server-generated emails. On Dwa, a pharmacy delivery product in Kuwait, the bilingual surface included order flow, address entry, prescription instructions and customer receipts — the app screens were only part of the work.
Arabic content is a product decision, not a translation task
Two language questions have to be answered before anyone writes copy. First, register: interface text, legal pages and error messages belong in clear Modern Standard Arabic, while conversational surfaces such as support replies and in-app assistants read better in local Gulf phrasing. Mixing those arbitrarily is what makes an app feel machine-translated. Second, ownership: someone on your side has to own the Arabic glossary — your product nouns, your plan names, your category labels — or every release will introduce a new word for the same thing.
If your app includes a chat or support layer, the Arabic requirements go deeper than strings, because the system has to understand user input rather than just display it. That is a different engineering problem, and we covered it separately in our guide to building an Arabic customer service chatbot.
What it costs and how long it takes
Building Arabic-first from day one typically adds a modest premium to the design and front-end effort — you are choosing direction-agnostic layout primitives and reviewing every screen in two directions as you go, not rebuilding anything. Retrofitting Arabic into a shipped English app is the expensive path: the UI layer often needs a substantial rework plus a full regression pass in both directions, and the schedule cost usually hurts more than the invoice. For how this sits inside overall project budgets, see our breakdown of app development cost in Kuwait.
The decision point is honest and simple. If Arabic-speaking users are a core audience rather than a future nice-to-have, build bilingual from the first screen. If Arabic is genuinely a phase two, at least make the structural choices now — leading and trailing layout, externalised strings, locale-aware formatting, an Arabic-capable font in the design system — so phase two is a translation project instead of a rebuild.
How to scope an Arabic-first build
- Decide day one whether Arabic ships with v1 or is explicitly deferred, and write that into the brief.
- Choose your numeral rule and your date convention, including whether Hijri dates appear anywhere.
- Pick an Arabic typeface that pairs with your Latin one, and set separate line-height values for each.
- Externalise every string, including validation and error text, before the second sprint.
- Test in Arabic on real devices with real Gulf names, addresses and phone numbers — not with placeholder text.
- Localise the store listing and all notification templates, not only the in-app screens.
This is the work we do as part of building bilingual products and AI-powered apps and assistants for Kuwait and GCC businesses: Arabic treated as a first-class language in the product, not a column in a spreadsheet.