All posts

Tools

Record a demo that shows the work instead of hiding it

Plan a short walkthrough around the problem, one real journey, a useful result and the limitations a viewer needs to understand.

HackHoster Team · · 4 min read

Modular ivory prototype pieces and a notebook on a matte charcoal workbench
Illustration: HackHoster (AI-assisted), original artwork

At a glance

  • Lead with the person and problem before explaining the stack.
  • Show one complete journey using the submitted version of the project.
  • Use captions and a written walkthrough to support the recording.
  • Identify prepared examples, edits and known limitations honestly.

Practical guidance from HackHoster. Sources and illustration credits accompany the article. Publishing standards and corrections.

A clear demo shows a problem, one working journey and a result the viewer can inspect. Keep the explanation close to what happens on screen. The goal is to help someone evaluate the project, not to make the prototype look larger or more reliable than the work you completed.

Start from the current submission rules. If a video is encouraged rather than required, a good written walkthrough and accessible links still matter. This guide suggests a recording process you can adapt to the available time. The imaginary examples are illustrations, not published HackHoster submissions or award winners.

Conceptual illustration of building a focused prototype from small components
Illustration: HackHoster (AI-assisted), original artwork

Choose one story the product can support

Write an opening sentence naming the user and task. For an imagined volunteer planner, it could be an organizer who needs to turn meeting notes into a reviewed action list. Explain why the current process is inconvenient without inventing testimonials, customer numbers or measured savings you have not observed.

Choose the journey that best demonstrates the promise. Paste the notes, review unresolved tasks, make a correction and export the result. If you have several features, resist showing each briefly without completing any. A complete task gives the viewer a clearer basis for assessment than a fast tour through unrelated screens.

Prepare the environment and sample

Use the version you will submit. Clear unrelated tabs, notifications and sensitive files from the recording environment. Check that no credentials appear in the terminal, address bar or developer tools. A convincing walkthrough should not require exposing information that has nothing to do with the project.

Prepare fictional or properly authorized sample input with an expected result. Keep the sample available in the README so a viewer can repeat the demonstration. Practice resetting the application before each take. Do not quietly replace a difficult input with a friendlier one while claiming that the result is representative of every possible use.

Show the meaningful steps at a readable pace

Keep the text and controls large enough to follow in the final recording. Narrate what changes and why it matters. Say that a missing owner is highlighted for review, rather than only saying click here. Pause long enough for the viewer to inspect the corrected record and exported output.

Editing can remove dead time and mistakes, but preserve the meaning of the workflow. If a long processing step is shortened, make that clear where the duration matters. Do not edit a failed operation into an apparent success. A prepared example is useful when labeled, and misleading when presented as the current live result.

Let the viewer see the output long enough to understand it. The most important evidence should not flash past between title cards.

Explain one implementation decision

After the working journey, identify a technical decision that shaped the result. Perhaps the review step separates suggestions from confirmed tasks, or the application validates the export before offering a download. Connect the implementation to the user's outcome rather than listing every library in the stack.

If AI tools contributed to the build or the product's output, credit them accurately. Describe what the tool does and where your own processing or interface adds value. Avoid treating a model's fluent answer as proof of correctness. If you evaluated the output, explain the test set and its limits in ordinary language.

Include a useful limitation

Choose a limitation that changes how someone should interpret the prototype. The planner may handle pasted text but not scanned documents, or it may leave ambiguous dates unresolved. Show the boundary directly if possible. This gives the reviewer a more accurate understanding of the system than a generic statement that improvements are planned.

Explain the next step only after the current result is clear. Future integrations and possible business models are not the same as completed work. Keep the recording focused on what can be tried now. Place additional ideas in the repository when they would distract from the main demonstration.

Make the explanation available in more than one form

Add accurate captions and a text walkthrough. W3C's media guidance explains the role of captions, transcripts and descriptions. Check automated captions for project names, technical terms and sentences that could reverse meaning when transcribed incorrectly. A short recording still needs readable text and understandable audio.

Test the shared video link from a fresh browser session and make sure its permissions match the submission instructions. Include the same sample input, result and limitations in the README. Finally, watch the exported recording once from start to finish. Check the beginning, the actual result and the closing links rather than assuming the editor preview guarantees a usable final file.

A short exercise to try

Try a narration-only rehearsal before recording. Explain the problem, the user action, the result and one limitation in ordinary language without reading the interface labels aloud. If the explanation becomes a long list of features, return to the main journey and remove unrelated material. Then rehearse once with the screen visible and mark where a pause would help the viewer inspect the evidence. The exercise can improve clarity without adding effects, music or production work that distracts from the prototype itself.

Sources