A woman visited us one Sunday. She had come from Germany, and she spoke German and Russian. No English at all.

She stayed for the whole service. She stood when everyone else stood, sat when everyone else sat, and afterwards she shook hands at the door and smiled. Then she went home carrying nothing. An hour of preaching, and not one sentence of it had reached her.

Nobody had done anything wrong. There was no interpreter free that morning, and even if there had been, an interpreter for one visitor is a lot to arrange: you need a person who speaks both languages, who is willing to sit beside a stranger and whisper for an hour, and who is not already serving somewhere else. Most churches have one such person, for one language, some of the time.

So the visitor sat through something that mattered, and left with nothing to take away from it. That was the problem we started with.

What was actually missing

It is easy to describe this as a translation problem, but that is not quite it. Translation existed. Phones could already translate. What was missing was a way for one person at the front to be understood by one person at the back, in a language nobody else in the room needed, without anyone having to organise anything on the day.

The service could not change shape around one visitor. The preaching was in English, and it was going to stay in English. The question was whether the visitor could still follow it.

A room, a code, and a phone in her hand

What we built is simple enough to explain in a sentence. One phone at the front listens to the preaching. It creates a room with a short code. Anyone in the building who needs it opens the app, types the code, and picks their own language. The words appear on their phone as they are spoken.

The visitor did not need an account, a subscription, or any help from us beyond the code. She needed her own phone and the language she thinks in.

The next time she was with us, she read the whole message in Russian while it was being preached in English.

That was the part we expected. Here is the part we did not.

She could talk about it afterwards. During the week, with other Russian speakers who had not been in the room at all, she could say what the message had been about. The service was in English and stayed in English, but the understanding travelled out of the building in another language entirely. A visitor who used to leave with nothing now left with something she could pass on.

The thing nobody asked for

Then people who speak perfect English started using it.

You know the moment. The preacher gives a reference, and you go looking for it. Thin pages, wrong book, back a little, forward a little. By the time you have your finger on the verse, he has said three more sentences — often the sentences that explain why he sent you there. You look up, the room is nodding, and you have lost the thread.

With the app running, the last few lines are still sitting on the screen. You find your passage, glance down, catch up in five seconds, and you are back with everyone else. Nothing was missed. It was only delayed.

We had built a bridge for a visitor from Germany, and the regulars started walking across it.

What it changes for a congregation

Once the barrier is one phone rather than one rota, the arithmetic of a church changes.

Visitors stop being a special case.

Nobody has to be found, briefed, or thanked afterwards. The code goes up, and whoever needs it uses it.

More than one language at a time.

A Ukrainian family, a Brazilian student and a Romanian couple can be in the same service, each reading in their own language, without three interpreters and three sets of headphones.

The message outlives the hour.

People who followed in their own language can talk about it afterwards, in that language, with people who were never there.

Nobody is singled out.

No booth, no headset, no hand raised to ask for help. A phone in a lap looks like every other phone in the room.

How a church would start

  1. One phone at the front.

    Whoever is running sound opens the app on the Speaker tab, sets the spoken language to English, and starts the room.

  2. Put the code where people can see it.

    On the screen, in the bulletin, or on a card at the welcome desk. Five characters.

  3. Everyone else just joins.

    They open the app, type the code, choose their language, and read. Listeners never pay and never need an account.

Try it first on a Sunday evening, or in a home group, before you put the code on the main screen. You will know within one message whether it earns its place.

What we will not claim

This is not a human interpreter, and we do not pretend it is. A live machine translation of a sermon is close enough to follow and honest enough to trust for meaning, but it will not give you the preacher's rhythm, and it will not always land an idiom the way he meant it. If your church has a gifted interpreter and a congregation that needs one language, keep them.

What this is for is everyone else — the visitor you did not know was coming, the language you do not have covered, the week your interpreter is away, the person at the back who would never ask.

How many people can join depends on the speaker's plan: 4, 8 or 16, the speaker included. That is where the plans sit today because it is what has been asked for so far, not a limit of what the app can do. If your congregation needs a bigger room, write to support@ytranslate.app.

One visitor is the whole point

Churches count carefully, and it is tempting to justify something like this by numbers: so many languages, so many visitors, so many downloads. That is not how it started.

It started with one woman who came, listened for an hour, understood nothing, and went home. Everything since has been an attempt to make sure that when she comes back, she leaves with the message.

Looking for more on how yTranslate works? Visit the yTranslate blog.