A translation tool exists for people who do not understand the language of the room. So if its first screen is in that language, it has already failed them. From the start we decided the joining had to be solved first: the join page, the listener screens and the site come in many languages, chosen separately from the language a guest listens in.
The first thing a guest sees is not the translation. It is the page that gets them to it.
Picture a woman visiting a church for the first time. She does not speak the language of the service. Somebody kindly points at the QR code on the screen, she scans it, and her phone opens a page that says "Join", "Choose a language", "Interface language". Every word of it in the one language she came here not understanding.
The tool exists so that she can follow the sermon. And the door to it is written in the language she cannot read.
From the start we believed one simple thing: a translation tool must speak the listener's language itself. If a listener joins to hear the sermon and cannot understand the join screen in the first place, what use is the tool? The translation can be faithful, the voice can be clear, Smart Hints can explain every verse the pastor quotes, and none of it matters if she gives up on the first screen.
So when we planned how MulingStream should grow into other languages, the listener came first. Our plan put it in one sentence: listeners use us precisely because they do not speak the language of the room, so showing them the interface in that language defeats the purpose. Before the account pages, before the pricing, before anything a church leader sees, we wanted the joining problem solved.
If a guest cannot understand the screen that lets them in, the translation behind it does not matter.
There are two languages on a listener's phone, and they are not the same thing.
The first is the language they listen in or read along in. That is the translation itself, and a guest can choose it from 200+ languages; the languages page shows what that means.
The second is the language of the page: the buttons, the labels, the little notes that say what to tap. We call it the interface language.
We keep the two apart on purpose, because people are different. A Persian speaker may want the buttons in Persian and the sermon in Persian. A student from Ukraine may read the buttons in English without a second thought and still want to listen in Ukrainian. A grandmother may want both in her own language while her grandson beside her switches the page to English. The page says it in plain words, too: changing the interface language changes only the buttons and text on the page, never what you hear.
On 5 August 2026 the listener screens and the whole site went out in many languages at once. Not English with a few translated buttons: the join page, the listening screen, the settings, the help notes, the FAQs and the pages around them, translated in full, so a guest never meets a stray English sentence halfway through.
A few details mattered more than they look.
Right to left, done properly. For Arabic, Persian and Hebrew the whole page turns around, not just the text. Menus, arrows and sliders run the way the reader reads. Switching without losing a word. A listener can change the interface language in the middle of a sermon. The page changes around them while the translation keeps playing. Nothing reloads and nothing drops. Nothing to install. It all happens in the phone's browser, so there is no app store page in a foreign language to get through first. The same for the church. The church dashboard, the pricing and the help come in many languages too, so a pastor can set up in their own language in about two minutes.
The people who need translation most are the least likely to ask for help with it. A guest who cannot read the join page does not walk up to the sound desk to say so. They put the phone back in their pocket and sit through the service quietly.
When the page greets them in their own language, the welcome starts before the sermon does. And the church does nothing extra for it: no second link per language, no settings to change, no volunteer standing at the door explaining buttons. One link or one QR code, and every guest finds their own way in.
That is the whole of it. If you would like to feel it the way a guest does, open the listener demo room on your phone, switch the page into another language and listen. More about the listener side is on how it works for listeners and on the features for listeners.
A menu labelled "Interface language" is no help to someone who cannot read those two words. So since 24 September 2026 the listener page asks the question for them.
When a room is about a language, because the speaker speaks it, because the room carries it, or because the church told us its guests would need it, the page shows one short line in that language and in its own script: "Would you like to see this page in Persian?", written in Persian, with one button that says yes. One tap, and the page is theirs.
We only ask in a language whose interface we have fully translated. Offering a language and then leaving the guest on a page that is still in English would be worse than not asking at all.
The join page now has two tabs. On the first, the guest chooses the language to listen in before they enter the room. On the second, called Interface, they choose the language of the page. And when they come back next week, the language they chose last time is already selected.
200+ languages, with their regional variants, and the page around them in the guest's own language.