THE BEST APP ICON MAY NOT EXPLAIN THE PRODUCT. It may trigger the next open. Same pet app. Two behavioral cues. 🐾 A creates instant recognition. The brain connects the icon with the pet before processing a feature or task. 📅 B creates functional context. It signals there is something to remember, check or manage. Both work, but for different parts of retention Recognition builds familiarity. Context creates a reason to return. The real growth question: Which cue is stronger once the user already understands the product? 🐾 A Emotional recognition 📅 B Functional intent 👇 Which one would make you reopen the app? 👉 BOOK A MOBILE APP STRATEGY SESSION https://calendly.com/asol_design/book-diagnostic-call-linkedin-clone

I think B is the better option, though it could use a little more contrast. A feels too generic, if my Paws & Palms became an app, its icon could end up looking very similar to A and get confused with other apps. Something more unique and instantly identifiable would help it stand out.

Icons → tokens → components → screens. In that order, on purpose.

On an eIDAS-compliant signature platform, I built the design system in a strict sequence — each layer constraining the one above it.

Tokens came in three layers: global (primitive values), alias (intent — surface.primary, border.subtle), component (button.primary.background).

The separation did real work: globals could change without touching components; aliases let one primitive serve different intents across light and dark.

The test came later, when the team grew: other designers changed some of my decisions — and the token architecture absorbed the changes without breaking.

A system that can't be changed isn't a system. It's a style guide.