On this page
- The steps
- Real mobile app video ads
- Use Veo for the hook and payoff only
- Set up Veo 3.1 in Google Flow
- Write prompts that trim cleanly
- Borrow the pattern from long-running app ads
- Record the demo and finish the edit
- Test three openings, then scale the winner
- Prompts to copy
- Three to five openings to test against one demo
- Mistakes to avoid
- Questions
Real mobile app video ads to model yours on
3,317 video ads from 298 advertisers in the Meta Ad Library, read October 5, 2026. The median one ran 38 days, and an ad still paid for after months is the closest public sign that it works. Live ads first.
- Ran 1 day
- Ran 2 days
- Ran under a day
- Ran under a day
- Ran 1 day
- Ran under a day
- Ran 2 days
+3,305 more mobile app video ads
Hooks, landing pages and run length for each
- Ran 1 day
- Ran under a day
- Ran 4 days
- Ran under a day
Every creative, with its copy, format and run length
The openers that ran longest
ΰ€ͺΰ€Ήΰ€²ΰ€Ύ ΰ€ΰ₯ΰ€² @Rs 1/- π
InstaAstro Β· running 1,395 daysCuentos en 23 idiomas para ti!
Beelinguapp Β· running 756 daysClassic merge puzzle game
Gossip Harbor Β· running 748 daysJoin Local Groups & Make New Friends
Meetup Β· running 590 days
Use Veo for the hook and payoff only
Veo 3.1 is strong at lifestyle footage: people, rooms, light, motion and matching ambient sound. It is a poor choice for your interface. A generated phone screen tends to show wrong buttons, garbled text or features you do not have, and viewers notice. Treat Veo as your B-roll crew and your real screen recording as the proof.
That split gives you a simple 15-second structure built around one promise. The generated shots make people feel the problem and the payoff. The recording shows the app doing the work in between. For more formats beyond this one, see mobile app video ads.
- 0 to 3 sec: a relatable problem, generated with Veo
- 3 to 10 sec: a real demo of one useful action
- 10 to 12 sec: the payoff, generated with Veo
- 12 to 15 sec: end card with app icon, name and download line
Set up Veo 3.1 in Google Flow
On desktop, open a project in Google Flow, click the model name in the prompt box and choose Video. Pick Veo 3.1 Lite, set the aspect ratio to 9:16 portrait, and choose a 4 or 6 second clip. Shorter is better here. You want a strong moment you can trim, not a long take that drifts.
Google lists December 5, 2026 as the retirement date for Veo 3.1 Fast and Quality in Flow. If a saved workflow depends on those, move it to Lite now so your process does not break mid-campaign. Developers who generate through Vertex AI should check the current Veo 3.1 documentation for the options available there.
Use Frames when you already have an image the shot must start from, such as a brand-approved still of a kitchen, gym or desk. Flow also supports reference-based generation, which Google calls Ingredients to Video, to keep a character or object consistent across clips. Generate the hook and the payoff as separate clips so you can swap either one without rebuilding the ad.
Want mobile app video ads like these for your product?
The mobile app video ads that kept running, read from the ad libraries. Every change waits for your approval.
Write prompts that trim cleanly
Keep each prompt to one action and one camera shot. Google's Veo prompting guide supports specifying camera movement, ambient sound and dialogue directly in the prompt, so use all three. Put the movement in the first half-second so the clip works as an opener even after you trim the head.
Ask for no captions, no logos and no visible phone screen. Generated text is unreliable, and you will add headlines in your editor anyway. Name objects a viewer can read at a glance, like half a lemon, a running shoe or a paper grocery list. Concrete details make the problem feel real in two seconds.
Iterate by changing one thing at a time. If the framing is wrong, rewrite only the camera line. If the mood is off, rewrite only the lighting. Generate a few takes of each shot and keep the one with the cleanest first second. Save the prompts that work so each new feature gets a fresh hook quickly.
- Order: format and length, subject, action, camera, lighting, sound, exclusions
- One continuous shot per clip
- Describe sound: room tone, footsteps, chatter
- End every prompt with what to leave out
Borrow the pattern from long-running app ads
The mobile-app category in the Meta Ad Library has 3317 video ads from 285 advertisers, with a median run of 38 days. The openers that ran longest are blunt. Meetup ran "Join Local Groups & Make New Friends" for 589 days with a Download button. Spotify ran "Give every step a soundtrack." for 331 days with Install now.
Whatnot ran "Yup, you can buy new outfits without breaking the bank." for 386 days. Flipp ran "Download Flipp for Free" for 284 days. The pattern is one benefit, one verb, one audience. None of them explain the whole product. Each opener names what you get or what you do, in plain words.
Translate that to Veo. Your generated hook should show the same single promise: a group making room for a newcomer for a social app, a runner heading out at dawn for a music or fitness app. Then match your closing line to the button. The most common buttons in this category are Install now, Learn more, Download and Sign up. The Sprites ads library shows real ads from a category, so you can study more openers before you write your own. Start with mobile app ads.
Record the demo and finish the edit
Record your app with clean sample data, notifications off and Do Not Disturb on. Capture one action only: the tap and its result. Then crop in so the key button and the outcome fill the frame. If a viewer cannot read it on a phone held at arm's length, the crop is too wide.
Build the edit in a 1080 by 1920 vertical timeline. Keep headlines and captions away from the top and bottom edges where platform interface elements sit, and check the safe areas in the Meta ad specs. Hold the end card for 2 to 3 seconds with the app icon, app name and a download line that matches your ad button.
Veo can generate ambient sound and dialogue, which gives the hook natural room tone. Keep that sound under any music or voiceover and smooth the cut into the demo so the audio does not jump. Then watch the whole ad muted. Can you still tell what the app does and why you would install it? If not, fix the captions before you fix anything else.
Test three openings, then scale the winner
For your first test, keep the demo and end card identical and make three different openings: the problem, the finished result and the app result. That way you are testing the hook, not three entirely different ads. Name each file by its opening so results stay readable.
Run all three under the same conditions and compare them on the same measures. Retire the weakest opening, then write two new hooks against the winner using a single changed variable, such as a different person, room or camera move. The category median run is 38 days, so keep winning ads running while you test replacements.
If you would rather not run this loop yourself, Director by Sprites is a full creative team for your startup. Every Monday you get finished, on-brand video ads, reviewed by a human. You can see how it works at Director. Either way, keep the weekly rhythm: new hooks, same proven demo.
Prompts to copy
Paste each one as written, then change the product, the setting and the light to match your own footage.
Hook: the problem
Vertical 9:16, 4-second candid lifestyle ad. A tired young adult in a small apartment kitchen opens the fridge in the first half-second. Over-the-shoulder handheld shot reveals half a lemon, leftover rice, and a bell pepper. They pause, unsure what to cook. Warm kitchen light contrasts with the cool fridge light. One continuous shot, natural room tone and fridge hum. No dialogue, captions, logos, or visible phone screen.
Hook: community and belonging
Vertical 9:16, 6-second handheld shot in a sunny city park. A small group of adults in casual clothes laugh and wave as one more person walks up carrying a folding chair, and the group makes room. Camera starts at chest height and pushes in slowly. Natural daylight, soft background chatter, birds, no intelligible speech. One continuous shot. No captions, logos, or visible phone screen.
Hook: motion and momentum
Vertical 9:16, 4-second tracking shot at dawn on an empty neighborhood street. A runner in plain gray clothing, seen from behind, starts jogging in the first half-second as the camera follows at waist height. Cool blue light, with breath and rhythmic footsteps on pavement as ambient sound. Keep the runner's face out of frame. One continuous shot. No music, captions, logos, or visible phone screen.
Payoff: the finished result
Vertical 9:16, 4-second close-up payoff shot. A hand sets a plate of freshly cooked pasta with basil on a wooden table, steam rising. Slow push-in, shallow depth of field, warm evening window light. Soft sizzle fades to quiet room tone with a gentle plate clink. One continuous shot. No dialogue, captions, logos, or text on screen.
Hook: start from your own still (Frames)
Vertical 9:16, 6-second shot that begins exactly on the uploaded first frame of a tidy home desk with a closed laptop and a notebook. A hand reaches in from the right, flips the notebook open to a checked-off to-do list, then the camera slowly pushes in. Soft morning light, quiet room tone, a single pen click. Keep the desk layout unchanged. No captions, logos, or visible phone screen.
Three to five openings to test against one demo
| Opening | What Veo generates | On-screen line | Why test it |
|---|---|---|---|
| The problem | Fridge stare, messy desk, empty street | Nothing to cook tonight? | Hooks viewers who feel the pain first |
| The result | Finished dinner, completed run, tidy desk | Dinner in 10 minutes | Leads with the payoff, then shows how |
| The app result | No Veo; real screen recording from second 0 | Pick 3 ingredients. Get dinner. | Shows the product immediately |
| Belonging | Group in a park making room for a newcomer | Make new friends near you | Mirrors the plain promise of Meetup's long-running opener |
| The plain offer | Short lifestyle shot, then a download line | Download free | Mirrors direct openers like Flipp's "Download Flipp for Free" |
Mistakes to avoid
- Letting Veo generate your app screen instead of using a real screen recording.
- Packing several actions and camera moves into one prompt, which makes clips hard to trim.
- Leaving captions or logos in the prompt and getting garbled text in the footage.
- Testing three completely different ads instead of three openings on the same demo and end card.
- Building a workflow on Veo 3.1 Fast or Quality in Flow when Google lists them for retirement on December 5, 2026.
- Skipping the muted watch-through, so the ad makes no sense without sound.
Rather have the videos made for you?
Director by Sprites is a full creative team for your startup. Every Monday you get finished, on-brand video ads, reviewed by a human. You never write a prompt.
Apply to Director by Sprites βQuestions
Can Veo 3.1 generate my app's screen for the ad?
You can try, but it is risky. Generated interfaces often show wrong buttons, garbled text or features your app lacks. Use Veo for the hook and payoff, and cut to a real screen recording for the demo.
What aspect ratio and clip length should I use for app ads?
Use 9:16 portrait. In Flow with Veo 3.1 Lite, choose a 4 or 6 second clip and trim it to the strongest moment. Platform placements vary, so check the Meta ad specs for your placement.
Which Veo 3.1 model should I pick in Flow?
Pick Veo 3.1 Lite. Google lists December 5, 2026 as the retirement date for Veo 3.1 Fast and Quality in Flow, so Lite is the safer base for a reusable workflow.
Does Veo 3.1 add sound to the clip?
Yes. Google's Veo prompting guide supports specifying camera movement, ambient sound and dialogue in the prompt. For app ads, ask for room tone or natural sound, then layer music and captions in your editor.
How do I keep the same look across the hook and the payoff?
Use Frames to start a shot from a specific image, or use Flow's reference-based generation (Ingredients to Video) to keep a character or object consistent. Also reuse the same lighting and setting words across prompts.
How many hooks should I test for one app ad?
Start with three openings on top of an identical demo and end card: the problem, the finished result and the app result. Keep the winner and write two new hooks against it.