The Word for Church
Translating a church app looks, from a distance, like a software task. You export the text the app displays, run it through a translation system, import it back, and ship. With the tools now available, a team can put an app into dozens of languages in an afternoon. I know, because building SoapBox for churches in many countries put that exact afternoon in front of us.
It turned out to be nothing of the kind. Not because the tools are poor. For most of what an app says, they are remarkably good. It is because a small number of words in a church app are not ordinary words at all.
The words that carry a faith
Most of the text in any app is plumbing. Save. Cancel. Settings. Try again. Your changes have been saved. A machine translates those well, and if it gets one slightly wrong, the cost is a moment of confusion.
Then there is a short list of words that do something different. Church. Sermon. Congregation. Ministry. Prayer. Giving. These are not labels on buttons. They carry a faith. Each one has a history in each language, shaped by how the gospel arrived there, which translation of the Bible people grew up with, and how their own tradition talks about gathering, teaching and generosity.
Get one of those slightly wrong, and the app does not merely read oddly. It teaches the wrong thing, quietly, on every screen, to people who trust it.
The traps are not exotic. In more than one language, the most common translation of "ministry" is a government department, so a screen inviting someone to join a ministry can read like an invitation to join a branch of the state. The everyday word for "church" can mean the building rather than the people, which is exactly the distinction a pastor spends years trying to teach. A word for "giving" can carry the flavor of a fee or a tax, which is the opposite of what a gift is. None of these are mistakes a translation system is likely to flag, because each is a perfectly correct translation of the word in some other context.
What we changed
We learned this by finding translations that were wrong in exactly these ways, and taking them out. That experience changed how we work, and three rules came out of it.
The few words that matter live in a binding glossary. For each language, the words for church, sermon, congregation, ministry, prayer and giving are settled once, deliberately, and reviewed by native speakers wherever we can find them. After that, every translation must use them. A machine does not get a vote on what the word for church is.
Every translation is checked by translating it back. A translation is handed, without the original, to a separate pass that turns it back into English. Then we compare what comes out with what we meant to say. If "join this ministry" comes back as "join this department," we have our answer. It is a simple check, and it catches things that look perfectly fluent on the screen.
Where money moves, we do not guess. If a string on a giving screen has not been verified in a language, it stays in English until it is. That rule costs us something. A screen in English, inside an app that otherwise speaks someone's own language, is a small embarrassment, and people notice it. But a wrong word on the screen where someone gives to their church is not a small embarrassment. It is a breach of trust in the one place we have promised never to break it.
Heart language
Missionaries and Bible translators have a phrase for the language a person prays in when nobody is listening: their heart language. It is often not the language of school or work. It is the language of home, of grief, of the oldest prayers they know. The long, patient work of Bible translation exists because the church has always believed that people should hear the gospel in that language, not in a language they merely understand.
A church app is a very small thing next to that work. But it sits in the same lineage, whether its builders know it or not. When it speaks to someone in their heart language, it is borrowing words that other people spent generations getting right. The least we can do is not get them wrong carelessly.
Fast is not faithful
AI made translation fast, and I am grateful for it. It is part of why a small team can serve churches in so many countries at all. But fast and faithful are different things. A model can produce a fluent sentence in almost any language in a moment. It cannot know which of the possible words for church a particular congregation would recognize as theirs.
There is a humility in this that I think is healthy for a technology company. Software teams like to believe that every problem yields to a better system. This one partly does: the glossary, the back-translation and the rule about money are all systems. But at the center of each of them is a person who knows something we do not, and the systems exist mainly to make sure we ask that person before we ship, not after a congregation has already been reading the wrong word for months.
That knowledge lives with people: pastors, translators, ordinary believers who can read a screen and say, gently, that is not how we say it. Our job is to ask them, to listen, and to build the asking into the process instead of hoping the machine got it right. The word for church is too important to leave to an average.