How to Write App Ad Hooks: Patterns That Work
How winning app ads open: where the hook goes, how fast it lands, how long it runs, and six hook patterns from the Adlist library to adapt for your app.
The hook is the first thing a viewer sees or hears, and in a feed it decides whether the rest of your ad gets watched at all. Every ad in Adlist is tagged by its hook: the type, where it appears and the second it ends. Looking across the library, a few rules hold almost everywhere, and a handful of patterns come up again and again in the ads with the biggest reach.
Put the hook on screen
72% of the ads in the library show their hook as on-screen text. Another 23% speak it in a voiceover, and only 5% leave it to the post caption. Most people scroll with the sound off, so text is the one channel you can count on. If your hook is spoken, caption it too.
Land it in three seconds
The typical hook in the library ends at the three-second mark, and 72% are done by then. That is the window to say who the video is for and why they should keep watching. Save the app name, the features and the logo for after the hook has done its job.
Keep it to one short line
The median hook is nine words long, and 60% use ten words or fewer. A hook that has to be read twice has already lost the viewer. Write the line, then cut it until it still makes sense with half the words.
Choose a hook type that fits your app
Not every type of hook reaches the same audience. In the library, aspirational, skit, meme and reaction hooks have the highest median views, while founder stories and testimonials sit lower. Views measure reach, not installs, so treat this as a sign of what spreads in the feed rather than what converts. Each type is explained on the hook examples page.
Six hook patterns to borrow
These patterns show up again and again among the most viewed ads in the library. Each one is a structure, not a script. The example lines below are written for illustration, so swap in your own audience, problem and app.
1. The “they made an app for that” reaction. The creator reacts with surprise at finding the app, as if they can’t believe it exists. It works when the idea itself is the selling point, because the viewer’s first thought becomes “wait, what app?” For example: “Wait, someone actually made an app that plans my week for me?”
2. The quoted objection. The ad opens on a doubt someone has said out loud, shown in quotation marks, and the rest of the video answers it, often with a before and after. It turns a common complaint into the reason to watch. For example: “‘You can’t learn a language in ten minutes a day.’ Day 1 vs day 90.”
3. The “me when” moment. A caption describes a small, specific situation the viewer has lived through, and the app appears as part of it. The more specific the moment, the stronger the “that’s me” reaction. For example: “Me checking my budget app before saying yes to brunch.”
4. The “how do I get this?” tutorial. The ad shows a result people want, such as a photo style or a passed test, and promises to show how. The app arrives as the answer, so the tutorial is the pitch. For example: “How to get this film-camera look on your phone.”
5. The builder’s pitch. The founder, or someone close to them, says they built the app and dares the viewer to like it. It trades polish for a person and a reason the app exists, which reads as honest in a feed full of ads. For example: “I built this app because I kept forgetting my plants. You’re going to love it.”
6. The question the viewer answers in their head. A direct question, often aimed at a specific group, makes people answer it silently and stay for the reveal, with the app as the twist. For example: “Students, what’s the one subject you’d drop if you could?”
A checklist for your next hook
- It works with the sound off: the line is on screen.
- It is over by the three-second mark.
- It fits in about ten words.
- It names who the video is for, or a moment they recognise.
- It makes the viewer want the next second: a question, a surprise, a result or a doubt to settle.
- The app name and features come after the hook, not in it.
The fastest way to get better at hooks is to study a lot of them side by side. Filter the library by hook type or format, save the patterns that fit your app, and test two or three against each other rather than polishing one.