Skip to content
Localization 13 min read

Arabic UX writing for UAE apps and websites: microcopy that reads as if it was written in Arabic

By Manager & CEO, SmartTech Studio

Your Arabic app or website passes every check on paper. The strings file is fully translated, the layout flips to right-to-left, and still Arabic-speaking users say it “feels translated”. The cause is rarely the layout. It is the words: a sign-up screen that addresses every woman as a man and then switches to the feminine halfway through, an error message that reads like a legal notice, a price with the currency on the wrong side, and a counter that says «11 رسائل» because the plural rule came from English. Fixing those is the job of Arabic UX writing.

This article covers the microcopy in buttons, error messages, empty states, onboarding, notifications, emails, and SMS and WhatsApp templates. It sets out practical rules with English-to-Arabic examples, grounded in the Arabic content guidance of the UAE Design System published by the Telecommunications and Digital Government Regulatory Authority (TDRA), in Unicode CLDR data, and in guidance from the W3C and Apple.

Where translation vs localization covers strategy and our bilingual design guide covers layout, this piece covers the words inside the interface. We write from practice: SmartTech Studio builds bilingual apps and websites, every page on this site is written separately in English and Arabic, and our sister company, Smart World Legal Translation, is a legal translation firm.

Why an Arabic interface reads like a translation

Interface text is the hardest text to translate, because it is the shortest. A strings file gives the translator “Save”, “Order” and “Book”, one word per line, with no screen attached. “Save” is حفظ when it stores a form and توفير when it saves money. “Order” is طلب at checkout and ترتيب in a sorting menu. A translator who guesses right most of the time still leaves wrong words scattered across the app.

The second cause is structure inherited from English: one form of “you”, two plural forms, adjectives that agree with nothing, and sentences glued together from fragments in code. Arabic needs agreement in gender and number, has six plural categories and follows a different word order. When the code assumes English, even an excellent translator is handed sentences that cannot be made grammatical.

The third cause is ownership. The English copy had a writer and a review; the Arabic was a deliverable at the end of the project.

Addressing the user: gender, number and the slash problem

English “you” has no gender. Arabic “you” does, and so does every verb and adjective that refers to the user: أدخل or أدخلي, متأكد or متأكدة. Several approaches work; the worst outcome is mixing them on one screen.

One consistent imperative. The UAE Design System notes that Arabic convention uses the masculine form to address everyone, men and women alike, and that this is the form adopted in government content; for a service aimed specifically at women, it says to use the feminine. Its example is «أدخل رقم الهوية الإماراتية».

Verbal nouns and «يرجى». The same guide allows the masdar or «يرجى» in instructions and button labels: «يرجى إدخال رقم الهوية الإماراتية», and a button that reads «تقديم الطلب». Verbal nouns carry no gender, which is why they suit buttons, menu items, labels and headings: «تسجيل الدخول», «حفظ التغييرات», «إضافة إلى السلة». A clean rule: imperative where a sentence speaks to the user, verbal noun where a control names an action.

Unvowelled pronouns and passives. Written without diacritics, many second-person forms read the same for both genders: «حسابك», «لك», «بك». «تم تحديث حسابك» is correct for every reader. If users choose how they are addressed in their profile, the strings that need it can carry a masculine and a feminine variant; never infer gender from a name or a photo.

What to avoid is the slash. «أدخل/ي رقم هويتك/ـكِ» and «عزيزي/عزيزتي المتعامل/ة» both appear in the UAE Design System as examples of what not to write, because slashed forms break the flow of reading and confuse screen readers. In emails, open with the name, «مرحبًا أحمد،», or with «أهلًا بك». The plural «أدخلوا» dodges gender but sounds as if the screen is addressing a group, and the dual belongs only where you really address two people.

Register: simple MSA in the interface, dialect only where you choose it

Modern Standard Arabic is the default for interfaces. The UAE Design System asks for website content in simple, reader-friendly MSA that every Arabic speaker can understand, whatever their country or dialect. Local dialect, it says, may suit campaigns or social media aimed at a local audience, but not website and service content. It contrasts «ما الخدمة التي تبحث عنها اليوم؟» with the stilted «أيُّ الخدماتِ تبتغي الظفرَ بها في يومكَ هذا؟»: both are grammatical, and nobody wants to read the second on a phone.

