The safest way to keep API keys and customer data out of demo videos is to never let real values reach the screen: run the demo against a separate environment with seeded fake data, load secrets from
A nightly render job is a scheduled CI workflow that rebuilds your product demo videos from the latest code while nobody is waiting on it, then stores the files somewhere your team can grab them in th
If your demo narration lives in a file in the repo, you can build WebVTT captions from it in CI, like any other artifact. The script already has the exact words. You only add timing, a few validation
Three tools make product demo videos from developer artifacts instead of manual recording. They start from different things: a local code folder, GitHub pull requests and Playwright tests. A small gro
Translating a demo video is more than swapping the voiceover. Here's what has to change, what should stay the same, and how to plan for it before you make the first version. Once a product demo works
What happens between reading a codebase and rendering an MP4, where the accuracy comes from, and what you still need to check yourself. Most product demo videos start with someone recording their scre
Most demo retakes come from the state of the app, not from the person recording. Seed it, reset it and pin it down, the same way you would for a test. When a feature demo takes far more takes than it
Routes, labels, fixtures, tests and git history can tell you what to show, in what order, and in which words. Here's how to mine them before you plan a product demo.
