agentleFS
EronredEronred/aso-skills/skills/app-icon-optimization/SKILL.md

app-icon-optimization

Skill2.2k starsChanged 9 months agoMITView on GitHub

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.

1 other project uses a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Eronred/aso-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about Eronred/aso-skills

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No text (illegible at small sizes.

    line 23
  2. Distinctive:

    Test at 60×60px before finalizing

    line 25
  3. Distinctive:

    Avoid white icons — they disappear in light mode

    line 32
  4. Distinctive:

    Avoid very dark icons — they disappear in dark mode

    line 33
  5. Distinctive:

    Consider adding a subtle shadow or border on your icon background

    line 34
  6. Distinctive:

    Rule: Look at your top 20 competitors' icons.

    line 50
  7. Distinctive:

    Create up to 3 icon variants

    line 85
  8. Distinctive:

    Run for minimum 7 days or until statistical significance

    line 87
  9. Distinctive:

    Test one variable at a time:

    line 100
  10. Distinctive:

    When briefing a designer:

    line 144

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

CategoryCommon patternsHow to stand out
ProductivityBlue, clean, minimalWarmer colors, bolder marks
Health/FitnessGreen, orange, energeticPremium dark, sophisticated
FinanceBlue, green, conservativeBold, distinctive mark
GamesBright, characters, actionPremium/dark if competitors are loud
SocialRound shapes, soft colorsSharp, distinctive if feed is soft
MeditationPurple, blue, calmUnexpected contrast color
Photo/VideoGradient, cameraSingle 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

PlatformSize
iPhone (App Store)1024×1024px (master)
iPhone (home screen)60×60pt @1x, @2x, @3x
iPad76×76pt @1x, @2x
Watch40×40pt – 44×44pt
Android adaptive icon108×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:

TestVariants
Color schemeSame mark, 3 different background colors
Mark styleFlat vs illustrated vs 3D
Dark vs lightDark background vs light background
Character vs abstractCharacter-based vs geometric/abstract
With vs without textMark 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.