Arabic & GCC2 min read

Building RTL Design Systems in Figma

An RTL design system in Figma works when direction is a documented property of the system, not a separate copy of every component. Build the components once, define which properties flip, and give the team a clear way to preview both directions from the same source.

Decide what flips and what does not

Navigation arrows, progress indicators, leading icons and text alignment usually flip. Logos, media playback controls, numbers, code snippets and some charts do not. Write this list as part of the system, with examples, so designers do not decide differently on each screen.

Use auto layout with direction in mind

In Figma, auto layout can respond to direction when the frames are built correctly. Test each component in both directions. Pay attention to padding that is asymmetrical, icons that carry meaning, and text fields where the label and the helper text swap sides.

Create direction-aware tokens

Define spacing and alignment tokens with logical names such as start and end, not left and right. Engineers can then map those tokens to direction at build time. A token named 'left padding' forces a copy of every component for Arabic.

Build a bilingual test page

Create one page that shows each core component in English and Arabic side by side, with realistic copy and long strings. Review it whenever you change the library. This page catches flipped icons, clipped labels and broken alignment before they reach the product.

Document the rules for engineers

The handoff must state which components support direction switching, how the switch is triggered, which tokens are logical, and which elements stay left-to-right. Keep the documentation next to the component, in the same tool or the same repository.

Common failures

  • Icons that imply a direction, such as back or forward, that do not flip
  • Numbers and codes that are reversed because the container flipped
  • Text fields with prefixes or suffixes placed on the wrong side
  • Hard-coded widths that work in English and clip Arabic labels

A maintenance habit

Add the bilingual test page to the review checklist for every release of the library. A design system is only as good as the last change, and RTL problems often return quietly when a new component is added without the same care.

Next step

Get help improving conversion

Send me the page or flow that loses people. I will tell you where the friction is and what to change first.

Open the conversion page