Setup and context
App store success depends on four interconnected visual elements: app icon, screenshots, feature graphics, and preview video. While screenshots get most attention, your icon is the "face" users remember, and preview videos drive the highest conversion rates.
Here we treat all four assets as one connected system — why each matters, how to produce them, and how to test them against real download data. The aim is a working ASO (App Store Optimization) approach you can put into practice the same day.
Visual Asset User Journey
Users move through these touchpoints from discovery to download decision:
- Icon (search results, featured, profile)
- App name and subtitle (SEO and clarity)
- Screenshots (first impression)
- Preview video (see the app in action)
- Feature graphic (store featured slots, ads)
All elements work together—only when each element aligns does the user feel confident enough to download.
1. App Icon — Your First 1 Second
Specifications
- App Store: 1024 × 1024 px (PNG or JPEG)
- Google Play: 512 × 512 px (PNG)
- Web: 180 × 180 px minimum
Icon Design Workflow in Figma
Step 1: Create the Foundation
- Create 1024 × 1024 px frame
- Define safe zone (center 660 × 660 px)
- Build silhouette from basic shapes (circles, squares, triangles)
Step 2: Choose Your Brand Color
Icon color should reflect these principles:
- Distinction: Not confused with competitor apps
- Visibility: Recognizable at small thumbnails
- Emotion: Resonates with target users
Example: Rork-Generated Apps
- Photo organization: Calm purple + white
- Health tracker: Fresh green + bright white
- Entertainment: Bold orange + dark navy
Step 3: Add Refinement
- Subtle gradients (depth perception)
- Soft shadows (3D effect)
- Detail touches (personality)
Step 4: Multi-Size Testing Test appearance at:
- 1024px (original)
- 180px (web)
- 40px (home screen)
Small-size readability is critical.
Icon Variations
Consider multiple versions:
- Base (universal, most versatile)
- Dark mode (iOS 15+ support)
- Language-specific (if text-based)
Manage all in one Figma file using Pages.
2. Screenshots — Tell Your Story in 5-8 Slides
The Three Principles
Principle 1: Narrative Flow
- Slide 1: What is this app? (emotional hook)
- Slides 2-3: Three main features (one per slide)
- Slides 4-5: Real-world use cases ("Perfect for...")
Principle 2: Text Minimalism ~70% visual, ~30% text. Heavy text fatigues users.
Principle 3: Visual Consistency Same background, fonts, and colors across all screenshots build brand recognition.
Figma + Canva Hybrid Approach (Recommended)
- Build template in Figma (background, text layout)
- Capture real app screenshots
- Layer screenshots into Figma template
- Use Canva for multi-language versions (fast text editing)
This balances quality and speed.
Copywriting Optimization
For maximum ASO impact:
- Slide 1 headline: Lead with benefit, not feature
- ✅ "Organize your memories in minutes"
- ❌ "A feature-rich app"
- Feature descriptions: Action verbs
- ✅ "AI auto-organizes"
- ❌ "Has organization"
- Use cases: Connect to user emotions
- ✅ "Relive your best travel memories"
- ❌ "Cloud storage included"
3. Feature Graphic — Store Promotional Asset
Specifications
- Google Play: 1200 × 500 px (landscape)
- Apple Featured: Auto-layout (logo + text)
Google Play uses feature graphics in store hero slots and promotional campaigns.
Fast Creation with Canva
- Search "Google Play feature graphic" template
- Add brand colors and headline
- Use AI image generation (e.g., "photo organization" → relevant imagery)
- Export
5-10 minutes for a professional result.
Design Principles
- Single message: One key benefit only
- High contrast: Text visibly distinct from background
- Imagery: Include relatable visuals or mascots (emotion)
4. Preview Video — Your Highest-Converting Asset
Specifications
- App Store: 15-30 seconds (15-30 fps, H.264)
- Google Play: Up to 30 seconds (MP4, H.264)
Fact: Apps with preview videos see 20-40% higher conversion rates than without.
Video Structure Patterns
Pattern A: Feature Demonstration
[0-3s] Opening (app name + tagline)
[3-12s] Demo three main features
[12-20s] Highlight benefits (speed, ease, safety)
[20-30s] Closing (download CTA)
Pattern B: Story-Driven
[0-5s] Show user's problem
[5-20s] App solves the problem
[20-30s] User satisfaction/happiness
AI Video Generation Tools
Canva Video Pro
- Ease: ⭐⭐⭐⭐⭐ (most intuitive)
- Templates: ⭐⭐⭐⭐⭐ (app-specific abundant)
- Customization: ⭐⭐⭐
Runway ML
- Ease: ⭐⭐⭐⭐
- AI Power: ⭐⭐⭐⭐⭐ (text-to-video)
- Customization: ⭐⭐⭐⭐
Synthesia
- Ease: ⭐⭐⭐⭐
- AI Power: ⭐⭐⭐⭐ (avatar videos)
- Customization: ⭐⭐⭐
Recommended Workflow
- Record your Rork app in action (device screen capture)
- Pick Canva Video template
- Insert recorded footage
- Add text, transitions, BGM
- Edit to 15-30 seconds
5. A/B Testing Strategy
Testing Framework
Each element can be tested:
- Screenshots (text, layout, visual tone)
- Video (presence, length)
- Icon (color variations)
Cycle: Change every 2 weeks, measure, choose winner.
Key Metrics
- Impressions: How many saw your listing
- Clicks: How many clicked through
- CTR: Clicks ÷ Impressions (your key metric)
- Installs: Actual conversions
- Uninstalls: Quality indicator (should be low)
Stores provide these automatically (App Store Analytics, Google Play Console).
Testing Example
Headline A: "Organize 1000+ photos in minutes" Headline B: "Make your memories beautiful"
Run each for 2 weeks. Measure CTR and installs. Choose the winner. Repeat.
6. Complete Rork Integration Workflow
For Rork-generated apps, follow this process:
[1] Rork generates app UI
↓
[2] Export to Figma, refine brand colors/fonts
↓
[3] Create icon (Figma)
↓
[4] Create screenshots (Figma + Canva)
↓
[5] Create preview video (Canva Video / Runway)
↓
[6] Upload to stores
↓
[7] After 2 weeks, analyze A/B test results
↓
[8] [If major revision needed]
Regenerate in Rork → Repeat from Step 2
7. Pre-Launch Verification Checklist
Visual Assets
- [ ] Icon: 1024px visible and clear
- [ ] Icon: Readable on dark backgrounds
- [ ] Screenshots: Correct dimensions (both platforms)
- [ ] Screenshots: All languages included
- [ ] Text: Spell-checked, grammar correct
- [ ] Video: 15-30 seconds exact
- [ ] Video: BGM copyright cleared
ASO Elements
- [ ] Keyword in app name (primary)
- [ ] Subtitle includes secondary keywords
- [ ] Slide 1: Immediately clear what app does
- [ ] Video: Enabled on both stores
- [ ] Feature graphic: Approved and uploaded
8. Continuous Improvement Cycle
Store launch is the beginning, not the end:
Monthly Review
- Check store analytics (CTR, installs)
- Read user reviews for improvement ideas
- Analyze competitor screenshots
Quarterly Updates
- Replace 1-2 screenshots with new designs
- Add new features to screenshots
- Update preview video to latest build
This ongoing cycle compounds—each update teaches you what resonates.
Complete Example: Photo Organization App
Imagine a photo app from Rork:
Icon:
- Purple gradient background
- Clean photo frame symbol
- Minimal, modern style
Screenshots:
- Slide 1: "Organize photos in minutes, beautifully"
- Slide 2: "Auto-detect and arrange by date"
- Slide 3: "Create albums with one tap"
- Slide 4: "Share memories securely with family"
- Slide 5: "Cloud backup never loses your photos"
Feature Graphic:
- "Turn Your Photo Collection Into Art"
- Background: Sample organized photo grid
- CTA: "Download Now"
Video:
- [0-2s] Cluttered photo gallery
- [2-8s] App automatically organizes by date
- [8-15s] User creates album and shares
- [15-20s] Cloud backup in progress
- [20-30s] Happy user reviewing organized photos
Result: Cohesive, compelling story. High conversion.
Summary
App store success comes from integrated visual strategy:
- Icon: Brand recognition and discovery
- Screenshots: Understanding and interest
- Feature graphic: Visibility in featured slots
- Video: Confidence and purchase decision
Rork + Figma + Canva toolchain enables professional creation and A/B testing in manageable time.
Key Takeaway: View these four assets not separately, but as one complete marketing funnel. Each reinforces the others. Together, they drive the downloads that make your app successful.
Start with solid templates, launch quickly, then iterate based on real store data. Continuous improvement compounds—your second update will be faster and higher-converting than your first.