Arabic-First Design: Why Right-to-Left Support Isn't an Afterthought
Translating English text into Arabic is the easy part. The hard part — the part most tools quietly get wrong — is everything else that has to flip when a layout goes from left-to-right to right-to-left: where the logo sits, which direction a carousel scrolls, where a back button points, whether an icon that implies direction (an arrow, a chevron) still means the same thing once it's mirrored.
Get this wrong, and the result is a page that reads in Arabic but behaves in English — buttons in the wrong place, icons pointing the wrong way, a layout that feels subtly foreign even to a fluent Arabic reader, because their eyes expect the whole page to flow the way their language does, not just the words on it.
Linkaty was built the other way around: right-to-left is the default layout, not a translation applied on top of an English-first design. Every element — navigation, forms, the dashboard itself — was built to flow correctly from day one, with English added as the second language rather than Arabic being retrofitted as an afterthought.
The same care extends to typography: real Arabic web fonts, not a generic fallback font that happens to render Arabic characters without actually looking like real Arabic type design. For a business whose customers read and think in Arabic first, this isn't a nice-to-have detail — it's the difference between a page that feels like it was built for them, and one that feels like it was translated at them.