Presentation

How to control your church presentation from your phone

By Mambo Mutinda · Founder & CEO, TajiCast

1 August 2026 · Updated 8 September 2026

The screen is at the front. The computer running it is usually at the back, or in a side room, or behind a half-wall where nobody can see the stage properly. For most of church history that was fine, because somebody had to sit there anyway. A phone remote is what happens when they don't.

What a remote is actually for

It is easy to file this under convenience. In practice it solves four specific problems, and if none of them are yours, you don't need one:

• The desk is in the wrong place. Plenty of media positions have no clear view of the stage, or sit so far back that the operator is reading the room a second late.
• There is only one of you. On a one-person media team the operator is also running sound, or the camera, or the door. Being tied to one chair costs more than it looks.
• The person who knows the passage isn't at the desk. A guest speaker, a Bible study leader, a youth night with no volunteer, a mid-week service where nobody signed up.
• The service moves. Baptisms, communion, a reading from the middle of the room. The screen still needs driving while everyone is somewhere else.

What a phone should be able to do

A remote that only does next and previous will strand you the first time a verse is wrong. Look for these, in roughly this order of importance:

The last one is worth arguing for. Most remotes assume somebody at the desk has already got the output running. If that person is you, standing at the lectern, the remote has to be able to start the screen too or you have not actually left the desk.

Setting one up in TajiCast

1. Turn the phone remote onPress the phone icon on the transport bar and switch it on. It stays on for the service.
2. Scan the codePoint the phone camera at the pairing code. If the camera will not read it, type the address shown above it into the phone's browser.
3. Enter the six digitsThe code is good for five minutes. Show a new one if it lapses before the phone reaches whoever is using it.

There is nothing to install on the phone: it is a web page served by the app itself, so an old Android tablet in a drawer works as well as a new iPhone. Connect as many as you like, and disconnect any one of them without dropping the rest.

The part that actually goes wrong

Almost every failed connection is the network, not the software. Three causes cover nearly all of it:

• The phone is on mobile data, or on a different wifi from the computer. They have to be on the same one.
• The wifi is a guest network. Many are configured to stop devices seeing each other, which is good security and fatal to a remote. Use the same network the presentation computer is on.
• The firewall has not been asked. On Windows, allow the app through Windows Security → Firewall the first time. Nothing about the symptom tells you this, which is why it costs people an hour.

So who should hold it?

The remote makes a question live that most churches have never actually decided: does the person preaching drive the screen, or does the booth?

The case for the pulpit is timing. The person about to read a verse is the only one who knows they are about to read it. Everyone else is reacting, which is why so many verses land two sentences late — the lag is structural, not a failure of skill.

The case against is attention. A preacher looking down at a device is not looking at the congregation, and a room notices that far more than it notices a verse arriving late. There is a second cost too: the preacher who is also the operator carries a small technical worry through the sermon — did that go out, is it the right translation, is it still up — and that is exactly what a preacher should not be holding.

What most churches should do is share it. The operator drives by default, and the pulpit can override when the sermon goes somewhere the desk cannot follow. It sounds like a fudge and it is the right answer: the booth handles the ordinary flow, and the preacher reaches for the phone only for the unplanned passage or the longer pause.

For that to work, the pulpit's controls have to be usable without being looked at:

• Few controls. Next, back, blank. More than that is a menu, and a menu is a thing to read.
• Large targets, for a thumb at arm's length in stage lighting.
• The same layout every week, because muscle memory is doing the work, not the interface.
• A way to see what is on screen without turning round — the one thing a clicker cannot give you.

If your preacher would rather hold nothing at all, there is a third answer: automatic verse detection puts the passage up as it is spoken, so nobody has to decide when. Plenty of churches run that as the default and keep the phone in a pocket for the moments it misses.

What it does not replace

A phone is a second pair of hands, not a booth. Anything that needs care, building a theme, checking a long passage's line breaks, previewing before it goes live, still belongs on a proper screen with a keyboard. The remote is for the ten decisions a service actually demands: next, back, that verse, blank it, bring it back.

The takeaway

• A phone remote matters most when the desk is in the wrong place or there is nobody to sit at it.
• Insist on search and a clear key, not just next and previous, or you will still be walking to the back.
• Set it up and test it on a weekday: the failures are almost always wifi, and they are quiet ones.