Arabic app localization in the UAE: how to build and test iOS and Android apps that work right to left
By Dr. Hani Elimam Manager & CEO, SmartTech Studio
An app can pass the “we support Arabic” check and still feel broken to an Arabic speaker within a minute. The strings are translated, yet the back arrow points into the screen, a counter reads «2 رسالة», the order total shows ١٢٠ while the price beside it shows 120, and a booking reminder arrives in English because the server never learned which language the user chose. None of these is a translation mistake. Each one was decided in code, and decided wrongly.
This guide covers the engineering and process side of Arabic localization for iOS, Android and Flutter apps: strings, plurals, layout direction, icons, digits and dates, per-app language, push notifications, fonts, testing and cost. What the Arabic should say (the form of address, the register, the wording of each plural) is covered in our guide to Arabic UX writing, and right to left on websites in bilingual RTL web design. The platform facts come from Apple, Android and Flutter documentation, checked in November 2026.
Where we stand: SmartTech Studio builds bilingual apps and platforms from Abu Dhabi. Ehgizli, our clinic management SaaS, and Taxi Masr, a licensed-taxi booking app for Egypt, are both built in Arabic and English, and our Al-Azhar University platform is published in seven languages, three of them right to left. We have not been hired to localize an app that another team built, so where this guide goes beyond the official documentation, it describes what we do on our own builds.
Internationalize first: get every string out of the code
Apple’s documentation splits the work in two. You first internationalize the app, preparing code and assets so they adapt to any language and region, and only then localize it by translating strings and varying assets. Most of the defects above are internationalization bugs that no translator can fix, because the translator never sees the code. How far to adapt the product beyond its words is a separate choice, covered in translation vs localization.
On iOS, Apple calls string catalogs the recommended way to localize strings with plurals from Xcode 15 onward. Add a Localizable.xcstrings file and build: Xcode collects the localizable strings in your code and updates the catalog on every build, and most SwiftUI strings inside views are picked up automatically. Text built outside the localizable APIs is missed, so turn on “Show non-localized strings” in the scheme options, which displays every string Xcode will not export in capital letters.
On Android, default strings live in res/values/strings.xml and Arabic ones in res/values-ar/strings.xml. The default file must contain every string: Android warns that if one is missing, the app shows an error and does not run on a device set to a language you have not translated. Flutter generates its localization classes from one ARB file per language (app_en.arb and app_ar.arb, for example) once flutter_localizations and intl are added and generate is set to true in pubspec.yaml.
Three habits make strings translatable. Give each a descriptive key and a comment on where it appears and how much room it has (Xcode can even generate comments for you). Never join sentence fragments in code, because Arabic word order will not survive it. Mark what must not be translated, such as placeholders and brand names, which Android does with an xliff:g tag. Then hunt for the strings teams forget: permission prompts (Apple calls them purpose strings), error messages from your API, text baked into images, and the privacy policy.
| Task | iOS (SwiftUI and UIKit) | Android (Views and Compose) | Flutter |
|---|---|---|---|
| Arabic strings | String catalog (Localizable.xcstrings) | res/values-ar/strings.xml | lib/l10n/app_ar.arb |
| Plurals | Vary by Plural in the catalog | plurals resource: zero, one, two, few, many, other | ICU syntax: =0, =1, =2, few, many, other |
| Turning on right to left | On by default in system frameworks | android:supportsRtl="true" in the manifest | GlobalWidgetsLocalizations sets the default direction |
| Spacing that follows direction | Leading and trailing | start and end attributes; start and end padding in Compose | EdgeInsetsDirectional |
| Icons that mirror | SF Symbols right-to-left variants | android:autoMirrored; Icons.AutoMirrored in Compose | IconData.matchTextDirection |
Arabic plurals: six forms in every toolchain
Apple’s documentation puts it plainly: Arabic has different plural forms for the zero, one, two, few, many and other categories, following the Unicode CLDR rules, while English needs only one and other. What each of the six sentences says is a writing question, answered with examples in our UX writing guide. The engineering question is whether your strings file holds all six, and whether anything forces someone to fill them.
In a string catalog, Control-click a string that contains a number and choose Vary by Plural. When you add a language, Xcode adds the categories that language uses, so Arabic shows six fields where English shows two. Apple warns that the text may be grammatically wrong if a category is left out, and that each variant should use the format specifier or a spelled-out word, never a literal numeral such as 1, which may display wrongly if the user changes region.
Android’s plurals resource takes the same six keywords, and its documentation names Arabic as a language that treats zero specially. English ignores a zero string even when the count is 0, so an English file never reveals a missing Arabic zero. And when the string shows the number, you pass the count twice to getQuantityString or pluralStringResource: once to choose the form, once to fill the %d.
Flutter’s ARB files use ICU plural syntax, with the cases =0, =1, =2, few, many and other, and the documentation notes that only other is required. In Arabic that is a trap. A file copied from the English shape, with only =1 and other, compiles cleanly and prints the wrong grammar for counts such as 0, 2 and 3 to 10. Add a build or review check that rejects any Arabic plural with fewer than six cases.
Layout direction: let the framework flip, then fix what it cannot
Apple’s Human Interface Guidelines say the system-provided UI frameworks support right to left by default, so standard components flip on their own. In SwiftUI and UIKit that holds only while your own layout uses leading and trailing rather than left and right: a hard-coded left padding stays on the left in Arabic. To preview a SwiftUI view in Arabic, Apple’s instructions set the locale and also the layoutDirection environment value.
On Android, mirroring needs android:supportsRtl="true" in the manifest and layouts written with start and end: paddingStart, layout_marginEnd, drawableStart. When the app targets API level 17 or higher and both left/right and start/end are defined, start and end win; when only left and right exist, nothing flips. Code needs the same treatment (Gravity.START, getMarginStart(), custom views that check the layout direction before drawing), and Android names ViewPager as a framework element that does not support right to left.
In Jetpack Compose, the start and end parameters of Modifier.padding flip while absolutePadding keeps its left and right, and in a custom layout placeRelative mirrors a child’s x position while place leaves it alone. LocalLayoutDirection changes the direction for part of the screen, which is how you keep a phone or card number field left to right inside an Arabic form.
In Flutter, GlobalWidgetsLocalizations.delegate sets the default text direction from the locale, and the Directionality widget passes it down the tree. Padding built with EdgeInsetsDirectional puts start on the right-hand side in Arabic; padding built with EdgeInsets and a fixed left value does not.
No framework flips canvas drawing, animations and swipe gestures with hard-coded directions, or any x coordinate you calculate yourself. Find these in the code before testing starts.
Icons and images: what flips and what stays
Apple’s guidelines give the clearest rules, and they work just as well on Android. Flip controls that show progress or move through a fixed order: in Arabic a back button points right, sliders and progress bars run from right to left, and next and previous buttons swap places. Flip icons that show forward or backward motion; Apple’s example is a speaker icon whose sound waves must come from the right in Arabic.
Do not flip logos, universal marks such as the check mark, clocks, photographs and illustrations, or icons of tools held in the right hand. Do not flip a control that refers to an actual direction: an arrow that means “to the right” keeps pointing right. And never reverse the digits inside a number. A phone number or card number reads in the same order in every language, even when the numerals along a progress bar or rating control change order.
The tooling helps. SF Symbols include right-to-left variants and symbols localized for Arabic. On Android, android:autoMirrored="true" mirrors a drawable from Android 4.4, though the documentation limits it to simple drawables whose mirror image is a straight flip. Compose offers Icons.AutoMirrored from version 1.6.0 of the Material icons, and in Flutter an icon whose IconData sets matchTextDirection is mirrored when the direction is right to left.
For custom icons, keep a list with one decision per icon (flip, keep or redraw) and have an Arabic reader approve it.
Digits, dates and prices: format with the locale, never by hand
Apple’s advice is to stop handling regional variation yourself and use Foundation’s formatters, which turn dates, numbers, currencies and durations into strings for the device’s locale; for money its examples use a currency code and Decimal, not Float or Double. On an iPhone, Language & Region also lets the person change the calendar, the date format and the number format. A formatter follows the device’s settings, while a date you assemble from day, month and year in your own code ignores them.
Digits often surprise app owners in the UAE. In the current Unicode CLDR data (version 49), the default numbering system for Arabic, and for Arabic in the UAE (ar-AE), is Western digits, 0 to 9, while Arabic in Saudi Arabia, Egypt and Oman defaults to Arabic-Indic digits. In a quick check we ran with Node.js (ICU 78.3, CLDR 48), 1234.5 came out as 1,234.5 for ar-AE and as ١٬٢٣٤٫٥ for ar-SA. Phones use the CLDR data their operating system ships, and Android’s documentation still describes most Arabic locales as using their own digits. Decide your digit policy (a writing decision, covered in our UX writing guide), make the formatter enforce it, and check it on real devices.
Keep formatting for people apart from formatting for machines. Android’s documentation gives the classic failure: String.format on a device whose locale has its own digits writes numbers in those digits and breaks a SQL query, so pass Locale.US for anything a machine reads. Treat API payloads, analytics events, order references and file names the same way.
Mixed-direction text needs the same discipline. A phone number that starts with a plus sign, or an English name inside an Arabic sentence, can land in the wrong place. Android’s answer is to wrap every piece of text you insert into a localized message with BidiFormatter.unicodeWrap(), except machine-readable strings such as a URI.
Per-app language: Arabic for your app, English for the phone
A user may keep the phone in English and want your app in Arabic, or the reverse, and both platforms now allow it. Apple’s localization overview says that on iOS and iPadOS people can select a preferred language for your app independent of their device language. Android 13 added the same choice, under Settings > System > Languages & input > App languages, or Settings > Apps, then the app, then Language.
On Android, your app appears in that list only if it declares its languages. From Android Studio Giraffe and Android Gradle plugin 8.1, set generateLocaleConfig = true in the androidResources block and name the default locale in a resources.properties file; compileSdk must be 33 or higher. For an in-app language picker, Android recommends AppCompatDelegate.setApplicationLocales from AppCompat 1.6.0 or higher. It keeps the in-app choice and the system setting in sync and works on older versions (with autoStoreLocales on Android 12 and lower). With Compose, the activity must extend AppCompatActivity, or the change does not take effect.
Because the app language and the phone language can now differ, read the app’s locale rather than the system’s, and tell your server about the choice (next section). To test on iOS, the App Language menu in the Xcode scheme runs your app in Arabic without switching the whole simulator.
Content the app does not ship with: API data, push notifications and email
Strings inside the app are the easy half. Product names, order statuses and error messages often come from your server, and they arrive in English unless the API knows which language to send. Send the app’s language with every request, usually in an Accept-Language header, and store both language versions of every field a user reads. For product data, that work is covered in our guide to Arabic product catalogue localization.
Push notifications have two official routes, both described by Apple. You can put the localized text in the payload, which means your server must track each user’s preferred language, or send loc-key, title-loc-key and loc-args and let the device take the string from the app’s own localization files. Firebase Cloud Messaging offers the same pattern for Android with title_loc_key and body_loc_key. Keys suit fixed messages such as an appointment reminder; text written on the server suits campaigns and anything that changes daily.
Email, SMS and WhatsApp messages triggered by the app follow one rule: store one language per user, set by the user’s choice in the app, and use it everywhere. When an Arabic string is missing, English is an acceptable fallback for a brand or product name, rarely for an instruction or an error.
Fonts, line height and the room Arabic needs
On Apple platforms the system font covers Arabic: Apple describes SF Arabic as a contemporary interpretation of the Naskh style, designed to sit with SF Pro in multilingual text. Trouble starts with a custom brand font. A Latin typeface with no Arabic glyphs falls back to a system font with a different weight and different metrics, and headings in the two languages stop matching. Choose an Arabic typeface whose weight sits well beside your Latin one, and bundle both.
Arabic needs vertical room for the dots and marks above and below its letters. Apple recommends Dynamic Type, which helps prevent clipped words and letters in languages that need more vertical space, and Xcode’s Tall Pseudolanguage simulates exactly that text. The usual culprits are fixed-height labels, tight line heights and containers that clip their content. We met this on our own website: animated headline words sat in boxes that clipped their content, the dots under a final ي were cut off, and «في» looked like «فى». More vertical padding inside the box fixed it.
Apple also suggests making Arabic about 2 points larger when it sits beside uppercase Latin text in buttons, labels and titles, because Arabic has no capital letters and can look too small next to them. Never add letter spacing to Arabic, which breaks the joins between letters, and avoid fixed widths: Xcode’s Double-Length Pseudolanguage shows where a layout breaks when text grows.
Test in Arabic before an Arabic speaker does
Both platforms ship tools that catch most layout bugs before a translator delivers a word. In the Xcode scheme options you can run the app in pseudolanguages, among them Right-to-Left, Double-Length, Accented, Bounded String and Tall. On Android, set pseudoLocalesEnabled for debug builds and choose English (XA), which accents and expands the text and brackets each message, or AR (XB), which switches text to right to left, even if nobody on the team reads Arabic. A message split across two brackets in XA is a concatenated string. Android 4.4 and later also have Force RTL layout direction in the developer options, and Compose previews accept @Preview(locale = "ar").
Pseudolocales do not replace a real test. Before release, put the Arabic build on a real iPhone and a real Android phone and walk through the flows that break most often:
Sign-up and login with an Arabic name and a phone number starting +971, in fields that keep the number left to right.
Mixed text: an English brand or product name inside an Arabic sentence, and a support chat where the user types both languages in one message.
Every number on screen, from prices and counters to dates and receipts, checked against your digit policy and all six plural forms. The counts 0, 1, 2, 3, 11 and 100 touch each Arabic category once.
Push notifications, emails and SMS received while the phone is set to English and the app to Arabic.
Navigation: back gestures, swipeable tabs, carousels, step indicators and anything animated sideways.
Screens your app hands over to: permission prompts, the share sheet, maps, the payment sheet, and PDFs or receipts from your server. Then run the main flows once with VoiceOver and once with TalkBack in Arabic.
Apple also suggests running Xcode test plans in each language, then TestFlight for feedback from users in the market. The Arabic store listing is a separate deliverable with its own character limits and keyword research, covered in our guide to publishing on the App Store and Google Play.
Process and cost: who translates, and what Arabic adds to the budget
Engineering and language work run side by side. Developers externalize strings, fix layouts and wire up the formatters. A native Arabic writer works from a glossary and a one-page style guide. Then a reviewer checks every screen in the running build, not in a spreadsheet. Xcode can export all localizable content for a translator, from catalogs, code and Interface Builder files, and import it back; Android strings files and Flutter ARB files travel the same way. Send screenshots with the files, because a translator who sees the screen picks the right word.
Both IDEs now offer machine help. Apple lists generating translations among Xcode’s string catalog tasks, and Android’s documentation points to Gemini in Android Studio for translating string resources. Treat the output as a draft: interface strings reach a model with little context, and a native reviewer still has to read each one inside the app. Our multilingual content service does that writing and review.
Prices, all “from” and excluding VAT: Arabic localization of text from AED 0.35 per word, and through our app development service, a cross-platform app built bilingual from the first screen from AED 10,000, or a full product with an admin dashboard and API from AED 20,000. As a hypothetical example, an app with 6,000 words of interface text, notifications and emails would cost from AED 2,100 to localize at that rate. The larger, less predictable cost is engineering when Arabic is added to an app built for English only, which is why we build in both languages from day one. Our guide to mobile app costs in the UAE explains what those prices include.
If you have an app that needs Arabic, or one whose Arabic feels wrong, send us a test build or a few screenshots and we will tell you which of these problems it has and what fixing them involves.
Sources
- Apple Developer: Localizing and varying text with a string catalog
- Apple Developer: Preparing your interface for localization (non-localized strings and pseudolanguages)
- Apple Human Interface Guidelines: Right to left
- Apple Developer: Localization overview (per-app language on iOS and iPadOS, test plans and TestFlight)
- Android Developers: Support different languages and cultures (RTL mirroring, BidiFormatter, number formatting, per-app languages)
- Android Developers: Test your app with pseudolocales (en-XA and ar-XB)
- Flutter documentation: Internationalizing Flutter apps
FAQ
How much does Arabic app localization cost in the UAE?
With us, translating the text into Arabic starts from AED 0.35 per word, so a hypothetical 6,000 words would start from AED 2,100. A cross-platform app built bilingual from the start begins at AED 10,000, excluding VAT. Adding Arabic to an existing English-only app also needs engineering work, priced after an audit of the code.
Can we add Arabic to an existing iOS or Android app without rebuilding it?
Usually, yes. Most of the work is internationalization: moving hard-coded strings into resource files, replacing left and right with leading and trailing or start and end, adding plural forms and formatters, and deciding which icons to mirror. Custom views and canvas drawing take longest. Running the app in a right-to-left pseudolanguage first shows the size of the job.
Should an Arabic app in the UAE use Western or Arabic-Indic digits?
In current Unicode CLDR data, Arabic in the UAE defaults to Western digits, 0 to 9, while Arabic in Saudi Arabia, Egypt and Oman defaults to Arabic-Indic digits. Phones follow the data their operating system ships, so choose one policy, enforce it through your formatters, test it on real devices, and keep anything a machine reads in a fixed locale.
Does Flutter handle right to left automatically?
Largely. With flutter_localizations, the text direction follows the locale, and widgets read it through Directionality. You still need EdgeInsetsDirectional instead of fixed left padding, matchTextDirection on icons that should mirror, all six Arabic plural cases in the ARB file (only other is required), and manual handling of anything you paint yourself.
How can we test Arabic if nobody on the team reads it?
Start with the built-in tools: the Right-to-Left pseudolanguage in Xcode, and the AR (XB) pseudolocale and Force RTL layout direction on Android. They expose mirroring, truncation, hard-coded strings and concatenation without any Arabic text. Before release, a native Arabic reader still has to go through the real build on real phones.