On-set phone playback: workflow and FAQ

Written for props masters, playback operators and ADs who have to make a phone screen behave on camera. The workflow below is how phone playback is normally run with PhoneGuy, but most of it applies whatever tool you use.

The workflow, prep day to wrap

1. Build the character's phone

Pick the model that matches the hero phone in the actor's hand, set the wallpaper, the contacts, the carrier name, the clock and the battery level. If the production is nervous about real brands on camera, build your own interface skin with your own app icons and a fictional messaging app instead of a branded one.

2. Break the scene into beats

A beat is one state of the phone in the script: the thread as it stands before the argument, the incoming call, the missed call afterwards. Beats are what make a long scene shootable out of order — you jump to the beat you are on instead of scrolling through a conversation.

3. Lock the hero phone before it goes to set

Airplane mode, so no real call or notification lands mid-take. Then Guided Access (Settings, Accessibility, Guided Access) so a triple-click is needed to leave the app and the actor cannot swipe out of the simulated interface by accident. Set brightness manually and turn auto-lock off.

4. Run the take from off camera

The operator holds a second device — a phone or tablet — and triggers the next message, call, FaceTime or push notification on the actor's cue. That is the difference between a screen that reads as real and a screenshot that reads as a prop.

5. Reset between takes

Reset the beat to its start state. Every take begins with the same screen, the same time and the same unread counts, so editorial is not fighting continuity later.

Questions we get asked on set

Does the actor need to do anything?

Usually not. They hold the phone and play the scene; someone off camera makes it react. If the beat is the actor typing or tapping, the interface responds properly to touch, so that works too.

Does it work with no signal?

Yes. Projects are stored on the device, so basements, tunnels, stages and remote locations are fine. Changes sync when the phone is back on a network.

Do I need to jailbreak the phone?

No. It is an app on a normal iPhone or Android. Nothing about the operating system is modified.

Are messages and calls actually sent?

No. Nothing leaves the device, no number is dialled, no data goes to a carrier. That also means no message history to clean up when the phone goes back to its owner.

Can the status bar match the story?

Yes, and it matters more than people expect. Clock, battery, signal bars, carrier name and 5G indicator are all set by you, so the screen still says 02:14 with 4 % battery at three in the afternoon on a fully charged phone.

Can two phones in the same scene be controlled?

Yes — each phone in the project is its own device and can be driven separately, so a conversation between two characters stays consistent on both screens.

What if the director changes a line at the monitor?

Messages can be edited or typed live from the control room, so a rewrite between takes does not mean rebuilding the scene.

Which phones can it look like?

iPhone models from the 8 up, and Android look-alike skins including Pixel, Samsung and Nothing Phone layouts, so the screen suits the character rather than the crew's newest handset.

How much prep time does a scene need?

A simple message exchange is minutes. A scene with a call history, unread threads, notifications and a custom interface is more like an hour on prep day — and it is an hour you get back on the shoot day.

Working a scene that does not fit any of this? Write to hello@phoneguy.ai.