Arabic-First UX: Designing Offers Apps GCC Customers Actually Enjoy

In the Gulf, many customers switch between Arabic and English several times a day. They may read work email in English, message family in Arabic and use their banking app in whichever language feels natural at that moment. For them, a good app is one that feels equally at home in both.

Yet many banking and offers apps are still designed in English and "translated" at the end. Customers notice immediately. This guide covers what it takes to design an Arabic-first experience that works just as well in English.

Why "Arabic-first" rather than "Arabic too"

Arabic-first does not mean Arabic-only. It means Arabic is considered from the first sketch, not added in the last sprint. The difference shows up in dozens of small details:

• Layouts that mirror correctly, rather than breaking.
• Text that fits, rather than being truncated.
• Copy that sounds natural, rather than machine-translated.
• Icons, numbers and dates that make sense in context.

When those details are right, customers trust the product more. When they are wrong, the app feels like it was built for someone else.

Layout and direction

Mirror the whole interface, thoughtfully

In a right-to-left (RTL) layout, the reading direction flips. Navigation, back buttons, progress bars, carousels and lists should all mirror so the flow feels natural.

But not everything should flip:

• Logos, photos and maps stay as they are.
• Media controls such as play buttons generally keep their standard orientation.
• Charts over time need a deliberate decision; be consistent across the app.
• Directional icons like arrows should point in the direction of reading.

Use logical, not physical, spacing

Designers and developers should think in terms of "start" and "end" rather than "left" and "right". Modern design tools and front-end frameworks support logical properties, which make mirroring largely automatic and far less error-prone.

Typography

Arabic script has different proportions from Latin script. Text that fits neatly in English may overflow in Arabic, or look too small.

• Choose a typeface family with high-quality Arabic and Latin designs that work well together.
• Allow for slightly larger font sizes or line heights in Arabic for readability.
• Avoid all-caps and letter-spacing tricks borrowed from English; they have no Arabic equivalent.
• Test long merchant names and offer titles in both languages, not just short labels.

Numbers, currencies and dates

GCC customers are comfortable with both Western digits (0-9) and Arabic-Indic digits. Many banking apps use Western digits in both languages for consistency with cards, statements and receipts. Whatever you choose, apply it consistently.

Other details to get right:

• Currencies: show the currency code or symbol clearly, for example BHD, SAR, AED, and format decimals correctly. Bahraini dinars use three decimal places.
• Dates: support the Gregorian calendar, and consider showing Hijri dates where relevant, such as for Ramadan offers.
• Weekends: remember that the working week differs across GCC markets; "weekend offer" should mean the right days for each market.
• Phone numbers and codes: keep them left-to-right inside RTL text so they remain readable.

Copywriting

Good Arabic copy is written, not translated. For banking and offers, that usually means clear Modern Standard Arabic that feels warm and direct, not stiff or overly formal.

• Write both versions from the same brief, rather than translating one into the other.
• Keep offer titles short. "خصم 20% على الغداء" is clearer than a literal translation of a long English headline.
• Use consistent terminology for key concepts: offer, redeem, card, merchant. Build a bilingual glossary early.
• Avoid awkward transliteration of English marketing terms when a natural Arabic phrase exists.
• Check tone for the audience. Premium cardholders, students and families may each need a slightly different voice.

Search and content

Customers will search in both languages, and sometimes mix them. A good offers app should:

• Store merchant names and offer text in both languages.
• Match searches regardless of which language is used, including common spelling variations.
• Handle Arabic characters that have several forms, such as different forms of alef and ya, so search is forgiving.

Forms and input

• Align form labels and inputs to the start of the reading direction.
• Keep fields such as email, card digits and mobile numbers left-to-right.
• Make error messages specific and polite in both languages.
• Test the keyboard experience on real devices with Arabic keyboards enabled.

Testing with real users

No checklist replaces watching real people use the product. Include Arabic-preferring users from different GCC markets in usability testing. Pay attention to:

• Where they hesitate or re-read.
• Words that feel unnatural or too formal.
• Screens where the layout feels "wrong" even if nothing is technically broken.

Also test switching languages mid-session. Customers do it more often than teams expect.

Merchants need Arabic too

The merchant side matters as much as the customer side. Merchant validation apps, dashboards, contracts and support should all work properly in Arabic. Many small business owners and front-line staff prefer it, and a merchant who is comfortable with the tools will honour offers more reliably.

A quick Arabic-first checklist

• Is every screen designed and reviewed in both Arabic and English?
• Does the layout mirror correctly, with deliberate exceptions?
• Are numbers, currencies and dates formatted consistently?
• Is Arabic copy written natively, with a shared glossary?
• Does search work across both languages and spelling variants?
• Are merchant tools and contracts available in Arabic?

cardoff.ai was built in Bahrain with Arabic and English as equal first languages, full RTL support for customer apps, websites and merchant tools, and multi-currency formatting across the GCC. If you want your offers programme to feel native to every customer, we would be glad to show you how it looks in both languages.