Your first video
The quickstart gets you through the mechanics. This page walks the same path again and explains why you'd choose one option over another — useful the first time you make something you intend to publish.
Before you record
Decide what the video is for, because it changes the recording. A support answer wants one flow and no preamble. An onboarding walkthrough wants the whole path, including the parts that seem obvious. A release note wants the before and the after.
Two things much easier to get right in the recording than to fix afterwards:
- Go slowly between actions. Decodx cuts on your clicks; a pause gives each scene a clean edge.
- Keep real customer data off screen. Blurring works, but not recording it is safer.
Recording
Record the flow start to finish in one take. Don't narrate while recording — narration is written and voiced separately, which is what lets you change it later without re-recording.
Reviewing the scenes
Decodx proposes a scene per meaningful step and drafts a narration line for each. Read the whole script top to bottom before doing anything else.
Common first-pass fixes:
- Merge two scenes that are really one action.
- Cut a scene that only exists because you fumbled a click.
- Rewrite a narration line that describes the UI instead of the intent.
Voice and pacing
Pick a voice, then listen to one generated scene before generating them all. Words the voice mispronounces — product names, acronyms — belong in the pronunciation list rather than being spelled phonetically in the script.
Rendering
Check the estimate. Approve. The job runs in the background; you don't need to watch it.
Publishing
You now have a video, a written guide and a share link. Decide who the link is for before you set its permissions — most first videos get shared more widely than intended.
Then change something
Go back, edit one narration line, and re-render. It will take seconds, because only that scene is re-made. That behaviour is the reason to use Decodx at all — see How it works.