Seeding the demo the same way as a test fixture is a great habit, and freezing the clock matters just as much, since relative dates like 3 days ago drift between takes. Fake names that look realistic but are clearly fictional also save you from blurring screenshots later. A one command reset script makes it painless to record again after a single wrong click.
Freezing the clock is the one people skip, and it's the one that bites on a retake. Relative dates look fine on the first take and then drift. What works is having the seed script set a fixed "now" and computing every timestamp from it, so the same fixture always gives the same screen. On fake names, I'd keep them boring but plausible, and do a quick search first so a "fictional" company isn't someone's real business. Agree on the reset script. If it takes more than one command, people stop rerunning it and start recording on a dirty state.
StackShortlist
Proof Over Promises.
Seeding the demo the same way as a test fixture is a great habit, and freezing the clock matters just as much, since relative dates like 3 days ago drift between takes. Fake names that look realistic but are clearly fictional also save you from blurring screenshots later. A one command reset script makes it painless to record again after a single wrong click.