Click Build, hard-cut to a loading screen with a morphing glyph, hard-cut to the finished app
Study the source, inspect the editable build, then adapt the treatment to your own content.
What the source does
A warm beige start screen holds with a greeting, a filled prompt card and the pointer resting on the orange send button (local f0-16, master 478-494). On the click (~f16) the view hard-cuts to a light workspace: a chat column on the left and an empty canvas with a small black glyph that morphs and rotates above "Building your idea…" copy (f17-58, master 495-536). At ~f59 (master 537) it hard-cuts again to the generated app: chat column, a large coastal map with a dashed route and stops, and a right-hand itinerary panel, which holds to the end.
Two hard cuts carry a build: submit state, loading state with a morphing glyph, result state, with no dissolves between them.
Phase notes
- Frame 0 — Start screen, pointer on send
- Frame 16 — Click
- Frame 17 — Hard cut to loading workspace, glyph morphs
- Frame 59 — Hard cut to the finished app
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.
- Both variants rerendered from the packaged text renderer to repair a prior code/preview mismatch.