Gulf colloquial has a place in a push campaign, an Instagram caption or a WhatsApp offer. Decide per channel and stay there; a checkout flow that switches between MSA and dialect reads as if two writers never met. Payments, errors, consent and account security stay in MSA.

Avoid English written in Arabic letters. The guide sets «سجّل الدخول إلى التطبيق، ثم حمّل الملف» against «اعمل لوج إن على الأبلكيشن، ثم داونلود للفايل», and «البريد الإلكتروني» against «الإيميل», though it allows a foreign word that is the most common one and has no understood Arabic equivalent.

Punctuation is part of the register: the Arabic comma ، and question mark ؟, never the English ones, and no space before a punctuation mark.

One boundary: your app store listing and landing pages must also match what people type into search, a separate exercise covered in Arabic keyword research in the UAE.

Arabic microcopy, before and after

These are the strings we see go wrong most often. The second column is what a literal translation or a context-free tool tends to produce; the third is what a native UX writer would ship.

Common English interface strings: literal Arabic vs natural Arabic
EnglishLiteral ArabicNatural ArabicWhy
Save (form button)«توفير»«حفظ»The money sense of the word
Book now (clinic app)«كتاب الآن»«احجز موعدك»Book means reserve; say what
Oops! Something went wrong.«عفوًا! حدث خطأ ما.»«تعذّر إرسال الطلب. تحقّق من اتصالك وحاول مرة أخرى.»Name the problem and the next step
Are you sure?«هل أنت متأكد؟»«حذف العنوان نهائيًّا؟»No gender; says what will happen
You don’t have any orders yet.«أنت لا تملك أي أوامر حتى الآن.»«لا توجد طلبات بعد. ابدأ التسوّق الآن.»طلب, not أمر; offer an action
Enter your email«أدخل/ي بريدك الإلكتروني»«أدخل بريدك الإلكتروني»No slash forms
Dear customer,«عزيزي/عزيزتي العميل/ة،»«مرحبًا أحمد،»Use the name
Your password must be at least 8 characters.«كلمة مرورك يجب أن تكون 8 أحرف على الأقل.»«يجب ألا تقل كلمة المرور عن 8 أحرف.»Arabic word order
Got it«حصلت عليه»«حسنًا»Idiom carried over literally

The pattern is consistent: verbs where the user is told what to do, verbal nouns where a control names an action, the problem stated before any apology, and nothing carried over from English idiom. The UAE Design System puts the error rule the same way: short and direct, naming the problem and offering the fix.

Length, truncation and the space Arabic needs

There is no fixed ratio between English and Arabic length, so design for both directions. Some labels grow: “Sign in” becomes «تسجيل الدخول», “Add to cart” becomes «إضافة إلى السلة». Others shrink: “Back” is «رجوع». Avoid fixed-width buttons and let a label wrap rather than cut it off. Give translators the maximum length of every string that has one, such as tab labels and notification titles, and rewrite a long Arabic label rather than add an ellipsis. On our Al-Azhar University platform, published in seven languages, three of them right-to-left, navigation had to stay coherent even when a menu label doubled in width from one language to another.

Arabic has no capital letters, so emphasis by uppercase does not exist, and the UAE Design System tells writers not to use italics in Arabic content. Apple’s Human Interface Guidelines note that Arabic can look too small next to uppercase Latin text in buttons, labels and titles, and suggest increasing the right-to-left font size by about 2 points.

Messaging channels have hard limits. Twilio’s documentation explains that non-Latin scripts, Arabic among them, need UCS-2 encoding, which limits a single SMS to 70 characters, against 160 for a plain GSM-7 message, and to 67 characters per segment once a message is split. A one-time-password text that fits one English segment can need two in Arabic. Write SMS templates in Arabic first and count.

