Software explainer videos that stay current with every release
Why screen-recorded product videos go stale, and how filming the real app from its source keeps tours, training and onboarding videos up to date.
A product tour recorded by hand is out of date the first time the interface changes. Re-recording it means booking the time, writing the script again and editing again.
Why videos go stale
- The interface moves. A renamed button or a new step makes the narration wrong.
- Nobody owns the re-shoot. It is always less urgent than the next feature.
- The video shows the happy path. A new user meets the error the video skipped.
Filming the real app
Vidabug films your software by using it. It plans the chapters from your app's own features, signs in with a demo account, and works through each feature as a new user would. The narration is written from what happens on screen, and the video comes with captions, a transcript and a written step guide.
Because the video is made from the app, it can be made again. When your project follows its default branch, Vidabug shows what changed since the last video, and you can run a new one.
Walkthrough or training?
- Walkthrough: a tour for prospects and new users, about 45 seconds a chapter.
- Training: step by step and slower, about 90 seconds a chapter, for people who must use the feature tomorrow.
Defects found while filming
A video exposes broken flows quickly. When Vidabug meets one, the job records it instead of hiding it. Where your plan includes repairs, the flow is fixed, tested again and filmed working, and the repair goes to a branch you review.
What you receive
- an MP4 with a voice-over and burned-in or separate captions;
- a transcript and a step-by-step guide;
- a report of anything that did not work;
- a share link and an embed for your help centre.