hubeiqiao/how-i-make-videos-with-ai/joe-speaking-feature-in-app-video

In-app feature video

This is a portable teaching adaptation, not Joe's installed project. It was built from the in-app videos for his app, Joe Speaking: 17 feature demos (June to August 2026), then the Advanced examiner launch film (September 2026), which Joe set as his quality bar for every video. Each rule comes from a real correction or failure in those videos.

Read first

Read workflow.md and the input brief. Ask only for decisions that change the video.

Inputs

screen recording of a real session / its audio, if recorded separately / [your app icon and wordmark] / [your ending card] / an instrumental track / your one-line angle.

This folder is instructions, not a renderer: build or adapt a Remotion project.

Work in visible stages

1. Map the timeline before any design: each section's purpose, and whether it gets captions and speaker labels.
2. Draft the hook. For a launch film, start from the creator's one-line angle: Joe rejected five hooks before his own line worked.
3. Show proof stills before the full render: frame 0, the hook's exit, each speaker, loading, the first result, the ending.
4. Render, balance and check the final file: levels per section, cuts on the beat, every highlight cropped at full size, a text scan for internal names.
5. After approval, write the copy. Any Chinese version follows on the same timeline.

Rules, and why

• Frame 0 is the thumbnail. The hook is fully painted there, and gone before the app's conversation starts.
• In a demo, open on the app launch when you have it. It proves this is a real app you can tap, not a poster.
• Real assets only. Cut visual elements from the recording and use the clean icon: a redrawn copy of the app's orb read as fake, and a logo file with baked-in white corners was caught on screen.
• Measure every highlight on the recording's pixels and crop-check it at full size. Joe spotted a ring 21 px off centre.
• Keep phone footage upright and centred. Zoom and move vertically; a sideways pan was rejected.
• Speed up only waiting screens, with a small notice, and play the results at normal speed.
• Hold a payoff shot at least 1.3 s. At 0.67 s it flashed past.
• Music: a new instrumental track for each video (Joe rejects repeats), at full energy from frame 0, none under a live conversation in a demo, and no synthesized sound effects (he found them cheap).
• Claim only what the on-screen proof shows. Name the product tier, never the model behind it.

Example invocation

Read the screen recording, the audio and notes/brief.md. Map the timeline and propose the hook from my one-line angle. Show me frame 0 and the proof stills before any full render.

Done means

The creator has watched and approved the final file, the balanced video is the only deliverable, and every claim in the copy matches the proof on screen. Publishing is a separate action.