WhatsApp templates have more room, but the notification preview is short, so the first line must carry the message: «موعدك غدًا الساعة 10:00 صباحًا» before any greeting. Arabic and English go in as separate language versions of the same template, as our guide to the WhatsApp Business API in the UAE explains.

Numbers, prices and dates in Arabic UI text

Arabic has two sets of digits: Western (0–9) and Arabic-Indic (٠–٩). Apple’s guidelines note that Arabic text might use either, and that usage varies between countries and even within one. For the UAE, the UAE Design System is explicit: use Western Arabic numerals (0–9), the ones adopted on UAE government websites, with a comma separating thousands in numbers of four or more digits, such as 1,000 and 200,000. Never mix both sets on one screen, and check what your framework outputs for the Arabic locale you use.

Apple also states that the digits in a specific number, such as a phone number or a credit card number, always appear in the same order, whatever the language. In an Arabic sentence, a +971 number can still render with its plus sign at the wrong end, because the plus sign has no direction of its own. Isolate phone numbers and order references, as described in the bidi section below, and keep phone input fields left-to-right.

Prices follow a fixed pattern. The UAE Design System puts the currency code before the amount in English, “AED 1,500”, and the amount before the currency name in Arabic, «1,500 درهم»; its examples prefer that over «AED 1500» or «1500 د.إ». In running text the noun changes with the number: «1,500 درهم», but «بين 100 و150 درهمًا», as the guide’s own example shows, so a template cannot simply append «درهم» to any number.

For dates, the guide asks for the day, then the month by name, then the year, using the Gregorian month names current in the UAE: يناير، فبراير، مارس. Its example of what not to write is «11 تشرين الثاني 2026»: the Levantine month names are correct Arabic, and they look foreign on a UAE screen. The Gregorian calendar is the standard for services and transactions; Hijri dates are for religious occasions such as Ramadan and Eid, followed by «هـ», and when both appear, the Gregorian date takes «م». Times use the 12-hour clock: «من 9:00 صباحًا إلى 5:30 مساءً», not «09:00 AM - 17:30». Oman and Egypt need their own check.

Plurals and placeholders: where English-shaped strings break

English has two plural forms for counting. Unicode CLDR, the locale data published by the Unicode Consortium, gives Arabic six cardinal categories: zero (0), one (1), two (2), few (3 to 10, and numbers ending in 03 to 10, such as 103), many (11 to 99, and numbers ending in 11 to 99, such as 111) and other (100 to 102, 1000 and similar).

A message counter therefore needs «لا توجد رسائل» for 0, «رسالة واحدة» for 1, «رسالتان» for 2, «3 رسائل» for 3 to 10, «11 رسالة» for 11 to 99 and «100 رسالة» for 100. With days, many and other differ too: «11 يومًا» but «100 يوم». A strings file built for English, with one singular key and one plural key, produces «11 رسائل» or «2 رسالة». The platform already knows the categories: in JavaScript, Intl.PluralRules returns zero, one, two, few and many for Arabic, as Mozilla’s documentation shows for 0, 1, 2, 6 and 18. What it cannot do is write the six Arabic sentences.

The second trap is building sentences in code. “You have” + count + “new messages” cannot become Arabic, because the number moves, the noun changes with it and the adjective must agree. Give translators the whole sentence with a named placeholder, «لديك {count} رسالة جديدة», as one complete string per plural category.

Placeholders carry gender too. “{item} was added to your cart” forces a choice between أُضيف and أُضيفت, depending on the product name, which the code cannot know. «تمت إضافة {item} إلى السلة» sidesteps it, because the verb now agrees with إضافة.

Bidi pitfalls that live in the words

Arabic interfaces are full of left-to-right fragments: brand names, product codes, email addresses, names typed in Latin script. The layout side, from mirroring to icons and fonts, is in our guide to bilingual RTL web design; this section is about the strings.

Set direction in the markup. The W3C’s guidance is to add dir="rtl" to the html element when the document is right-to-left and never to use CSS to apply the base direction. It also warns against assuming that a language declaration indicates direction, so declare both lang and dir.

