Push into a settings page's last card with a blur kick, then click its toggle on
Study the source, inspect the editable build, then adapt the treatment to your own content.
What the source does
After a hard cut, a white settings page fills a window on a blue-violet desktop: a left nav list and a long right column of section rows ending in a 'Developer mode' card with an orange 'Elevated risk' label, a title, two lines of body copy and an off toggle. The pointer drifts toward the card (~f0-20). Between ~f22 and ~f34 the picture blurs and the camera pushes in about 1.9x so the card fills the frame. The pointer sits on the toggle and clicks (~f55); the toggle knob slides right and the track turns blue (~f55-60). The pointer moves away and fades (~f76-80) and the on state holds.
Eased camera push-in with a blur kick onto one settings card, followed by a pointer click that flips a toggle's knob and track colour.
Phase notes
- Frame 0 — Full settings page, pointer drifting
- Frame 22 — Blur ramps, push-in starts
- Frame 34 — Card fills frame at 1.9x
- Frame 55 — Click; knob slides, track turns blue
- Frame 80 — Pointer gone; hold
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.