AppWispr

Find what to build

The Prelaunch Creative Prioritization Playbook: What to Build First When You Only Have 1 Designer

AW

Written by AppWispr editorial

Return to blog
L
AS
AW

THE PRELAUNCH CREATIVE PRIORITIZATION PLAYBOOK: WHAT TO BUILD FIRST WHEN YOU ONLY HAVE 1 DESIGNER

LaunchMay 14, 20266 min read1,162 words

You have one designer, two weeks before launch, and five possible assets: icon, two screenshots, 15s preview clip, landing hero, and ad creative. Build the highest-ROI pieces first. This post gives a simple decision framework based on channel mix, expected CPA, and time-to-value, plus a two‑week sprint checklist and practical export presets your designer can drop into Figma or straight into an asset builder.

prelaunch-creative-prioritization-playbook-1-designerapp-store-screenshotspreview-videolanding-heroad-creativeprelaunch-checklistexport-presets

Section 1

The single principle: prioritize the asset that reduces your acquisition risk fastest

Link section

When creative bandwidth is the limiting factor, treat assets as risk mitigators. Which missing asset will prevent a channel from working, or make acquisition costs balloon? Prioritize that. For example, if half your prelaunch plan is App Store search and browse, screenshots and an app preview are far more critical than a new landing hero.

Channel mix, expected CPA, and time-to-value map directly to priority. Channels with low time-to-value (organic App Store discoverability, product hunt, early PR) need store assets first. Paid channels (Facebook/Meta, Google UAC) need ad creative and short preview clips to hit acceptable CPAs quickly.

  • If App Store is core: icon → 2 screenshots (value+proof) → 15s preview clip.
  • If paid ads are core: ad creative → 15s preview clip → landing hero (for retargeting/LP).
  • If Product Hunt / community launch: landing hero → screenshots → icon.

Section 2

A practical decision matrix founders can use in 60 seconds

Link section

Score three inputs (channel mix, expected CPA, time-to-value) quickly: channel mix weight (0–5), expected CPA sensitivity (0–5), and asset complexity/time (hours). Multiply channel weight by CPA sensitivity to get a channel urgency score. Rank assets by their total urgency divided by hours-to-produce. This yields a simple priority list you can agree with your designer.

A short worked example: 60% organic App Store (weight 4), CPA sensitivity low (1), screenshot production estimated 6 hours. Priority score = (4×1)/6 = 0.67. Compare that with paid ads where ad creative weight 3, CPA sensitivity 5, estimated 8 hours → (3×5)/8 = 1.875 — ad creative wins.

  • Step 1: Assign channel weights (sum to 10).
  • Step 2: Rate CPA sensitivity (1 low → 5 high) for each channel.
  • Step 3: Estimate hours-to-complete each asset.
  • Step 4: Compute priority = (channel weight × CPA sensitivity) / hours.

Section 3

What to build first (asset-by-asset playbook)

Link section

Icon — Why first sometimes: it's the smallest, fastest polish that affects discoverability and conversion on stores and ad thumbnails. Make a few rapid variants (flat vs. depth, single symbol vs. logotype) and split-test. Deliverables: 1024×1024 PNG for App Store; 512×512 and 192×192 for other uses.

