Should I run ads before my app launches?

Not to acquire installs, since there is nothing to install. A small budget to fill a waiting list can be worth it if your cost per email is low, but organic and creator routes usually beat paid at that stage.

How big should a waiting list be before launch?

Large enough to produce a meaningful first day, which for most apps means several hundred rather than several thousand. Quality matters more than size: a hundred people who asked for it beat a thousand who were bought.

When should I submit to the App Store?

Two weeks before your intended date, so review delays do not become launch delays. You can hold an approved build and release it manually on the day you choose.

What breaks most often on launch day?

Links. The same URL goes into a dozen placements at once, nobody tests it from inside a social app on an iPhone, and a share of the biggest traffic day the app will have lands on a blank page.

Pre-launch app marketing

Launch day traffic is the easiest attention you will ever get and the easiest to waste, because most of the machinery that captures it has to exist beforehand.

9 August 2026 · PAD team

What is worth doing before release

Activity	Payoff	Do it?
Waiting list with email capture	an audience on day one	yes, always
Store listing written and tested	conversion from day one traffic	yes
Relationships with five to ten creators	coordinated launch week reach	yes
Paid acquisition	nothing, there is no product to install	no
Press outreach	one spike, rarely repeatable	only if the story is genuinely unusual
Content and SEO	compounding, but slow	start, expect nothing until month three

The through-line is that pre-launch work should either capture an address you can use later or build something that keeps working after launch week ends.

The waiting list is the only real asset

Everything else you do before launch is borrowed attention. An email list is attention you own, and it converts far better on release day than any paid channel will for months. Build it with a single page, one clear promise, and one field.

Where the list actually leaks is the link you promote it with. If you share it from an Instagram story or a creator post, it opens in the app's own browser. That works fine for a form. It stops working the moment the page tries to send someone to the store, which is exactly what it will do on launch day.

Set up the launch link before you need it

On launch day the same URL will be in creator posts, your bio, your emails and possibly an ad. If it is a plain App Store URL, it will fail for a share of the people who tap it from inside a social app, and you will be too busy to notice.

Measured on 21,000 taps routed between 3 and 9 August 2026, 19,381 came from inside social apps and 95.6% were iOS. Launch traffic skews harder that way than steady-state traffic does, because it comes from posts rather than search.

One link that routes to App Store, Play or a web page depending on the device.
A campaign tag per placement, so you can tell the creator post from the bio link.
Tested on a real iPhone, from inside Instagram, before the day it matters.

A four week countdown that works

When	Do
4 weeks out	landing page live, list capture running, store listing drafted
3 weeks out	creator outreach, agree on dates rather than hope for coverage
2 weeks out	screenshots final, listing submitted, links built and tested
1 week out	warm the list, brief the creators, prepare the day-one email
Launch day	email first, creators same morning, watch arrival rates not downloads

What launch day is actually for

Not a download record. It is the only moment you get a burst of unqualified attention with which to learn what converts. Instrument it properly and the data is worth more than the spike.

Build the launch link two weeks early and test it where people will actually tap it.

Create a link