Vistralo/Use cases/Engineering handoff
Hand over a feature with a walkthrough
The feature works and you understand it. The person taking it over does not, and the pull request description says what changed in the code, which is a different thing from what the feature does on screen. Record it once and they can watch every screen explained.
The demo runs in your browser on sample projects. It needs no account.
One recording, handed over
Press Record and use the feature
Record is on every page of the app and goes straight to the browser's screen picker. Share the tab and click through the flow as a user would.
Stop, and the project opens
The recording becomes a project named for what it is and when it was made. The share link is the first thing offered.
The narration follows
While you get on with something else, each screen gets its line and the film is built. The same link plays the narrated version once it is ready.
Paste the link where the work lives
In the pull request, the ticket or the handoff note. It opens in a browser with no account.
A kit for whoever builds next
Download files packs a project into one ZIP: the narrated video, its captions as timed text, a still for each screen and a short written prompt that ties them together. It was made so that a coding agent, or a person, can pick the work up without the recording's author in the room.
If you gave the address of the site you recorded, the narration can also name the libraries the page loads, taken from its code.
Before you record something internal
- Who can open the link?
- Anyone who has it, until it expires or you remove it. The link shows the finished video or brief and nothing else in the project.
- What leaves the browser?
- The recording is stored in your workspace. For narration, frames from it are sent to OpenAI and the script is sent to HeyGen, on Vistralo's accounts or on your own keys, depending on your plan. Do not record anything you could not send to those two services.