Tap a call-to-action, push the detail screen in from the right, then drive the camera into the phone
Study the source, inspect the editable build, then adapt the treatment to your own content.
What the source does
The dashboard holds on the centred phone; the pointer rests on the lime call-to-action and clicks at local ~20. Over ~21-32 a detail screen (dark hero with a large percentage, a 'Conditional go' style headline, and a checklist) slides in from the right while the dashboard slides left. From ~25 the whole frame pushes in on the phone, and by the last frame the device is about 1.8x larger with its top edge near the top of the canvas.
Tap-to-detail with camera follow: an in-device horizontal push transition is immediately joined by a camera push-in so the new screen fills the frame.
Phase notes
- Frame 0 — Dashboard holds, pointer on the button
- Frame 20 — Click
- Frame 21 — Detail screen pushes in from the right
- Frame 25 — Camera push-in begins
- Frame 54 — Phone at ~1.8x, top-aligned
Use this example
- Watch the source and draft at normal speed. Compare the order of actions, the held states, and the transition into the result.
- Download the project and read its README before changing inputs. The package includes its implementation and declared dependencies.
- Replace the sample content through the package's documented input or content builder. Keep source footage in the research comparison.
- Render your adaptation and inspect text fit, framing, intermediate states, and entry and exit frames.
The source and remake are different assets. The original code-based illustration remains editable; source footage is a research reference. Read the retained findings below before using the choreography.
Recorded limits
- Visual fidelity is an authored draft judgement from sampled source frames; no independent blind review or native Resolve execution.
- Fractional line spacing corrected to pixel values in this revision; both variants rerendered.