Using your phone as a teleprompter remote.

The problem is not laziness. It is that a teleprompter on a desk was designed for someone sitting at that desk. The moment you move back to a sensible distance from the camera, the controls stay behind, and every small adjustment turns into a trip.

The walk back is a retake

A trip to the keyboard costs more than the ten seconds it takes. Three things break each time.

Your position. You were sitting in the right spot, at the right angle, with your face where the light was set for it. You stand up, you sit back down, and you are a few centimetres off. Sometimes it shows, sometimes it does not, and you only find out in the edit, when two takes refuse to cut together.

Your state. Recording to camera has a warm-up. After a few takes you settle into the material and your voice relaxes. Getting up to press a key is a small reset of that, every time. You come back to the chair as someone who was just fiddling with a computer, and the first sentence of the next take sounds like it.

Your willingness to fix things. This is the expensive one. When a correction costs a walk, you stop making corrections. You notice the text is a line too far down and you read around it. You fluff the opening of a section and, instead of going back to its start, you carry on and hope it works out. It is one of the quieter reasons a short video takes all evening: the small fixes you skip turn into whole takes you throw away later.

On a set, none of this exists, because someone else is at the controls. Alone, you need the controls to come to the chair with you.

What a remote has to do

Look at what you actually reach for between takes and during them. It is a short list.

• Start and stop. Begin the scroll when you are ready, not when you happened to press a key across the room. Stop it the moment a take goes wrong, so the text is still near where you lost it.
• Nudge by a line. The text is slightly ahead of you, or slightly behind. You want to move it one line, not jump a page. And you want to hold the button to keep moving, rather than tap twenty times.
• Jump a section. When you record in blocks, the unit of work is the section. Fluff one and you go back to its start; finish one and you move to the next. That is the most frequent jump in a solo session, and it should be a single press.
• Back to the top. For the full run-through at the end, or when you decide the opening needs another go.

If the scroll runs on a timer, add a fifth: a little faster, a little slower. Pace is something you discover while speaking, not something you set once.

One more thing a remote needs, and it is not a button: you have to be able to see where you are. A remote you press blind is a remote you double-check by looking at the prompter, which is exactly the glance you were trying to avoid. A line of text, or at least the section name, on the remote itself is enough.

All of this assumes your script is split into sections in the first place. If it is one long block, "jump a section" has nowhere to land. Breaking the script at the natural cut points is the same habit that makes a weekly recording routine sustainable, and it is what turns a remote from a convenience into a time saver.

What a remote should not do

The temptation is to put everything on it. Resist that. Every control on the remote is a control you can press by mistake while holding it off camera, and a remote you have to look at carefully before pressing is no better than the keyboard.

• No editing. Rewriting a line on a phone keyboard between takes is slow and error prone. If the script needs changes, stop and change it at the desk.
• No display settings. Font size, margins and the position of the reading line are set once for the room. Changing them from the chair invites drift between takes.
• No script switching in the middle of a session. One script per sitting. Loading another one is a desk job.
• Big targets, few of them. You will often press it without looking, with the phone resting on your knee. Play should be impossible to miss, and anything that throws away your position (back to the top) should be away from it.

A good remote feels almost too simple. That is the point: it is the operator's hand, not the operator's desk.

Why the phone is the right remote

You can buy a small clicker, and for some setups it works. But a clicker has a few buttons and no screen, so it cannot show you where you are, and it usually speaks to the computer as a keyboard, which means it does whatever the focused window decides those keys mean.

The phone is already in your pocket. It has a screen big enough for large buttons and a line of text. It can show whether the connection is alive, which matters more than it sounds: a remote that silently stopped working is worse than no remote, because you only find out when you press it in the middle of a take.

The catch is that a phone remote talks to the computer over the network, so two things have to be true. The phone and the computer must be on the same Wi-Fi, and pairing must be easy enough that you do it once rather than fight it every session. If pairing is a chore, you will stop using it and go back to walking.

How it works in Mirrento

Mirrento, a teleprompter for the Mac, serves its own remote page to an iPhone or iPad over the local network. In Settings, under Remote, you choose Pair with QR code and scan it with the phone's camera. The page opens in the phone's browser and pairs itself. If you would rather type, the same panel shows a 6-digit PIN. Once paired, the phone keeps a token, so you do not enter anything again next session. If a phone should stop having access, Revoke all devices on that same panel cuts off every paired phone. Rotate PIN only stops the old PIN from pairing anything new.

The remote itself is the short list above and little else:

• a large play and pause button in the middle;
• Back and Forward, one line per press, repeating while you hold;
• previous and next chapter, where a chapter is a section of your script;
• slower and faster, for when the scroll runs on its own;
• Restart, which goes back to the top of the script, placed at the bottom of the screen, away from play.

Above the buttons it shows the script name, which chapter you are in out of how many, and the line currently at the prompter's reading line. A chip in the corner says whether the phone is live, connecting or offline, and a REC badge appears while a recording is running. If you would rather not look at buttons at all, Swipe mode turns the status card into a gesture surface: tap to play or pause, swipe left or right for chapters, up or down for lines.

When the scroll follows your voice instead of a timer, the remote adapts. Play and the speed buttons stop doing anything (play shows a microphone and a short notice), because your voice is driving, and Back and Forward move the text by a block and re-anchor the tracking there. That is the case where the remote matters least, since the text already waits for you, but it is still how you jump back a chapter to redo a section without standing up. I wrote about why that kind of scroll changes solo recording in how to film yourself without a crew.

The remote is included from the trial onwards. If walking to the keyboard is what eats your sessions, the 7-day trial is enough to record one script both ways and count the trips you no longer make.