Continue a type-on inside a mobile composer that grows a line above the keyboard
Study the source, inspect the editable build, then adapt the treatment to your own content.
What the source does
A phone-scale composer sits above an on-screen keyboard on a white screen framed by pale green. At local frame 0 the first sentence and a half are already typed with a caret ('...travel and home.'); characters keep arriving at roughly 9 frames each ('I'm not' ~f45, 'I'm not sure which' ~f90, 'features' ~f135, 'features to look for' ~f180). Around f195 the text wraps to a third line and the composer plate grows upward while the keyboard stays fixed; typing continues faster ('How should I think about th' by f315).
Caret-driven type-on that is already in progress at the cut, with the composer plate stepping taller when the text wraps to a new line above a fixed keyboard.
Phase notes
- Frame 0 — Composer mid-sentence, caret blinking
- Frame 45 — Second sentence continues
- Frame 195 — Wrap to third line: plate steps 66px taller
- Frame 318 — End of window, still typing
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.