Your app icon has to work when it is small. Start with one recognizable shape, give it enough contrast and check it beside other apps. Fine details can wait until the basic design is clear.
This guide covers the design process, the differences between store and launcher assets, and a practical way to test a new icon. Use it alongside your screenshot design work so the listing feels like one product.
Where people will see your icon
People may encounter your icon in search results before they know anything about your app. After installation, they need to recognize it among the apps on their home screen. A distinctive silhouette and consistent colors help with both jobs.
Look at the icon beside the app name, then look at it on its own. The name can explain the product; the icon needs to be easy to recognize. It does not have to illustrate every feature.
Treat the icon as one part of your listing review. If the screenshots show an outdated interface or the description is unclear, changing the icon alone will leave those problems in place.
iOS and Android icon requirements
Prepare the right asset for each destination. A Google Play listing icon and an Android launcher icon are separate files with different specifications. Apple also supports a layered icon workflow, so a single flat PNG is no longer a complete description of every Apple icon.
| Destination | What to prepare | What to check |
|---|---|---|
| Apple app, using an asset catalog | A 1024 × 1024 source image and the appearances required by your project | Use Xcode's asset catalog settings and validate the resulting app. |
| Apple app, using Icon Composer | A layered icon file added to the Xcode project | Preview the supported appearances in Icon Composer and on a device. |
| Google Play listing | A 512 × 512, 32-bit PNG in sRGB, no larger than 1024 KB | Supply square artwork without an outer shadow or pre-rounded corners. |
| Android launcher | Foreground and background layers, plus a monochrome layer for theming | Use 108 × 108 dp layers and keep essential artwork within the central 66 × 66 dp area. |
Apple explains the two workflows in its asset catalog guide and Icon Composer guide. Google documents the Play listing asset separately from adaptive launcher icons. Check those references when exporting, especially if your app supports more device families.
Apple: check the appearance, not just the source file
Use the current Apple icon guidance for your chosen workflow. Transparency rules depend on the asset and appearance. Avoid applying an old “no alpha anywhere” instruction to every layer of a modern icon.
Keep the design clear in default, dark, tinted and clear appearances where supported. Thin highlights and low-contrast details can disappear when the appearance changes. Preview the final result in the tools and OS versions you support.
Android: separate store artwork from launcher layers
Google Play applies the listing icon's outer mask and shadow. Android launchers apply their own masks to adaptive icons. Preview both; a design that looks fine in the store can still lose part of its symbol on a circular launcher mask.
Google's icon policy prohibits misleading ranking, deal and install-promotion elements. That is more specific than a blanket ban on all text. A simple lettermark and a “#1” badge serve different purposes; avoid promotional badges and check the policy before adding copy.
Design your icon in seven steps
1. Choose one idea
Write down the app's main task and sketch a few symbols that could represent it. A receipt app might use a folded paper shape; a walking app might use a path. These are starting ideas, not rules for every app in the category.
If you already have a recognizable brand mark, begin there. You may only need to simplify its detail or adjust its placement for the smaller space.
2. Choose colors in context
Place the drafts beside actual search results for your app's main terms. Notice which colors and shapes blend into the surrounding icons. Try an alternative that remains consistent with your product.
Start with a small palette and enough contrast between the symbol and background. Check light and dark wallpapers before committing to subtle tones.
3. Compare rough designs at small sizes
Keep several simple sketches instead of polishing the first idea. Compare their silhouettes at roughly 60 pixels wide, then inspect smaller and larger previews. That size is a useful design check, not a universal display specification.
Ask someone unfamiliar with the app what they notice and whether they can tell the drafts apart. Listen for confusion about the shape or category. You are looking for a clear design direction, not treating a few opinions as a conversion test.
4. Build an editable master
Use a vector or layered source so you can adjust the symbol, spacing and colors independently. Keep the source file separate from store exports. Name versions clearly so an experiment does not overwrite your current icon.
Create the destination assets from this master using the platform guidance above. Do not package a 512-pixel Play listing image as though it were a complete Android adaptive icon.
5. Check the places the icon appears
- Store search: view it beside your app name and nearby results.
- Home screen: place it among other apps on both light and dark backgrounds.
- System appearances: inspect the supported Apple appearances and Android themed version.
- Masks: make sure the main symbol survives the relevant platform shapes.
Notification artwork may have its own requirements. Use the platform's notification asset guidance instead of assuming the full-color launcher icon can be reused everywhere.
6. Export and validate
Keep separate exports for each store and platform workflow. Confirm the file dimensions, color space and size, then inspect the uploaded preview or installed build. Open the final files yourself; a correctly named file can still contain an older draft.
When optimizing file size, check the edges afterward. Compression should not leave visible halos around a simple symbol.
7. Review the whole listing
Place the icon next to the screenshots, title and description. Reuse enough of the visual identity to make the product recognizable, while giving each asset room to do its own job.
Our screenshot size guide covers the companion artwork. AppDrift's screenshot editor helps prepare that gallery; create and validate the icon in a tool suited to the platform's icon files.
Which design styles are worth trying?
Choose a style that suits the app and remains legible. These directions are design options, not a ranking of what converts best in 2026.
- A single bold symbol: useful when a distinctive outline carries the identity.
- A restrained gradient: can add depth without competing with the foreground.
- A layered material: can work when the platform supplies lighting and appearance effects.
Apple's Icon Composer provides a way to prepare layered artwork for Liquid Glass. The design language arrived with iOS 26, not iOS 18. Follow the current tool previews rather than baking a generic glass effect into every icon.
How to test a new icon
Start with a reason for the change. Perhaps the symbol is hard to recognize on a dark background, or too similar to another app in search. Design one alternative that addresses that problem and keep the current icon as the control.
Apple's Product Page Optimization supports up to three treatments. Alternate icons must be included in the published app binary. Google provides Store Listing Experiments for testing listing assets.
Check the audience, traffic and uncertainty in the experiment report before choosing a version. A fixed number of days does not guarantee a clear answer. If the result is inconclusive, keep that finding instead of selecting a winner from a small difference.
Changing the symbol and color together can test the complete design, but it will not tell you which part made the difference. Choose the scope based on the question you want to answer. For a broader diagnosis, see our guide to planning a download-growth target.
Common mistakes to catch before export
- Tiny lettering: simplify copy that disappears at normal display size.
- Too much detail: remove secondary elements that make the silhouette hard to read.
- Clipped artwork: check the launcher masks as well as the square source.
- Weak dark-mode contrast: inspect the appearance on a device, not only in the design file.
- A near-copy of another app: change the concept enough to establish your own identity.
- The wrong export: verify the final file and app build against the intended destination.
Choose tools for the files you need
An editable design tool such as Figma, Sketch or Illustrator can hold the master artwork. Use the platform tools to inspect the final assets: Icon Composer or Xcode for Apple, and Android Studio's icon tools for Android. To produce the export set from one square master — an Xcode AppIcon set without an alpha channel, Android adaptive icons, the 512 px Play icon and Expo assets — the free app icon generator runs in your browser; validate its output in those tools. Check current licensing and supported formats before moving a project.
If you also design screenshot layouts in Figma, review the AppDrift Figma workflow. You can prepare the rest of the listing through AppDrift, including metadata drafts. Those drafts still need your review.
Finish with one icon you can recognize at a glance, valid exports for the platforms you support, and a saved source file for future changes. Then review the screenshot tools if the rest of the gallery needs attention.
Frequently asked questions
What is the difference between a Play store icon and an Android launcher icon?
The Google Play listing uses its own 512 by 512 PNG icon. Android adaptive launcher icons use foreground and background layers and are masked by the device. Follow the current specification for each asset.
Does changing an icon guarantee higher conversion?
No. Create a meaningful alternative and use the native store experiment results, including audience and uncertainty. A design trend is not evidence of a conversion increase.
