The short answer
Choose around the people and the service, not the word 'app'. A browser-based sermon translation tool is usually the lowest-friction option for multilingual visitors because it works on the phone already in their pocket. Keep a human route for pastoral conversation and consider church-owned devices or a receiver system where phones are unsuitable.
- Best for first-time visitors and several languages at once — a browser-based QR-code reader
- Best for sensitive prayer, safeguarding, counselling, and dialogue — a trusted human interpreter
- Best where phones are discouraged or internet access is unreliable — a receiver system or church-owned device
- Best buying test — run ten minutes of real sermon audio and ask a fluent listener whether they could follow the meaning
The three kinds of 'sermon translation app'
When churches say 'app', they usually mean one of three quite different things. Knowing which you actually need saves a lot of wasted setup time:
- Downloaded native apps — each attendee installs an app from an app store, creates an account, and opens it during the service
- Browser-based tools — attendees scan a QR code and the translation opens instantly in their phone's existing browser, with nothing to install and no account
- Hardware receiver systems — the church hands out physical earpiece devices tuned to a single interpreter channel
Why 'app required' quietly kills adoption
A downloaded app sounds modern, but on a Sunday morning it adds friction at exactly the wrong moment. A first-time visitor who doesn't speak the local language has to find the right app among dozens of similarly named results, trust it enough to install it, wait on the church WiFi for the download, then create an account — all before the sermon starts. Every one of those steps loses people. Browser-based translation removes the entire chain: there is nothing to download, nothing to log into, and nothing to update.
How browser-based sermon translation works — step by step
Voco is browser-based by design. From the attendee's side, the whole experience is four short steps:
- 1Scan the QR codeThe church displays a QR code on screen or in the bulletin. The attendee points their phone camera at it — modern iOS and Android scan QR codes natively, with no separate scanner app.
- 2The reader opens in the browserA lightweight page loads in whatever browser the phone already has — Safari, Chrome, or Edge. There's no install prompt, no app store, and no account or password to create.
- 3Choose a languageThe attendee taps their language from the list of 200+ options. Each person in the room can pick a different one independently from the same QR code.
- 4Read along liveTranslated segments appear throughout the sermon. Listeners read along on the device already in their pocket.
Browser-based vs downloaded app — the honest comparison
- Setup for attendees — browser: scan and read in ~20 seconds; downloaded app: find, install, register, then open
- Works on every phone — browser: any phone with a modern browser (iOS 14+/Android 8+); downloaded app: limited to supported OS versions and storage space
- Updates — browser: always the latest version, nothing for attendees to maintain; downloaded app: attendees must keep it updated or features break
- First-time guests — browser: zero barrier, ideal for visitors; downloaded app: most guests won't install an unfamiliar app mid-service
- Languages — Voco offers 200+ attendee output languages from one session, with each listener choosing independently
- Cost model — Voco starts at £6/week with unlimited attendees, not a per-seat or per-download fee
What you genuinely give up by going browser-based
An honest guide should name the trade-offs. A browser page can't send push notifications, and it relies on a live internet connection rather than caching a service for offline replay. For live sermon translation neither matters much — attendees are in the room while the service is happening, and the church's connection drives the translation regardless. If your specific need is offline playback of recorded sermons, a downloaded app or a separate subtitle file is a better fit. For real-time translation of a live service, browser-based is the stronger choice.
When a downloaded app or hardware still makes sense
Browser-based translation suits the vast majority of weekly services, but not every context. Hardware earpiece systems still have a place where phone use is discouraged, for congregants who aren't comfortable with smartphones, or in venues with no reliable connectivity. A downloaded app may suit a closed community that already uses one shared platform daily. For an open-door church wanting any visitor to follow along instantly, the no-download browser approach removes the most friction.