Why this lesson: your whole first platform runs on one skill — capturing your screen and, optionally, talking over it. No face, no fancy gear. Just your editor, your phone, and a quiet room. Get this loop tight and you can ship a Reel from any bug you fix.
First, recall
From Lesson 4: why did we pick Instagram Reels as your first platform? Because the barrier that stops most devs — being on camera — doesn't apply. A screen recording with text on top is a real Reel. This lesson is that recording, step by step.
Step 1 — capture a vertical screen recording
Reels are 9:16 (vertical), so record vertical from the start. You have three easy paths, all fine:
Phone screen record — build or run the thing on your phone, swipe the built-in recorder. Zero setup.
QuickTime (Mac) — File → New Screen Recording, drag a tall region. Free, already installed.
OBS — free, cross-platform, set a 1080×1920 canvas when you want more control.
Whichever you use, the goal is the same: a clean, tall clip of your real screen doing a real thing[Instagram best practices].
Step 2 — frame code so a phone can read it
Your editor at normal zoom is unreadable on a 9:16 phone screen. Fix it before you hit record:
Bump the font — editor font to 22–28px. If it looks too big on your monitor, it's about right for a phone.
Zoom in on the part that matters — show the 5 lines you're changing, not the whole file tree.
Leave room at the top — that's where your big on-screen hook text goes (Lesson 13).
Rule of thumb: if you can't read the code holding your phone at arm's length, neither can a scroller.
Step 3 — record the voiceover separately
Don't narrate live while wrestling with the code — you'll fumble both. Record the screen first, then talk over it after. Voiceover keeps your face out of it entirely:
Quiet room — kill the fan, close the window. Silence matters more than any mic.
Phone mic, held close — 15–20cm from your mouth beats any distant "good" mic.
Re-record, don't stress — flub a line? Pause, say it again, keep the good take in editing. Nobody hears the outtakes.
Worked example · a 15-second bug-fix capture
What you shipped today: a React state update that wasn't re-rendering — you forgot it was mutating state in place.
Record (screen): QuickTime, tall region, font at 24px. 15s — show the broken state.items.push(x), the wrong result, then the fix with a fresh array, and the UI updating. Zoom on those lines only.
Record (voice): quiet room, phone held close — "This looked right but never re-rendered. Here's why, and the one-line fix." Two takes, keep the clean one.
That's it — a raw clip and a voice track, both faceless. Next lesson turns them into a tight captioned Reel.
Quick self-check
No clues in the formatting — pick from memory, then click.
1. Before recording your screen for a Reel, the first thing to fix is…
Editor code at normal zoom is unreadable on a phone. Big font + zoom on the lines that matter is the fix — do it before you hit record, not after.
2. The recommended way to handle narration for a faceless Reel is to…
Recording voice separately lets you focus — screen first, then talk over it. Flub a line? Re-record it; the outtakes never make the cut.
3. For clean voiceover audio, what matters most?
A quiet room plus your phone mic held 15–20cm away beats a distant fancy mic. Silence and proximity do the work — gear doesn't.
Your turn · do this now
Take the last bug you fixed. Record a 15-second vertical screen capture of the broken → fixed moment (font bumped, zoomed in), then a one-line voiceover over it. Don't edit yet. Send me both and I'll tell you if the code is readable and the voice is clean enough to build on.
Primary source · study this
Instagram's own Creators — Best Practices hub covers Reels capture, format and reach straight from the platform. Note how the best tech Reels are just a clear screen + tight voice — no set, no face.
💬 Your teacher is here. Not sure QuickTime vs OBS, or whether your voiceover sounds okay? Send me a raw clip — I'll tell you exactly what to adjust before you edit.