App promotion

How to advertise a product nobody can hold

No unboxing, no texture, no reveal. What you are selling only exists once someone taps through — which changes the creative, the angles, and every number you look at afterwards.

Most advice about user-generated video ads assumes a physical product. Hold it up. Open the box. Show the before and after on your own face. That advice is fine, and almost none of it transfers to an app.

An app has no object at the center of it. What you are selling is an outcome — the invoice sent, the workout finished, the receipt that finally got filed somewhere findable. And the install costs nothing, which sounds like an advantage and is mostly a complication: a person will tap on very little, and "very little" is exactly the intent that never opens the app again.

So the job is narrower than it looks. Not to make the install attractive — to make the right install attractive, and to make it obvious enough that the person arrives already knowing what they came to do.

Three things that make app ads their own problem

Each one breaks a habit you picked up advertising physical goods.

There is no object

Nobody can turn your app over in their hands. The only tangible thing you have is the interface, which makes screen footage your product shot rather than a nice-to-have.

The value is an outcome

Nobody wants a habit tracker. They want to have gone to the gym. The ad shows the outcome and treats the app as the route to it, not the point of it.

The install is free

Free means low friction and low commitment in the same breath. The conversion that matters is what happens twenty minutes later, and your ad decides whether it happens.

The core format: screen plus face

The format that carries most app advertising is a screen recording cut against a talking-head reaction. One supplies proof, the other supplies a reason to care. Neither works alone.

Screen recording alone is a product demo — it shows what the app does and gives nobody a reason to sit through it. A face alone is a person making claims about software you cannot see, which is the shape of every ad the viewer has already learned to skip.

Together they do something specific. The person states a problem you recognize, and then the screen answers it in a way that cannot be faked. That second half does the heavy lifting: a viewer who has seen the actual interface has partly used your app, and the store page becomes a formality rather than a decision.

One video, shot by shot

Roughly 20 to 35 seconds. The proportions matter more than the timings.

The problem state, said out loud

Open on the mess, not the fix. "I had three months of receipts in a shoebox and a tax deadline." Specific enough that the right person recognizes themselves and the wrong person keeps scrolling — both are wins.

The turn

One sentence of transition, not a product introduction. "So I started photographing them the second I got them." That describes a behavior. The app enters as the thing that made the behavior possible.

The exact screen

Cut to real capture of the one screen that does the one thing. Not onboarding, not settings, not a montage. Slow enough to read. This is where the ad stops being a claim.

The outcome, in their own terms

Back to the face for the result. "Filing took an evening instead of a weekend." Keep it proportionate to what the app actually did — overstating here is what produces installs that churn.

The ask, with expectations set

Say what happens next and what it costs. A viewer who knows there is a paywall on day seven is a better install than one who finds out on day seven.

Why abstract benefit claims fail here

"Stay organized effortlessly" is not a claim, it is a category. It describes four hundred apps equally well, so it describes yours not at all — and the viewer has no way to check it, so they do not try. "Here is the screen where I photograph a receipt and it files itself" is checkable in two seconds, and being checkable is most of why it works. Whenever you are tempted to write a benefit, write the screen instead.

Generate angles by problem, not by feature

The most common mistake in app creative is a video per feature. Features are how your roadmap is organized; they are not how anyone experiences the product. Build the list this way instead:

  1. Write down the problems people arrive with, in their words. Not "lacks expense visibility" — "I never know how much I've actually spent this month." Support tickets and app store reviews are already full of these, correctly phrased.
  2. Give each problem one video. If two problems share a screen they are still two videos, because the person watching only has one of them.
  3. Segment by who has the problem. A freelancer and an agency owner may use one feature for genuinely different reasons. That is two angles, and they will perform differently.
  4. Add the objection angles. "I tried three of these and gave up" is a problem statement too, and often the highest-intent audience available — people who already agree the category is worth solving.
  5. Then vary the opener on whatever wins. Once a problem statement works, the next round is four new first lines on the same body, not four new problems. See hook ideas for openers worth trying.

A cheap install can cost you money

It is easy to write an app ad that produces a very low cost per install and damages the business. Vague curiosity, a hook implying something the app does not do, a promise of free where there is a paywall — all of these move installs and none of them move users. The person downloads, opens once, finds a different product than the one advertised, and leaves. You paid for that.

It is worse than it sounds, because the ad platform is learning from it. Optimize toward installs and the algorithm gets very good at finding people who install things — a real behavior, and a different one from needing what you built. Feed it enough misleading installs and it will bring you more of exactly those.

The fix is not subtlety, it is accuracy. Say what the app does, say what it costs, and let the ad disqualify people. A hook that filters out three viewers to keep the fourth is doing its job. Cost per install will look worse and everything after it will look better — which is the subject of testimonial ads and CPI.

What to measure past the install

Installs tell you the ad worked. Only these tell you whether it worked on the right people.

What to look atWhat it actually tells youWhen it matters
Install rate on the store pageWhether the ad set an expectation the listing confirms. High taps with low installs means the two disagree.First 48 hours of a new creative
Activation rateThe share of installs completing the one action that makes your app useful. The most honest signal you have.Always, per creative
Day 1 and Day 7 retentionWhether a specific ad brings people back. Two ads with identical CPI routinely differ enormously here.From week one onward
Cost per activated userSpend divided by activated installs rather than total installs. This is the number that should drive budget.Whenever you compare creatives
Trial start or paid conversionThe commercial outcome. Slow to accumulate, so it confirms rather than steers.After enough volume to be real

Report each of these per creative, not per campaign. A campaign average hides one video subsidizing three bad ones.

One note on app-store creative

These are paid social ads. They are not the same asset as the preview video on your App Store product page, and you should not plan to reuse one as the other — Apple requires an App Preview to be captured from the app itself, so a performance shot on a phone in a kitchen does not qualify however good it is. Google Play works differently again. Store rules change, and the platforms' own current documentation is the authority. Treat store creative as its own project with its own constraints.

Common questions about app creative

How many videos do I need to start?

Five to ten distinct problem statements is a realistic first round. The count matters less than the spread — ten videos of one angle teach you almost nothing, while five different problems teach you where the demand is. How many UGC ads you need to test shows how to size that against your own budget.

Do I need to supply screen recordings?

Yes, and you are the only one who can. Record the specific screens on a real device, unhurried, with personal data removed. Capture more than you think you need — the useful shot is usually three seconds longer than the one you planned.

Can an AI creator demonstrate my app?

The person performs the script and speaks to camera; your screen capture supplies the demonstration. That combination is how most app ads are assembled regardless of who is on camera. What we cannot do is have someone describe an outcome they personally experienced.

Should the ad mention the price?

If people hit a paywall early, yes. Naming it costs you some installs and buys you better ones. Hiding it produces a spike in downloads and a matching spike in one-session users.

What length works for app ads?

Long enough to show one screen doing one thing properly, which is usually 20 to 35 seconds. Shorter cuts tend to lose the demo, and the demo earns the install. Test a short version of a proven winner rather than starting short.

How fast can new creative be made?

Yuugc delivers in 48 hours, with script writing from your brief, caption variants, one revision round and full commercial rights included, at around $50 a video. See pricing for how volume affects the quote.

Send us your screens. We'll write the rest.

Tell us the problems your users arrive with and we'll turn each one into a script and a video, back inside 48 hours.

Get a quote