Behvandi Build intelligent systems
Back to blog

Studio notes

A trilingual product: Persian, English, and Arabic

A trilingual product in 2026 is not a post-launch translation. Direction, calendar, and per-language SEO have to live in the architecture.

Right-to-left multilingual interface for Persian and Arabic

I have seen the same product too often: a clean Persian (or English) core, a translation file bolted on, and Arabic crammed in the week before a Gulf partner visit. Buttons jump, a Jalali date leaks onto the English screen, and search indexes a half-empty locale. A trilingual product is not a marketing badge. It is an architecture choice.

The region in 2026 asks for this without romance. A team in Tehran, a buyer in Dubai, the contract in English. If the system does not know which string belongs to which culture from day one, flags and CSS will not save you later.

RTL is not a mirror of left and right

Persian and Arabic run right to left. Numbers, national ids, money, and URLs do not. When a numeric field follows the prose direction, operators mistype and you file it as a “weird bug.” Calendars too: store Gregorian, show Jalali only where the UI is Persian. English and Arabic keep Gregorian. These boring details are what make a product livable.

Each language needs its own SEO pack: title, description, slug, image. Publishing English with Persian body copy — or the reverse — means that locale’s listing is a lie. I would rather ship one complete language than three half ones.

Translation changes the product, not just the words

Arabic and Persian are not the same length as English. A three-word nav in English can wrap in Persian. That belongs in the first layout, not the night before launch. Some pages should stay unreleased in a language until the copy exists. An empty translated shell is worse than an honest omission.

If you are on a custom path, do not treat this layer as cheap. No-code usually makes one language second-class. On when custom is the right call, see custom software or no-code, and on staying alive after go-live evolvable systems.

Before you promise an “international site”

Ask whether three languages means three markets with an editorial commitment, or a polite vitrine. If there is no commitment, two complete languages beat three theatrical ones. If there is, start from routes and SEO packs, not a flag in the header. To put this on a real product, the order form is the door.

Comments

No comments yet. Be the first to write one.

Email or mobile is for the studio only and is not shown on the site.