Hook openings that hand off to an app demo

The opening is a question, not a feature list

A useful hook does not explain the product. It creates a small reason to keep watching: surprise, relief, doubt, or “wait, show me that again.” The demo that follows should answer that reason in one visible action.

If the first frame is a logo or a feature menu, most people have already moved on. Put a face or a sharp line first, then cut to the product.

Four patterns worth filming or licensing

A gasp, then the result. Someone reacts to an outcome, and the next shot shows how the app produced it.

A skeptic, then the proof. The opener sounds unconvinced. The demo removes the objection with one tap.

A before, then the fix. Name the messy moment — a crowded inbox, a blank workout plan — and cut to the cleaner state.

A specific person, then the workflow. “If you ship ads every week…” only works when the next frames show that weekly job getting shorter.

What to write on the first line

Keep the on-screen line under about eight words. It should match the face, not fight it. “I did not expect that” works when the reaction is real. “Introducing our all-in-one platform” does not.

Captions matter because a lot of viewing is muted. The spoken hook and the written hook should say the same thing.