bloomz 
Part of our guide to school translation and language equity.
Two platforms can both claim translation, demo it convincingly, and deliver completely different experiences to a parent who reads Spanish or Arabic. The difference is not in the marketing copy. It is in how far the translation reaches. One translates the message and stops. The other translates everything the parent touches. For a family that speaks no English, that gap decides whether the platform is usable or just technically multilingual.
What message-only translation actually does
Message translation works on the body text of a communication. A teacher writes “Field trip permission is due Friday” in English, the parent has set their preferred language to Korean, and the platform renders that sentence in Korean. So far, so good.
Here is where it stops. The menu the parent uses to find the message stays in English. The “Reply” and “Sign” buttons stay in English. The permission form the message refers to opens in English. The settings, the navigation tabs, the notification labels, the form fields asking for a signature and a date, all of it stays in English. The platform translated the sentence and left the parent alone with an English app.
This is the model most school communication platforms use, including ParentSquare. It is not nothing. Translating the message text clears the easiest and most visible part of the problem, which is why it demos well. But it solves the part of communication that requires the least from the parent and skips the part that requires the most.
Where message-only translation breaks
The breakdown happens at the first action a parent has to take on their own.
A Korean-speaking mother reads the translated message about the permission form. She understands it. Now she has to act. She taps into the app, and the interface is in English. She needs to find the form, which is labeled in English. She opens it, and the fields are in English: student name, grade, parent signature, date, a checkbox next to a paragraph she cannot read. She is back to exactly where she would be with no translation at all, except now she knows there is something she is supposed to do and cannot.
Multiply that by every form, every RSVP, every fee, every conference sign-up across a school year. Message-only translation gets a family informed and then strands them at the threshold of every task. The result is a parent who receives everything and completes nothing, which looks, in the school’s data, indistinguishable from a parent who never engaged.
What full-app translation does instead
Full-app, or UI-level, translation renders the entire application in the parent’s language. Not just the message body. The menus, the buttons, the navigation, the settings, the notification labels, and critically the forms a parent has to fill out.
The same Korean-speaking mother sets her language once. From then on, the whole app is Korean. She finds the permission form under a Korean menu label, opens a form whose fields read in Korean, understands what she is consenting to, signs, and submits. She did not need anyone to sit beside her translating buttons. She completed the task the way an English-speaking parent would, which is the entire point.
Bloomz immersive translation is built this way. Every parent-facing surface translates into more than 250 languages, and a parent picks their language once rather than per message. You can see the full set in the supported languages list.
The right-to-left dimension
Translation also has a layout component that message-only tools routinely miss. Arabic, Urdu, Farsi, and Hebrew read right to left, and rendering them correctly is not just a matter of swapping words. The interface itself has to mirror: navigation flips, text aligns to the right, the reading flow reverses. Dropping translated Arabic into a left-to-right layout produces something a fluent reader has to decode rather than read.
Bloomz mirrors the layout for right-to-left languages so the experience reads naturally rather than feeling like English wearing Arabic words. We go deeper on what this takes in our post on reaching Arabic and Urdu-speaking families with proper RTL.
The one evaluation test that cuts through it
Vendors will all say they support translation. The way to tell message-only from full-app is simple, and it works in any sales conversation.
Ask to see the live app, in a real family’s language, on an actual device. Not a slide. Not a translated message in a screenshot. The working application, set to Spanish or Arabic, with a real form open.
Then watch for a few things:
- Are the menus and navigation in the family’s language, or only the message text?
- Open a permission or registration form. Are the field labels translated, or English?
- Switch to Arabic or Urdu. Does the layout mirror right to left, or does translated text sit in a left-to-right frame?
- How many languages are actually supported, and is it the same depth across all of them?
A platform that only does message translation will steer you toward a slide or a demo message at exactly this point, because the live app in another language is where the gap shows. A platform built for full-app translation will just turn it on and let you look.
The distinction is not a technicality. It is the difference between a parent who can run their child’s school life in their own language and one who gets translated headlines followed by English walls. If language access is something your district is accountable for, the depth of translation is the thing to verify, not the existence of a translate button.
To see the live app running in any of 250-plus languages, including proper right-to-left layouts, schedule a demo.