When this is useful
Portrait dimensions alone do not make a mobile demo. A cropped desktop sidebar may hide the content, while a responsive product may replace that sidebar with a drawer. Native apps can have additional gestures and operating-system interactions that a browser cannot demonstrate.
How to make the decision
- Identify the target experience: responsive website, installed mobile app or desktop product advertised in a vertical placement. State that choice in the brief.
- For responsive web footage, record at a phone-sized viewport and follow its actual navigation. For a native app, obtain device or simulator footage through an appropriate recorder.
- Inspect the complete task in the final portrait frame. Keep the menu opening, selected action and resulting state understandable without relying on desktop-only context.
A practical decision example
An illustrative scheduling product could open its navigation drawer in a mobile browser before showing a calendar entry. Cropping a desktop calendar into a narrow strip would not demonstrate that interaction and could cut off the date being edited.
Limits and checks
A responsive browser capture does not prove native-app support, touch performance or behaviour on every device. Demovela’s mobile capture refers to a phone-sized browser, not an installed iOS or Android application.
Your next step
Request separate source footage when the layout changes. Use cropping only when it preserves the experience being shown.
References and scope
Vendor descriptions use official sources checked on 12 September 2026. These are editorial selection criteria, not comparative hands-on benchmarks. General workflows are not promises of product compatibility. Read our editorial approach and current Demovela scope.