Release Videos That Update With Every Version
After a feature merge, rerun the affected demo scenes in a preview environment so the launch video stays in sync with the latest UI.
When a product team merges a feature update, it often finds that the demo video on its launch page still shows old buttons, copy, and flows. Rather than rerecording everything just before launch, the team stores voiceover scripts and scene steps in the code repository. Each scene specifies the page to open, what to enter, the outcome to highlight, and its captions and pacing. Once the preview environment has deployed, the pipeline knows which scenes need to run again.
The scene runner operates in the preview environment through page elements and user actions rather than fixed screen coordinates. It records the updated interface, applies the existing zooms, cursor paths, captions, and transitions, and produces a short video for review. If a button has been renamed, a flow breaks, or a target element disappears, the job stops on the specific scene as an automated test would, with the old frame, new frame, and failed step attached.
On the review page, designers deal only with the seconds that changed. They can revise a step, change the highlighted area, or approve the automatically generated replacement scene. Approved clips are merged back into the master video, with a final cut retained for each version. The first release focuses on web-product feature demos and supports preview environments and recording accounts. Videos involving on-camera talent, complex 3D animation, or ads that require live performance remain with traditional production workflows.
Why now
When observed on August 31, Topview Motion Studio ranked third in Product Hunt’s new-product feed. S1 Launch-video creation without a timeline is gaining attention, yet footage becomes outdated as soon as UI changes merge, and there is still no maintenance workflow that reruns it with each version.
Target user
SaaS product teams that ship features weekly or every two weeks. Once a feature has merged and the preview environment is ready, product marketers and designers are most likely to notice that an existing video no longer matches the UI. Launch dates are usually already set, so rerecording from scratch compresses time for copy, approvals, and channel preparation. Teams with existing automated tests and stable test accounts can adopt it most easily.
Minimal entry point
Run web scenes with Playwright, prioritizing roles, labels, and test IDs as locators. It natively records video and can save screenshots, page snapshots, and execution traces. S3 Store scene scripts as repository JSON or YAML, covering entry points, actions, assertions, captions, and hold times. The first version does not attempt to infer impact from arbitrary code changes; instead, merge requests explicitly tag the relevant scenes. On failure, output before-and-after screenshots, the target locator, and the trace file. Use FFmpeg for clip trimming, zooming, captions, and compositing; webreel has validated a similar browser-recording stack. S4
Punching above its weight
Open-source the scene-script format, example repositories, and GitHub Actions workflows to attract SaaS teams already using Playwright tests. Publish before-and-after clips from real UI updates in developer and product-marketing communities. Then offer a free checker that scans repositories for broken scene locators. The earliest conversions should come from teams that frequently publish release notes and feature videos.
Competitors & gaps
- Topview Motion StudioGoogle
- Topview Motion Studio takes a product brief and reference materials, then generates a launch video in a selected style. It supports multiple aspect ratios and durations from four to 60 seconds. S2 This works well for quickly turning a creative direction into a complete video. Its own guidance also says interface and brand details still need human review. S2 Its unit of work is a one-off generation, not executable scenes stored in a repository. After a product merge, teams still need to decide which footage is outdated. It also does not turn a missing element or broken flow into a scene-level failure. The opportunity is to preserve the existing edit style while rerecording only the real UI footage affected by a change.
- webreelGoogle
- webreel already uses JSON to define clicks, text input, and key presses. It can add a cursor, keystroke cues, and sound effects in a headless browser, then export MP4, GIF, or WebM files. S4 Its configuration can live in a code repository and run in continuous integration. S4 It is therefore very close to the technical direction of repeatable recording. The gap is in the maintenance workflow for launch videos, rather than browser execution itself. It does not describe how to identify scenes affected by product changes. Designers also lack a review view that places the old frame, new frame, and failed step side by side. Nor does it offer approving clips, replacing them in the master video, and archiving version-specific final cuts.
How it makes money
Subscription pricing based on the number of video projects updated each month. The base plan covers one product and a limited number of rendering minutes. A team plan adds parallel jobs, approval permissions, and version archives. Additional cloud recording and rendering time is usage-based.
The case against
Page locators can break when components are refactored, making maintenance costs approach those of end-to-end tests. Unstable logins, verification codes, and test data can cause recording jobs to halt unnecessarily. Differences in asynchronous loading and animation can also make footage jitter, creating needless rerecording. Real accounts may expose customer data, so isolation and redaction must be built into the recording pipeline. If a change affects scene pacing, simply replacing a clip can disrupt voiceover and music synchronization. And if automated impact detection is inaccurate, designers still need to review every scene, quickly eroding trust.