Mobile Apps

8 min read

Arabic-First App Design: Building RTL Properly

Why bolting Arabic onto a finished app breaks it, and what designing right-to-left from the layout system up actually involves on mobile.

By NxFold

Updated 23 Oct 2026

Arabic-First App Design: Building RTL Properly

Product teams sometimes start with one language and postpone the second. That can look like a copy task, but direction also affects layout, navigation, forms and interaction behavior.

RTL is not only a text property. As screens and components are built around left-to-right assumptions, supporting RTL can require reviewing layout and controls throughout the app. The amount of rework depends on the existing design system and implementation.

The Short Answer

Translation changes the copy; localisation also affects product and technical decisions. Plan for direction, input, formats and content before the component patterns are fixed. A later RTL audit is still possible, but its scope depends on the existing app.

If a meaningful share of your users read Arabic first, include right-to-left behavior in the design and technical scope from the start. Direction affects navigation, alignment, text flow, forms and interaction patterns. Retrofitting can require changes across screens and components; the work depends on how the existing app was built.

In Halaly, NxFold built an Arabic marketplace app for farm-related listings and services. The documented interface shows right-to-left layout, listing search, category navigation and listing cards with prices in Kuwaiti dinars. Those are observable interface details; they do not establish usage, transaction volume or publishing speed.

The web version of this argument is in Arabic website design in Dubai. This one is about mobile, where the constraints are different and less forgiving.

What Mirrors and What Must Not

This is where most retrofitted apps give themselves away.

Mirrors: the layout axis, navigation direction, back gestures, drawer position, progress indicators, list item alignment, and directional icons like arrows and chevrons.

Does not mirror: logos, media playback controls (play always points the same way), clock faces, physical-object imagery, and anything representing a real-world object whose orientation is fixed.

Choose number formats deliberately. The right display can depend on the audience, locale, currency and field. Test prices, quantities, dates and phone numbers in the contexts where people use them; do not infer a preference from the interface language alone. Keep phone numbers, URLs and identifiers readable as left-to-right runs within Arabic text.

Mixed-direction text is the hard case. An Arabic sentence containing an English brand name, a URL or a number needs bidirectional handling. Test a product title with an English brand, an order ID, a URL, and a phone number inside Arabic copy. Check punctuation, brackets and currency placement in both interface directions; isolate direction-sensitive tokens where needed so they do not reorder with the surrounding sentence.

Typography Is Not a Font Swap

Arabic has different metrics from Latin, and treating the font as a variable while holding everything else constant produces text that is technically correct and physically uncomfortable.

Check line height and font size in context. Some Arabic typefaces need different spacing from the Latin pairing, but the right settings depend on the font, size and device. Review real paragraphs, labels and validation messages for clipping and readability.

Compare type at the actual display size. Do not assume that matching pixel values will look equally readable across the Arabic and Latin typefaces.

Weights do not map across. A Latin font's regular and its Arabic counterpart's regular can look noticeably different in density. Pair them by eye rather than by name.

Letter-spacing does not apply. Arabic is connected script; tracking that improves a Latin uppercase label breaks Arabic words apart. Any design system with letter-spacing on labels needs that rule disabled under Arabic.

Practically, this means the type scale is a pair of scales, and the design system needs a language-aware layer rather than a single set of tokens.

Building It Into the System

The engineering principle is simple to state: never hard-code direction.

Use logical properties throughout — start and end rather than left and right, for padding, margins, alignment and positioning. Both React Native and Flutter support this, and a codebase written with logical properties from day one flips almost for free. One written with left and right requires a manual audit of every screen.

The two places it still breaks even when you have done this correctly:

Custom animations and gestures. A swipe-to-delete built for one direction may feel backwards in RTL. Test it against the operating system’s navigation conventions and the intended action.

Absolutely positioned elements. Anything placed by coordinate rather than by layout will not flip. Badges, floating buttons and overlays are the usual offenders.

Test both directions continuously. Not in a QA pass at the end — in every review. An RTL bug found the week before launch is a bug found too late, and an app that is only ever demoed in English will ship with RTL problems nobody saw.

Content, Not Just Interface

The interface is the easy half.

Voice and register. Modern Standard Arabic is correct and can read stiff for a consumer app; dialect is warmer and less portable across the GCC. Most consumer products land on simplified MSA that reads naturally. This is an editorial decision, not a translation one, and it should be made by someone who writes Arabic rather than someone who checks it.

