July 4, 2026
Product demos rot. A screen recording is out of date the week the UI changes, and a click-through built in a separate demo tool is a second copy of the product that nobody maintains. The demo that matters most, the one a salesperson runs live, depends on someone remembering where to click.
So I built ScreenReel: an open-source demo recorder whose output is a plain file that sits next to the code it explains.
You record a flow in ScreenReel Studio by using your app normally. Studio turns typing, selects, toggles, sliders, clicks, scrolling and navigation into editable actions. Each scene gets a title, talking points and a pace, and the result exports as a screenreel.json file you commit with the app.
{
"id": "overview",
"route": "/dashboard?team=sales",
"title": "Start with the outcome",
"talkingPoints": "Explain what changed and why it matters.",
"actions": [
{ "type": "glow", "selector": ".kpi-card", "sequence": true, "count": 4 },
{ "type": "click", "selector": "[data-action=\"open-review\"]" }
]
}
Because it is plain JSON, a demo can be reviewed, diffed and versioned like any other change.
Setup is one script tag and one element:
<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/projector/screenreel.js" defer></script>
<screenreel-projector project-id="my-app" flow-src="/demos/my-demo.json"></screenreel-projector>
The point of keeping the demo in the repository is that it can break loudly instead of quietly. Validation catches a selector that no longer matches, and flow doctor repairs safe selector changes before a customer sees the break. It can run in CI like any other test.
ScreenReel is Apache 2.0 and framework independent. It needs no backend, no account and no analytics service, and no data leaves the page unless you configure it.
The live demo runs ScreenReel on its own landing page, and the source is on GitHub.
Updated for v0.4.0: the setup snippet, playback modes and flow doctor arrived after the first release.