Accuracy
The video is only as good as the screens it records. Two habits get you from “that looks like some app” to “that is our app.”
1. Give screenshots
Attach screenshots of the real screens. They become the bar: exact colors, spacing, corner radii, shadows, type, and — the thing code alone gets wrong — whether something is a floating card or an edge-to-edge sheet.
/reely Make a reel of onboarding — match these screenshots exactly.
Screenshots win over source when they disagree. Without them, the agent works from your code alone, which is usually right about structure and occasionally wrong about style.
2. Look at the screens before recording
Reely renders every screen as a still image before it records anything. Ask to see them. It costs one extra pass and it is the only moment where a wrong shade, a missing row, or a dropped progress bar is cheap to fix.
/reely Show me the rebuilt screens before you record.
Correcting what drifted
Point at the specific thing. Vague notes produce vague fixes.
| Instead of | Say |
|---|---|
| “It looks off” | “The card background should be #F7F7F9, not white.” |
| “Wrong font” | “Headings are Inter Semibold, not the system font.” |
| “Something is missing” | “The progress bar at the top is missing on every screen.” |
| “Spacing is weird” | “The list rows are too tall — 56pt, not 72.” |
Things worth calling out early
- Persistent chrome — a tab bar, nav header, progress bar or mini-player that must appear on every screen.
- Custom icons — anything that is not a system symbol, so it is not silently approximated.
- Real copy — if the mock invents wording, say the strings must come from the app verbatim.
- Realistic data — the names, prices, and avatars you actually want on camera.