app-icon-optimization
When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon refresh", or wants to know what makes a good app icon. For screenshot optimization, see screenshot-optimization. For full listing A/B tests, see ab-test-store-listing.
Best use case
app-icon-optimization is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon refresh", or wants to know what makes a good app icon. For screenshot optimization, see screenshot-optimization. For full listing A/B tests, see ab-test-store-listing.
Teams using app-icon-optimization should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/app-icon-optimization/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How app-icon-optimization Compares
| Feature / Agent | app-icon-optimization | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon refresh", or wants to know what makes a good app icon. For screenshot optimization, see screenshot-optimization. For full listing A/B tests, see ab-test-store-listing.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# App Icon Optimization You help design, audit, and A/B test app icons to maximize tap-through rate (TTR) — the percentage of users who tap your app after seeing it in search results or browse. ## Why the Icon Is Your Most Impactful Asset The icon is the **first thing users see** in search results — before the title, rating, or screenshots. A compelling icon can lift TTR by 20–40% with no other changes. In browse/charts, it's often the only visual element competing for attention. ## Icon Design Principles ### 1. Simplicity at Small Size Icons render at 60×60pt (iPhone search results). At that size, detail disappears. - Maximum 2 elements - No text (illegible at small sizes; Apple discourages it) - Strong silhouette recognizable at a glance - Test at 60×60px before finalizing ### 2. Color Contrast Against the App Store Background The App Store has a white/light background (light mode) and dark background (dark mode). - High contrast on both modes - Avoid white icons — they disappear in light mode - Avoid very dark icons — they disappear in dark mode - Consider adding a subtle shadow or border on your icon background ### 3. Category Visual Language Match and differentiate from your category norms: | Category | Common patterns | How to stand out | |----------|----------------|-----------------| | Productivity | Blue, clean, minimal | Warmer colors, bolder marks | | Health/Fitness | Green, orange, energetic | Premium dark, sophisticated | | Finance | Blue, green, conservative | Bold, distinctive mark | | Games | Bright, characters, action | Premium/dark if competitors are loud | | Social | Round shapes, soft colors | Sharp, distinctive if feed is soft | | Meditation | Purple, blue, calm | Unexpected contrast color | | Photo/Video | Gradient, camera | Single strong mark | **Rule:** Look at your top 20 competitors' icons. Then design to be immediately distinguishable. ### 4. Recognizable Mark The icon needs a single, memorable mark — not a scene or a composition. Ask: > "Can someone describe this icon in 3 words?" - ✅ "Red speech bubble" | ❌ "Someone using a phone with a gradient" - ✅ "Bold orange flame" | ❌ "Abstract colorful shapes" ### 5. Brand Consistency The icon is your brand mark in the App Store. It should: - Match your app's primary color palette - Be consistent with your splash screen, push notifications, and marketing - Work as a favicon, social media avatar, and press kit asset ## Icon Sizes Required | Platform | Size | |----------|------| | iPhone (App Store) | 1024×1024px (master) | | iPhone (home screen) | 60×60pt @1x, @2x, @3x | | iPad | 76×76pt @1x, @2x | | Watch | 40×40pt – 44×44pt | | Android adaptive icon | 108×108dp (safe zone 66×66dp) | Submit a single 1024×1024px PNG (no transparency, no rounded corners — Apple applies the mask). ## A/B Testing Icons ### iOS — Product Page Optimization 1. App Store Connect → Your App → Product Page Optimization → Create Test 2. Create up to 3 icon variants 3. Set traffic allocation (20–33% per variant) 4. Run for minimum 7 days or until statistical significance **Access:** App Store Connect → App Store → Product Page Optimization ### Android — Play Store Experiments 1. Play Console → Store listing experiments → New experiment 2. Upload up to 3 icon variants 3. Set traffic split 4. Google reports install conversion rate per variant ### What to Test Test one variable at a time: | Test | Variants | |------|---------| | Color scheme | Same mark, 3 different background colors | | Mark style | Flat vs illustrated vs 3D | | Dark vs light | Dark background vs light background | | Character vs abstract | Character-based vs geometric/abstract | | With vs without text | Mark only vs mark + short text | ### Reading Results - **Primary metric:** Install conversion rate (impressions → installs) - **Minimum sample:** 1,000+ impressions per variant for reliable signal - **Significance threshold:** p < 0.05 or Appeeky/Play Console confidence indicator ## Icon Audit Evaluate your current icon against: ``` Clarity at 60×60px: [1–10] - Recognizable mark at small size? - No illegible text? Color contrast: [1–10] - Works on white (light mode)? - Works on dark backgrounds (dark mode)? Category differentiation: [1–10] - Stands out from top 10 competitor icons? Simplicity: [1–10] - Max 2 elements? - Describable in 3 words? Brand alignment: [1–10] - Consistent with app's visual identity? Overall: [N]/50 ``` ## Brief for Icon Designer When briefing a designer: ``` App: [name and one-line description] Category: [category] Primary audience: [who uses it] Brand colors: [hex values] Mood/feeling: [premium / playful / trustworthy / energetic / calm] What the icon should convey: [core value or identity] What to avoid: [don't replicate competitor X, avoid Y] Competitors to differentiate from: [list 3–5 with icons] Reference icons I like: [list 3–5 from other apps] Deliverables: - 3 distinct concepts at 1024×1024px - Each concept tested at 60×60px mockup in App Store search context - Final: PNG, no alpha, no rounded corners ``` ## Related Skills - `ab-test-store-listing` — Full A/B testing methodology - `screenshot-optimization` — Complement the icon with strong screenshots - `android-aso` — Android adaptive icon requirements - `aso-audit` — Icon is one factor in the full ASO score
Related Skills
screenshot-optimization
When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.
retention-optimization
When the user wants to reduce churn, improve user engagement, or increase lifetime value. Also use when the user mentions "retention", "churn", "users leaving", "engagement", "DAU/MAU", "user activation", or "why are users uninstalling". For onboarding-specific issues, see app-launch. For monetization, see monetization-strategy.
onboarding-optimization
When the user wants to improve their app's onboarding experience, increase activation rate, reduce Day 1 drop-off, or optimize the first-run flow. Use when the user mentions "onboarding", "first-run", "activation", "tutorial", "day 1 retention", "new user flow", "permission prompts", "sign-up conversion", "onboarding funnel", or "users dropping off early". For overall retention strategy, see retention-optimization. For paywall placement, see monetization-strategy.
metadata-optimization
When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.
ua-campaign
When the user wants to plan or optimize paid user acquisition campaigns. Also use when the user mentions "Apple Search Ads", "user acquisition", "paid ads", "UA", "ad campaign", "install campaign", "Facebook ads for apps", "TikTok ads", or "cost per install". For organic growth, see aso-audit. For launch-specific UA, see app-launch.
subscription-lifecycle
When the user wants to optimize their subscription business end-to-end — from trial start through renewal, cancellation, and win-back. Use when the user mentions "subscription lifecycle", "trial conversion", "churn", "cancellation", "win-back", "lapsed subscribers", "dunning", "billing retry", "grace period", "renewal rate", "subscriber LTV", or "resubscribe". For paywall design and pricing strategy, see monetization-strategy. For subscription analytics dashboards, see app-analytics.
seasonal-aso
When the user wants to optimize their App Store listing for seasonal events, holidays, or trending moments — including keyword opportunities, metadata updates, screenshot theming, and timing strategy. Use when the user mentions "seasonal", "holiday", "Christmas", "New Year", "Valentine's Day", "summer", "back to school", "seasonal keywords", "trending now", "limited time", or wants to capitalize on a calendar event. For general keyword research, see keyword-research. For full metadata rewrites, see metadata-optimization.
review-management
When the user wants to analyze, respond to, or improve their app reviews and ratings. Also use when the user mentions "reviews", "ratings", "negative reviews", "how to get more reviews", "review response", or "my rating is dropping". For broader ASO audit, see aso-audit. For retention issues causing bad reviews, see retention-optimization.
rating-prompt-strategy
When the user wants to improve their app's star rating, increase ratings volume, optimize when and how they prompt users for a review, or recover from a bad rating period. Use when the user mentions "app rating", "star rating", "review prompt", "SKStoreReviewRequest", "In-App Review API", "ask for review", "low rating", "rating drop", "get more reviews", or "recover from 1-star". For responding to reviews, see review-management. For overall ASO health, see aso-audit.
press-and-pr
When the user wants to get press coverage, media mentions, or editorial features for their app — including writing press releases, pitching journalists, getting on "best apps" lists, or building an app press kit. Use when the user mentions "press", "PR", "media coverage", "TechCrunch", "journalist", "press release", "app press kit", "get featured in media", "editorial coverage", "review from a blogger", or "app launch announcement". For Apple editorial featuring, see app-store-featured. For launch strategy, see app-launch.
monetization-strategy
When the user wants to design or optimize their app's monetization — pricing, paywalls, subscriptions, or in-app purchases. Also use when the user mentions "pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", or "conversion to paid". For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.
market-pulse
When the user wants a comprehensive App Store market overview, daily/weekly market briefing, or combined view of chart movements, trending keywords, featured apps, and new releases. Also use when the user mentions "market overview", "what's happening on the App Store", "market briefing", "weekly report", "market trends", or "state of the market". For chart-specific rank changes only, see market-movers. For keyword trends only, see keyword-research.