Type into the composer, open an app menu from a trigger word, and let the selection collapse into an inline chip

What the source does

A white app window with a centred heading and an empty composer at the bottom, presenter picture-in-picture at right. The first word types on (~f4–f12). At ~f15 a menu of app rows pops up above the composer (icon, name, small grey caption) and stays while the typed trigger filters it (~f15–f26). At ~f27 the menu vanishes and an inline chip with an icon and app name replaces the trigger inside the composer. Typing then continues after the chip to the end of the sentence (~f33–f84).

Composer mention flow: caret type-on, trigger opens a filtered app menu, selection converts the trigger into an inline chip, and typing resumes after the chip.

Phase notes

1. Frame 0 — Empty composer
2. Frame 4 — First word types
3. Frame 15 — App menu pops up above composer
4. Frame 27 — Menu closes; chip inserted
5. Frame 33 — Typing resumes after chip
6. Frame 84 — Sentence complete

Use this example

1. Watch the source and draft at normal speed. Compare the order of actions, the held states, and the transition into the result.
2. Download the project and read its README before changing inputs. The package includes its implementation and declared dependencies.
3. Replace the sample content through the package's documented input or content builder. Keep source footage in the research comparison.
4. Render your adaptation and inspect text fit, framing, intermediate states, and entry and exit frames.

Recorded limits

• Visual fidelity is an authored draft judgement from sampled source frames; no independent blind review or native Resolve execution.
• Both variants rerendered after correcting unrevealed whitespace and the caret’s active line.

Inspect the original verification record ↗