Your app's story,
told before the store listing.

Three reasons: paid and social traffic converts better through a page that sells the benefit before the store's cluttered listing; you get real attribution (UTMs, per-page analytics) the store consoles won't give you; and pre-launch, it's the only way to collect emails before there's anything to install.

Yes — dual store badges are built into the CTA block, and your UTM parameters pass through so install campaigns stay attributable. iOS-only or Android-only? Show one badge and use the second CTA slot for a waitlist on the other platform.

Lead with the outcome (the run streak, the strength gain, the sleep score), show the real screens doing it, prove it with ratings and user counts, then ask for the install. Feature grids full of jargon ('AI-powered biometric engine') consistently lose to one concrete outcome per screen.

Yes — generate the page in waitlist mode: same design, email capture instead of store badges. At launch, switch the CTA to download buttons on the same URL and email the list. Your pre-launch ads keep their landing page and their SEO history.

Helpful but not required. Upload whatever screens you have — even builds from TestFlight — and the AI arranges them in device frames with captions. You can swap in polished store screenshots later without touching the rest of the page.

Every subscription starts with a 3-day free trial; Solo is $9/mo after that, with your page live on a pagestrike.app URL plus 1 custom domain (get.yourapp.com). From $19/mo you get 3 domains and no PageStrike branding. No cut of anything, ever — installs are between you and the stores.