Capture menus without hiding the page

The working approach

Record the route change when needed.
Close the menu before the destination shot.
Confirm the page title and main content are visible.

A concrete example

For a mobile analytics demo, verify that the navigation drawer has disappeared before holding the metrics screen.

Before recording this scenario, write down what the starting screen contains and what should be different at the end. This gives the reviewer an observable result to check, rather than asking them to approve a general impression.

The mistake to avoid

Capturing immediately after a menu click can preserve the overlay.

If the source cannot support the intended message, narrow the claim or capture the missing evidence. A transition, caption or voiceover can explain a real change; it should not manufacture one.

Put it into a production brief

Replace the bracketed fields before using this brief. The scenario is illustrative; keep only the actions your product actually supports.

EDITABLE PRODUCTION BRIEF

Purpose: Capture menus without hiding the page.
Audience: [specify the viewer and their familiarity with the product].
Decision: [what should the viewer understand or do next?].
Approach: Navigation is useful context but an open drawer can obscure the proof. Decide whether a shot demonstrates navigation or the destination.

Required evidence:
1. Record the route change when needed. Show the relevant entry state, action and completed result.
2. Close the menu before the destination shot. Show the relevant entry state, action and completed result.
3. Confirm the page title and main content are visible. Show the relevant entry state, action and completed result.

Reference scenario: For a mobile analytics demo, verify that the navigation drawer has disappeared before holding the metrics screen.
Avoid: Capturing immediately after a menu click can preserve the overlay.

Deliverable: [duration], [format], [placement].
Use only recorded product behaviour. Preserve the full original.
Acceptance: check each claim against its visible scene, review at actual viewing size, and test the final file.

Review before delivery

Evidence: can a new viewer identify the result described in the example without being told where to look?
Reading distance: are the relevant controls and labels understandable at the intended placement size?
Continuity: does each cut preserve the relationship between the action and its result?
Accuracy: does the final caption describe the visible product state, including any limits?

Using this with Demovela

The automatic URL workflow currently supports Postraid and Adfolio. Other product scenarios on this page are production-planning examples, not compatibility claims. Adapt the brief to your own recorder or editor. Demovela preserves originals and creates separate outputs; review the resulting file before publishing.

Check the current preview scope →

Keep the workflow moving

Choose the next resource based on the decision you still need to make.

Browse the complete resource library →