Lead with Arabic. Where direction is detected automatically, as with dir="auto", the first strong character decides. «SmartTech ترحّب بك!» starts with Latin letters, so the line can be laid out left-to-right, exclamation mark on the wrong side. «مرحبًا بك في SmartTech!» starts with Arabic and displays correctly. Rewriting the string is cheaper than fixing it in code.

Isolate what you insert. When a placeholder is filled at run time with text of unknown direction, such as a customer’s name or an order reference, the W3C recommends wrapping it in a bdi element or a span with dir="auto". Its article lists brand names among the usual opposite-direction phrases, and phrases that begin or end with punctuation as a problem case.

Let user input find its own direction. The W3C advises dir="auto" on forms and inserted text, and the dirname attribute so a field’s direction is submitted with the form. A support form or chat box in a UAE app will receive Arabic and English, often in the same message. The W3C notes that automatic detection is not foolproof, so email, phone and URL fields stay left-to-right.

Process: who writes the Arabic, and with what context

Write Arabic first where the audience is Arabic-first. The UAE Design System’s rule for bilingual content is short: write, do not just translate, and have a native speaker review the Arabic, because literal or machine translation often reads unnaturally and can change the meaning. For flows used mostly in Arabic, such as an app for Arabic-speaking patients or a consumer app aimed at Emiratis, draft the Arabic first. On the Al-Azhar platform, Arabic was the primary locale and the other six languages were built outward from it. If you use AI for drafts, the limits in our guide to machine translation for websites apply even more to interface strings, which reach the tool with no context.

Keep a glossary and a one-page style guide. The glossary fixes terms that must never vary: product names in Arabic, «طلب» for an order, «موعد» for an appointment, «السلة» for the cart. The style guide records the decisions in this article: form of address, verbal nouns on controls, register per channel, digits, dates, currency, punctuation and how errors are built.

Give every string a key and context. A key such as checkout.payButton.label tells a translator far more than string_1047. Add a note where needed: where the string appears, its maximum length, what each placeholder holds ({name} is a first name, {count} a number of messages). Attach a screenshot of every screen; a translator who sees the screen chooses حفظ over توفير without being told.

Test with real users in the running build. Put the Arabic build on real phones in front of a handful of people from your audience, give them tasks such as signing up, booking and paying, and watch where they hesitate. An Emirati and an Egyptian user may flag different words, and each is right about their own reading. Then keep one named owner for the Arabic after launch.

Where we fit, and what it costs

We write Arabic interfaces as part of the products we build and as a standalone service. For an existing app or website, the usual job is a strings audit against the points above, a glossary and style guide, rewrites where needed, and an in-context review on the staging build. For a new product, the Arabic writer works alongside design from the first wireframe. Where a sign-up flow includes consent text, terms or a privacy policy, that text needs a legal translator, which is the daily work of our sister company, Smart World Legal Translation.

Prices start from these figures, excluding VAT: Arabic localization from AED 0.35 per word and complete bilingual website copy from AED 1,500, through our multilingual content service; a cross-platform app built bilingual from day one from AED 10,000, through app development. The final quote depends on the number of strings, screens and channels. If your Arabic interface feels translated and you are not sure why, send us a few screenshots and we will tell you what we would change first.

Sources

FAQ

Can AI write our Arabic microcopy?

It can produce useful first drafts, especially when you give it the screen, the glossary and the style guide. On its own it tends to apply the form of address inconsistently, carry English idioms over word for word and miss context, such as Save meaning حفظ rather than توفير. Every string still needs a native writer’s review in the running app.

Do we need a separate Arabic style guide if we already have an English one?

Yes, though one page is usually enough. Most of the decisions have no English equivalent: the form of address, verbal nouns on buttons, register per channel, digits, Hijri dates, Arabic punctuation and plural forms. The tone of voice can be shared between the two languages; the rules cannot.

Who should own the Arabic strings after launch?

One named person, in-house or at your agency, who approves every new or changed Arabic string before release. Arabic interfaces often degrade after launch, when a quick fix ships with an English-only string or an unreviewed machine translation. Treat a missing or unreviewed Arabic string as a reason to hold the release.

العربية