When this is useful
A desktop product squeezed into a phone-shaped frame can lose navigation, results or both. The correct repair depends on whether the video is advertising a desktop workflow vertically or demonstrating the actual mobile product experience.
Diagnose and fix the cause
- State which experience the asset represents. For a mobile-web demonstration, capture the responsive layout and its real menus. For a desktop teaser, a framed desktop window can remain clearly identified as desktop.
- Mark the action and result regions on each source scene. Verify that both survive the planned crop and that movement between them remains comprehensible.
- Preview with the destination’s interface overlays and captions. Keep important product evidence away from areas likely to be covered by controls or text.
What this looks like in practice
An illustrative desktop report places filters on the left and an export button on the right. A centre crop loses both. Two intentional detail scenes or a fresh mobile recording can explain the task; a single narrow crop cannot.
Limits and checks
Changing the output dimensions does not change how the product behaved during recording. Avoid describing a desktop crop as a genuine mobile walkthrough.
Your next step
Approve separate landscape and portrait storyboards before rendering a batch of variants.
References and scope
Examples are illustrative production guidance, not measured customer results. General workflows are not promises of product compatibility. Read our editorial approach and current Demovela scope.