The No‑Designer Launch Kit: 7 Contractor‑Ready Visuals a Solo Founder Must Ship (and Exact Briefs to Get Them Done in 48 Hours)
Written by AppWispr editorial
Return to blogTHE NO‑DESIGNER LAUNCH KIT: 7 CONTRACTOR‑READY VISUALS A SOLO FOUNDER MUST SHIP (AND EXACT BRIEFS TO GET THEM DONE IN 48 HOURS)
As a solo founder you don’t have time for design back-and-forth. Ship the seven visuals App Stores and ad platforms actually need—icon, five store screenshots, a 30‑second preview, and three ad frames—by sending contractors airtight briefs, specs, and acceptance tests. Below you’ll find exact copyable briefs, pixel-perfect export settings, and quick QA checks that get deliverables accepted and ready to upload within 48 hours.
Section 1
What to ask for (the seven deliverables and why each matters)
Keep this short for your contractor: list the seven outputs you need and the single conversion goal for each. The store icon is a recognition cue in search and the Play feature graphic / App Store metadata; screenshots are the conversion elevator; the app preview video sells motion and flow; ad frames are your testing atoms for paid campaigns.
Deliverable clarity reduces rework. For App Store Connect you must match device-family screenshot sizes and video specs exactly; Google Play has its own icon and feature-graphic rules. If the contractor delivers correct pixels + a clean acceptance checklist, you’ll avoid multiple rounds of edits and App Store upload failures.
- 1× App icon (native source .svg or layered .psd/figma + exported 1024×1024 PNG for App Store & 512×512 for Google Play)
- 5× Store screenshots (single-device family: provide the largest required resolution so platforms can scale down)
- 1× 30s App Preview video (matches screenshot resolution, 15–30s, H.264/H.265/codec as required)
- 3× Ad frames (portrait, square, and landscape; each optimized for paid channels)
Section 2
Exact contractor brief: copy-paste for icon, with acceptance tests
Brief: “Deliver a final app icon and editable source that reads at small sizes and follows platform rules. Provide layered Figma or PSD + exported PNGs: 1024×1024 (App Store), 512×512 (Play); final PNGs in sRGB, 32‑bit PNG (alpha allowed for Play). Keep the mark centered inside a 60% safe area; avoid small text.”
Acceptance tests: open the 1024×1024 PNG on a phone mockup at 60px and confirm the core mark is legible; upload the 512×512 PNG to Play Console's local preview and ensure Google’s auto-mask does not cut important details. If either fails, the asset is rejected.
- File types: Figma/PSD/SVG + flattened PNGs
- Color space: sRGB; no color profiles embedded
- Safe area: central 60% circle or square, no micro-text below 24px equivalent
- QA: verify legibility at 60px and 40% opacity on various backgrounds
Sources used in this section
Section 3
Exact contractor brief: 5 screenshots (story-driven, production specs, acceptance tests)
Brief: “Produce five localized screenshots that tell a single 5‑scene story: 1) Hero + primary CTA message, 2) Core value / main feature, 3) Secondary feature or social proof, 4) Onboarding or key flow, 5) Closing benefit + CTA. Provide source files and exported PNG/JPEG for the largest device family (e.g., iPhone 6.9" at 1290×2796 or current largest Apple class). Use white or semi-opaque caption bars; captions must be short (10–12 words).”
Production specs: supply artboards sized to the App Store’s largest device class so App Store Connect can scale down automatically. Prefer PNG for UI clarity and export at 72–150 DPI depending on platform guidance. Acceptance tests: upload screenshots to the platform preview tool (App Store Connect / Play Console) and verify no cropping, legible caption text, and that the main tap targets/UX aren’t obstructed by the platform chrome.
- Provide layered source (Figma/PSD) + exports for the largest device family (portrait) in PNG and JPEG
- Avoid placing critical UI elements inside the top/bottom 80px (safe margins depend on resolution)
- Write captions as benefit-forward microcopy (10–12 words)
- QA checks: platform preview shows full image, captions readable at mobile widths, no misleading overlays
Sources used in this section
Section 4
Exact contractor brief: 30‑second app preview (how to shoot, encode, and pass upload)
Brief: “Produce a 15–30s motion preview that demonstrates the main flow from sign-up to core outcome. Shoot clean screen recordings (native recorder) or export from prototype tools at the target device resolution. Add minimal motion titles, a simple music bed or silence, and deliver a stereo audio track (even if silent) because App Store requires it.”
Encoding & acceptance: match the screenshot resolution for that device family, 30 fps, H.264 or Apple‑approved codec, AAC stereo audio, and keep within App Store size limits. Acceptance tests: confirm video plays without black bars in App Store Connect preview, and that App Store does not reject for codec/frame-rate mismatch. If you use Play Store promo video, ensure it satisfies Play Console upload guidance.
- Length: 15–30 seconds (Apple allows up to 30s for app previews)
- Frame rate: 30 fps; Resolution must match device-family screenshot resolution
- Audio: stereo AAC track (even if silent — include a low‑level ambient track if needed)
- Export tip: deliver both .mov and .mp4 exports and a short README with ffmpeg/encoder settings used
Section 5
Exact contractor brief: 3 ad frames (portrait, square, landscape) and quick test plan
Brief: “Deliver three static ad frames optimized for paid channels: portrait (9:16) for Stories/Reels, square (1:1) for feeds, and landscape (16:9) for YouTube/preview. Use the same visual language as store screenshots but tighter copy: 3–6 words headline, 6–12 words supporting line, and a visible CTA badge. Provide layered source and exports in PNG and JPG optimized for web.”
Test plan & acceptance: include a simple A/B test plan—swap headline or CTA across the three frames. Acceptance tests: check legibility at 320px width, CTA tap area visible, and file sizes under typical ad platform limits (keep JPGs below 150 KB where possible). Deliver alt text and suggested three ad copy variants for quick experiments.
- Portrait: 1080×1920 px; Square: 1080×1080 px; Landscape: 1920×1080 px
- Keep headline to 3–6 words, supporting line to 6–12 words
- Export: high-quality JPG for ads (progressive), PNG for transparency needs
- QA: legible at 320px, under 150 KB for feed JPGs, and CTA clearly visible
Sources used in this section
FAQ
Common follow-up questions
Can a single contractor produce all seven assets in 48 hours?
Yes, if you scope it tightly and provide clear source material (copy, UI screenshots, brand colors, and an interaction script). Use the exact briefs above, request layered Figma or PSD files, and ask for prioritized exports first (icon + one hero screenshot) so you can start uploads while the rest are finalized.
What common App Store preview video mistakes cause rejections?
Common issues: wrong resolution or device-class mismatch, incorrect frame rate (must be 30 fps), missing stereo audio track, unsupported codec/bitrate, and presence of device overlays or fake UI. Encode to the platform’s specs and deliver both .mov and .mp4 to avoid encoder issues.
Should I localize screenshots before launching?
Localize at minimum for your top markets. Start with English and your two highest-traffic markets—provide localized copy layers in the source files so the contractor can quickly swap text without re-layout. This reduces time and ensures consistent layout across languages.
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.
Apple Developer
Screenshot specifications - App information - Reference - App Store Connect - Help - Apple Developer
https://developer.apple.com/help/app-store-connect/reference/app-information/screenshot-specifications/
Android Developers
Google Play icon design specifications
https://developer.android.com/distribute/google-play/resources/icon-design-specifications?hl=en
AppLaunchFlow
App Store & Play Store Screenshot Sizes 2026 (iPhone 16 Pro Max) | AppLaunchFlow
https://www.applaunchflow.com/tools/store-sizes
Referenced source
App Store Preview Video guidelines (resolution & export best practices)
https://appscreenshot.net/guides/app-store-screenshot-size-guide/
Referenced source
Complete Guide to Running Effective Facebook Ads
https://nicholaserik.com/wp-content/uploads/2022/09/Facebook-Ads-Complete-Guide-Setup-Testing-Creative-Formulas-Audiences-and-Launch-Structure-v1.3.pdf
Adobe
Best Practices for Digital Display Ads (Adobe)
https://business.adobe.com/content/dam/dx/us/en/resources/ebooks/best-practices-for-digital-display-ads/best-practices-for-digital-display-ads.pdf
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.