bloomz 
Part of our guide to school translation and language equity.
Many districts now serve growing communities of Arabic, Urdu, Farsi, and Hebrew-speaking families. These languages share a feature that most school communication tools handle poorly: they read right to left. Translating the words is the easy part. Presenting them in an interface that actually reads naturally, with the layout, navigation, and reading order all flowing the right direction, is where most platforms quietly fall short. If your district serves these families, it is worth knowing the difference between translation that technically works and translation that genuinely reads.
Right-to-left is a layout problem, not just a text problem
When a language reads right to left, it is not only the sentence that flips. The whole reading experience expects to flow from the right:
- Navigation and menus belong on the right, where the eye starts.
- Text aligns to the right, and lines progress right to left.
- Directional icons, like back arrows and progress indicators, should point the correct way.
- Forms and lists read in the right-to-left order.
A platform that simply drops right-to-left text into a left-to-right layout produces something subtly broken: correctly translated words arranged in a way that fights how the reader naturally moves through them. Buttons sit in unexpected places, alignment feels off, and the experience signals, in a quiet way, that these families were an afterthought.
What “RTL done right” looks like
Proper right-to-left support mirrors the entire interface, not just the message text. The navigation moves to the right side, the layout flips, icons reorient, and reading order follows the language. The result is an app that a native Arabic or Urdu reader operates exactly as comfortably as an English reader operates the English version. It reads as native, not translated.
The test is simple, and worth insisting on during any evaluation. Ask to see the live app in Arabic, on a real screen, and watch whether the whole interface flips or only the words change. A slide with translated text proves nothing, while a working screen tells you everything.
Why this matters more than it seems
It is tempting to treat right-to-left as a niche detail, but it carries real weight:
- Equity and access. Families who cannot comfortably navigate the app cannot participate in it. The barrier is invisible to English-speaking staff and very real to the family.
- Trust. An interface that obviously was not built with a community in mind tells that community exactly where they stand. A naturally readable one earns the benefit of the doubt instead.
- Actual usage. Access that is awkward goes unused. Families fall back to asking a bilingual relative or simply disengaging, which undoes the point of offering the language at all.
For a district that has invested in reaching multilingual families, getting right-to-left wrong undercuts the rest of the effort precisely for the communities that are often hardest to reach.
Beyond the interface: two-way and voice
Reading the app is the start. Genuine inclusion means an Arabic or Urdu-speaking family can also reply in their language and have staff receive it in English, complete forms in their language, and receive translated voice communication, not just app text. Right-to-left support in the interface, paired with two-way translation across channels, is what makes participation real rather than nominal.
How Bloomz approaches it
Bloomz delivers immersive translation that includes full right-to-left layout mirroring for Arabic, Urdu, Farsi, and Hebrew. The entire interface flips: navigation, icons, alignment, and reading order, so the app reads natively rather than looking like translated text bolted onto an English layout. Translation is two-way across app, email, SMS, and voice, and you can check the specific languages your families speak on the supported languages page.
Judge it the way families will
For Arabic, Urdu, Farsi, and Hebrew-speaking families, translated words in a left-to-right app are only half the job. Right-to-left done right means the whole interface reads the way the language does. When you evaluate platforms, do not accept a translated screenshot. Ask to see the live app flip, and judge it the way those families will. If you serve right-to-left language communities, schedule a demo and ask to see Arabic and Urdu live, full interface and all.