About 16 minutes reading · 29 minutes practice
You will produce: An icon concept pack with hypotheses, constraints and evaluation requirements.
Treat the icon as identity
An icon must remain recognizable across the store and the installed product experience. Consider shape, contrast and distinctiveness at small size, but avoid turning it into a compressed screenshot or promotional billboard. Record brand and product constraints before exploring alternatives. A conversion-oriented change still has consequences for existing users trying to recognize the app.
Make alternatives strategically different
Changing a tiny decorative detail may be difficult to interpret and may not address the audience problem. Define the hypothesis: perhaps the current mountain symbol suggests navigation while a journal cue better communicates the product. Keep the comparison truthful and within current platform rules. Do not borrow another app’s recognizable identity merely because it performs well in your research set.
Plan implementation and evaluation together
Store icon experiments can have platform-specific requirements and product-release dependencies. Confirm what is supported before promising a quick test. Keep source files, export versions and implementation instructions. Evaluate recognition and technical acceptance separately from conversion, and record the possible effect on returning users rather than assuming all traffic is unfamiliar with the brand.
Quick check · pick a response
Make the call before you scroll.
Go deeper: practical decisions and tradeoffs
Define the recognition task
An icon needs to identify the app at small sizes and in a competitive environment. Start with the product category, brand constraints and the recognition problem you want to investigate. A journal symbol may communicate recording; a map pin may imply navigation. Decide which association is useful before drawing variants. Avoid treating a personally preferred illustration as strategy. The concept should connect to a supported product meaning and remain recognizable when shown beside other icons.
Vary concepts deliberately
Create alternatives around a clear idea such as a simplified journal mark versus a more expressive memory symbol. Keep notes on what changes and why. Review silhouette, contrast, detail and distinction at actual size. Do not copy a competitor's mark or use badges that imply unsupported status. A family of variants that changes shape, color and symbolism together is a package comparison; you cannot later identify which component caused the result without further investigation.
Check implementation before planning a test
Store-specific icon testing and submission requirements may depend on app configuration or included assets. Verify current platform guidance and coordinate with engineering before promising a quick test. Keep the production icon, alternate files and their identifiers unambiguous. Record the audience, primary measure and guardrails if experimentation is appropriate. An icon preference survey can inform recognition and interpretation, but it does not directly measure store acquisition performance.
Platform references for this work: Apple — Product page optimization overview · Google Play — Metadata policy
Your turn · two-minute exercise
Try the scenario. Make your case.
A team prefers a map icon because it looks more outdoorsy. Explain how to evaluate whether that association helps a hiking journal or creates an unsupported navigation promise.
Autosaved on this browser. Your work is private and does not sync between devices.
Your step-by-step procedure
Document the current icon’s identity role and suspected misunderstanding.
Create two clearly differentiated concepts with written hypotheses.
Review small-size recognition, brand consistency and current platform requirements.
Choose a feasible evaluation method and record implementation dependencies.
Completed example · use the reasoning
Three icon hypotheses
Gabriel’s take: An icon is not a competition to fit the most tiny objects into a square.
Constructed teaching material, not a client result. Adapt the evidence and product facts before using it for your app.
Read the complete example record
Journal: Page and bookmark → recording memories
Photo: Photo inside a page → visual journal, risk of photo-editor confusion
Map pin: Location cue → risk of navigation expectation
Next step: Compare recognition at small size before a native experiment.
Your turn · repair the decision
Make the call. Then compare.
Choose the first two concepts to review and name the misleading interpretation to watch.
Autosaved on this browser. Your work is private and does not sync between devices.
Explore the supporting case and interpretation
Trail Notes compares a mountain-outline concept with a journal-page concept. Both retain the approved color family and app identity. The question is whether the journal cue better communicates the use case, not whether one color magically improves ranking. A small recognition review precedes any store experiment, and the technical owner checks the platform’s icon-test setup before scheduling work.
Concept: Journal mark
Association to inspect: Recording and memories
Risk: May be too generic
Concept: Photo-memory symbol
Association to inspect: Personal visual record
Risk: May imply photo editing
Concept: Map pin
Association to inspect: Location and navigation
Risk: Wrong expectation for this app
The concept review asks what viewers infer, not which shape the team likes most. The map-pin direction could be visually striking yet unsuitable if it reinforces the navigation misunderstanding. The other concepts also need evidence: a photo symbol might shift the app into a different perceived category. Use those interpretations to refine the shortlist before investing in a full test and release pack.
Build a handover someone can use
Concept brief
Name the recognition problem, supported associations and brand constraints.
Variant set
Provide exact files and explain the intended difference between concepts.
Small-size review
Record recognizability, contrast and misleading associations in the actual context.
Technical readiness
Confirm required app configuration and platform-specific test or release steps.
Decision plan
Separate comprehension findings from experiment results and retain the approved production asset.
Your ASO assignment
Use your own app and evidence, or work through the teaching case. Keep your observations separate from assumptions and explain the reasoning behind your decisions.
Build something · track your work
Your assignment checklist
Tick each item after you have produced the work. Reading it does not count. The strategy deck will survive.
0 of 3 tasks checked.
Autosaved on this browser. Your work is private and does not sync between devices. Course completion is recorded separately.
Assess your work
- Alternatives represent a meaningful communication difference.
- Product identity and ownership constraints are respected.
- The proposed test is technically feasible for the selected platform.
Common mistakes to catch
- Claiming a particular icon color universally converts best.
- Ignoring the release requirements of an icon experiment.
Sources and further reading
Platform references reviewed 29 September 2026. These sources support platform capabilities and constraints; the teaching frameworks, assignments and illustrative cases are original course material.
- Apple — Product page optimization overview — Supported experiment assets, eligibility and setup.
- Google Play — Metadata policy — Accurate, relevant metadata and prohibited presentation.
Your ASO lesson notes
Use this space for your assignment, evidence and handover. Your notes save automatically in this browser. Download a copy to take with you.
Notes stay on this device and are not submitted to ASO Agency.
Complete your assignment with the ASO experiment planner.
Loading your progress…
Progress is saved only in this browser. It does not sync across devices. Mark a lesson complete after doing its exercise.