Screenshots (pick 2 for the first sprint) — Two screenshots force discipline: one hero slide showing primary value proposition and one proof slide (social proof, key metric, or standout feature). Follow App Store sizing and content rules strictly; getting screenshots wrong can delay review or harm conversion. Export all required sizes from your master artboard so you can reuse for Play Store and landing pages.

  • Icon exports: App Store 1024×1024 PNG (sRGB), 72–120 DPI.
  • Screenshot pair: 1 value-oriented hero + 1 proof/feature slide. Export master at highest device size and generate store sizes (iPhone 6.7", 6.5", 5.5" and Play Store equivalents).
  • Keep text short (6–10 words per slide) and readable at phone width.

Section 4

The 15‑second preview clip, landing hero, and ad creative — when to invest

Link section

15s preview clip — high impact for both App Store and paid channels, but high friction. If your prioritized channels need motion (UAC, Instagram Reels, Apple App Store preview), invest only after you have stable screenshots and icon. Keep the clip to 15 seconds, show a single flow start-to-finish, and export to App Store preview specs to avoid upload rejections.

Landing hero and ad creative — Think of the landing hero as the conversion bridge for paid and PR traffic. If you plan email or community acquisition, a simple hero with a clear CTA beats a flashy page. For paid ads, create a compact asset set: square image, vertical story, and the 15s clip trimmed for 15s/6s spots.

  • App Preview checklist: 15–30s accepted, H.264 or ProRes (App Store specifics vary). Match frame size to device slot and include stereo track even if silent. (See Apple guidelines.)
  • Ad sizes: 1:1 square, 9:16 vertical, and 16:9 landscape; produce 3 text-overlay variants for A/B testing.
  • Landing hero: headline (8–12 words), one subline, primary CTA, trust cue (testimonial or metric).

Section 5

Two‑week sprint checklist and export presets (copy this into Figma or your task board)

Link section

Week 1 — Stabilize fundamentals (days 1–7): Day 1: Align on priority using the 60-second matrix. Days 2–4: Designer produces 3 icon variants and two screenshot drafts; product team selects copy for screenshots. Days 5–7: Iterate screenshots, produce final icon, and export store-ready sizes.

Week 2 — Amplify and repurpose (days 8–14): Day 8–10: Produce 15s preview clip from screen-recorded flows, edit and compress to store specs. Day 11: Create ad creative permutations (1:1, 9:16, 16:9) using screenshot stills and preview clip snippets. Days 12–14: Build landing hero, assemble upload packages, and sanity-check all exports against App Store/Play specs.

  • Export presets (start with these master outputs): Master screenshot artboard: 1290×2796 px (iPhone 6.7" master) export to 1290×2796, 1284×2778, 1242×2208, 1080×1920 for Android; keep PNG.
  • Icon master: 2048×2048 px source → export 1024×1024 PNG for App Store and 512×512 for other uses.
  • Preview clip: master 1920×1080 @30fps H.264, 15–30s. Use ffmpeg preset to target App Store accepted codecs if needed.
  • Ad sizes: 1080×1080 (1:1), 1080×1920 (9:16), 1920×1080 (16:9) — export MP4 H.264 and static PNG/JPG variants.

FAQ

Common follow-up questions

Do I need an app preview video for launch?

Not always. If your primary acquisition channels are organic App Store and product hunt, a short 15s preview materially helps conversion—but only after you have strong screenshots. If your CPA model depends on paid ads, a preview clip can also supply short ad spots and improve paid efficiency. Follow App Store preview specs exactly to avoid upload friction. (developer.apple.com)

How many screenshot languages or device sizes should I export before launch?

Start with one primary locale and export all required device sizes for App Store and Google Play. Localize screenshots only after you validate messaging. Export masters at the largest device (iPhone 6.7" / 1290×2796 px) and generate the smaller sizes from that source. (mobileaction.co)

Can one designer realistically deliver everything in two weeks?

Yes — if you focus. Use the prioritization matrix to pick the 2–3 highest-impact assets, use templates or asset generators for variations, and avoid over-polishing. Reserve the second week for repurposing (ads + landing) rather than new hero concepts. (appshots.dev)

What common export mistakes cause App Store upload failures?

Common issues: wrong resolution or orientation for preview videos, incorrect codec/frame rate, missing audio track on App Preview uploads, and using deceptive or unsupported imagery in screenshots. Validate against Apple’s upload guidelines before submitting. (developer.apple.com)

Sources

Research used in this article

Each generated article keeps its own linked source list so the underlying reporting is visible and easy to verify.

Next step

Turn the idea into a build-ready plan.

AppWispr takes the research and packages it into a product brief, mockups, screenshots, and launch copy you can use right away.