Bonus 10. You are on a set, in a car, at a festival. Your studio is at home. This is what you can actually do from a phone, what you cannot, and why the difference is not arbitrary.
Your machine, reached remotely. Everything is there: your footage, your projects, your originals. It requires the machine to be awake.
A session in the cloud. Runs without your machine at all. It cannot see anything that only exists on your laptop.
Almost every disappointment with mobile work is these two being confused.
Your media is the size of your media.
Nothing about working from a phone changes the fact that four terabytes of footage is on a drive in your office.
| Works | Does not |
|---|---|
| reading anything written down | anything touching local media |
| status, what changed, what is unfinished | rendering, transcoding, proxies |
| drafting, notes, structure, lists | opening your editing application |
| approving, deciding, replying | anything needing your originals |
| kicking off a queue if it is connected | reviewing footage properly |
Notice the pattern. Words travel. Pictures do not.
Everything the main course made you write down is now the thing you can reach.
shots.json, the bible, the logs, LIBRARY.md, the delivery specs. Your project as text is portable. Your project as media is not.
"What changed yesterday, what is waiting on me, and what is the first thing I should do when I sit down?"
Read it on the way in. You arrive at your desk already decided, which is worth more than an hour of the desk itself.
Most of what stops a queue is a decision, and a decision is a sentence.
"Shot 14 take 2. Approve it and re-run the audit."
The work continues at home while you are not there, which is the entire promise of the unattended pattern extended one step further.
The highest value phone use in the whole system.
"Save a memory: the vertical crop on that platform loses anything in the bottom fifth. Found it on the client's phone, not mine."
You will not remember this tonight. Capture at the moment, from Bonus 4, and the moment is usually not at your desk.
Do not approve anything visual on a phone screen and call it approved.
A frame on a phone at arm's length in daylight is not a frame. You cannot judge a grade, a consistency drift, or a soft focus, and approving it there means finding out later.
Approve the decisions. Look at the pictures on a real screen.
A cloud session sees what has been stored somewhere it can reach. In practice: what you committed.
Anything sitting only in your local folder, uncommitted, is invisible to a cloud run. It is not lost, it is just not there, and the cloud session will proceed as though it does not exist.
The habit worth building: commit at the end of a working session, always.
Not because you need the history that day, but because it is the moment your work becomes reachable from anywhere and safe from the machine.
"Save a version with a short description of what changed."
Ten seconds, and it is the difference between a studio and one hard drive.
Anything in your project travels with it. Anything in your machine's own settings does not.
That is usually what you want: your guards and rules should travel, your credentials should not.
Check it once: "if this project were opened on another machine, what would be missing, and is any of it a credential?"
A cloud session has no memory of your local setup, no access to your connected tools unless they are reachable from there, and no ability to see the thing you are looking at.
It is a capable colleague who has read your files and is in another building. Brief it like one:
"Read the project. I am on set. Draft the delivery spec for the broadcaster from the notes in delivery/, and list anything you had to guess."Fifteen minutes, and do it before you next travel, not after.
Your project stopped being a hard drive and started being something you can think about anywhere.
Building Your Own Studio From Scratch. Everything in this session, assembled from an empty folder, in one sitting.
Verified against Claude Code 2.1.220 · 2026-07-30.