Skip to main content

· 4 min read · The Kinomock team

Why a slow camera move beats a fast one

A device mockup clip has one job: let someone read your screen while giving them a reason to keep watching. Most clips that fail do so because the camera is doing too much.

Keep the text readable

If a viewer cannot read the largest heading on the screen at any moment, the camera is too far away, too oblique or moving too quickly. A practical test: pause the clip at a random frame. If the screen content is a blur, slow the move down or shorten the distance it travels.

Angles matter more than speed. Past roughly 40 degrees off-axis, interface text compresses until it stops being legible. Use steep angles for the first second of a reveal, not for the part where people are meant to read.

Move in one direction

An orbit that goes left and then comes back reads as indecision. Pick a direction per shot and commit to it. If you need a second idea, cut to a new shot. In Kinomock, each shot has its own keyframes and shots cut from one to the next, so this structure is the default.

Ease the ends

A move that starts and stops at full speed looks mechanical. Ease-in-out on the first keyframe is usually all a single move needs. Save linear motion for loops, where the last frame has to match the first.

A starting recipe

  • One shot, five to six seconds.
  • Start around 30 degrees off-axis and end near 10.
  • Ease in-out.
  • Depth of field on auto, so the device stays sharp.

The Launch Orbit and Hero Push-in templates follow this recipe. Open either in the editor and swap in your own screen.

All posts