Guide · launch
SaaS launch assets checklist
October 23, 2026 · 10 min read
Launches stall on asset chores: someone still needs a 1024 icon, someone else asks for OG, and the favicon is still the Next.js default. Use this checklist, then generate everything from one logo in Launch Kit. Screenshot ASO sets belong in the Studio; this list is the icon, splash, and social layer.
Web and marketing site
Ship the favicon stack, theme-color, and at least one OG/Twitter card before the public URL goes out. If the product is installable, add manifest icons the same day.
- Favicon ICO + PNG + apple-touch-icon
- Optional SVG favicon
- OG 1200×630 + Twitter card
- theme-color / brand fill
- PWA manifest icons 192/512 any + maskable (if installable)
Mobile apps
Native or Expo/Flutter apps need store masters and splash continuity. Generate iOS and Android together so padding matches across ecosystems.
- iOS 1024 opaque master + AppIcon set
- Android adaptive foreground/background + legacy mipmaps
- Play high-res 512 icon
- Splash / Expo splash.png with matching backgroundColor
Desktop and cross-runtime
Electron and Tauri ships often forget ICNS/ICO until the week of signing. Enable the desktop pack in Launch Kit when those targets are real, not after the notarization appointment.
- macOS ICNS
- Windows multi-size ICO
- Tray/status variants if your shell needs them
Store listing graphics (beyond icons)
Play feature graphic (1024×500) and screenshot sets are listing assets. Feature graphic can come from Launch Kit's store pack; full screenshot narratives belong in App Snaps Studio so sizes match App Store Connect and Play Console.
- Play feature graphic
- Store screenshot slides via Studio
- Optional ASO draft captions per locale
One-pass workflow
Upload the logo once in Launch Kit, enable every pack you need, download the ZIP, and drop folders into each repo (web public/, iOS Assets.xcassets, Android res/, Expo assets/). Re-run the ZIP when branding changes instead of editing PNGs in place.