Review Arabic copy with fluent writers. Check terminology, tone and task instructions in context; a grammatically correct translation can still use the wrong product term or register.

User-generated content is mixed. Listings, reviews and messages will arrive in both languages regardless of interface setting. Search has to handle both, and the layout has to render an Arabic listing inside an English interface without breaking.

Store listing localisation is separate work. Review the title, description, keywords and screenshots for each supported locale, while keeping them consistent with the app itself.

RTL Text and Form Checks

Use a small set of repeatable examples in design review and QA:

  • Put an English product or company name inside an Arabic sentence, including parentheses and punctuation.
  • Show an international phone number such as +971 50 123 4567 beside an Arabic label; enter it, trigger validation and confirm the digits remain in order.
  • Display a price such as AED 1,250.00 and an Arabic numeral alternative if the product supports it; check currency placement and total calculations.
  • Submit a form with Arabic and English names, an email address and an order ID. Check required-field, invalid-format and success messages in both locales.
  • Test search results and user-generated listings when their language differs from the interface language.

Record each case as pass / fail / not tested on a real representative screen. A translated label alone does not verify layout, input, validation or mixed-direction behavior.

What It Costs

There is no reliable universal percentage for the extra design, engineering or QA effort. Scope depends on the number of screens, existing layout assumptions, custom components, animations, input behavior, content volume and language-review process. Planning RTL early makes those decisions visible while the layout system is being chosen; adding it later may require auditing and retesting affected screens.

For overall app cost ranges, mobile app development in Dubai is the current guide. And if discoverability matters as much as usability, Arabic SEO in the UAE covers the other half.

Frequently Asked Questions

Can we add Arabic later? Yes. The work depends on the layout and component choices already in the app. Review direction-specific styles, forms, navigation, animations and mixed-language content, then estimate the affected screens before setting the scope. If Arabic is on the roadmap, use direction-aware layout patterns from the start.

Does RTL require a separate design for every screen? Not necessarily. Direction-aware layout rules can cover many components, while typography, mixed-direction strings, navigation, custom gestures and overlays still need review in both directions. Estimate from the actual screen and component inventory.

Should we use Eastern or Western Arabic numerals? Decide by the audience, locale, field and product convention. Test the chosen display for prices, dates and quantities, and ensure phone-number entry and validation preserve the intended digit order.

Which Arabic typefaces work on mobile? Choose one designed for screen use with a matching weight range to your Latin face, and pair them by eye rather than by name. Expect to increase line height and size relative to your Latin settings.

Do we need separate App Store listings? You need localised store metadata — title, description, keywords and screenshots in Arabic — within the same listing. It is where a large share of organic discovery happens and it is routinely skipped.

How do we test RTL properly? Continuously, not at the end. Every review should be done in both directions, and at least one person on the team should read Arabic. Bidirectional punctuation errors are invisible to non-readers and obvious to users.

What about mixed Arabic and English content? Plan for it, because users will produce it. Search must handle both scripts, layouts must render an Arabic listing inside an English interface, and bidirectional text handling has to be correct rather than approximately correct.

MSA or dialect? Simplified Modern Standard Arabic for most consumer products — natural enough to feel human, portable across the GCC. Dialect is warmer but limits your market. Have it written by someone who writes Arabic, not translated by someone who checks it.

The Bottom Line

Arabic-first is not a feature or a courtesy. It is a decision about what your layout system assumes, and it is one of the very few decisions in an app build that is genuinely difficult to reverse.

If Arabic is a core language for the product, include its layout, content and input behavior in the design system and acceptance checks. The distinction between translated copy and a complete Arabic experience is visible in navigation, mixed text, forms and feedback.

If you are scoping a product for an Arabic-speaking audience, get in touch. The documented Halaly interface is one example of Arabic-first mobile work; the broader service scope is on mobile app development.

Arabic RTLMobile App DevelopmentBilingualUXLocalisationDubaiUAE

Have a project in mind?

Ideas to put into practice.

Turn what you have learned into a clearer plan for your website or product. Tell us what you want to build.

Discuss your project requirements
All articles

Contact

Have an idea? Let's make it real.

Tell us about your project.

Speak directly with the team building your project.

  • Free quote within 24 hours
  • No commitment, no pressure
  • Fixed timeline & price upfront
Start a project

Talk to us directly