| raw | raw/app-branding-masterclass.md |
|---|---|
| url |
TL;DR: Chris Raroque treats mascots as product UX, not cute decoration. A character gives users something to attach to, then becomes a repeatable visual system for icons, empty states, loading screens, and brand memory.
Biggest lessons
- Characters beat abstract logos. People attach to a named character faster than an abstract mark, especially in utility software that would otherwise feel generic.
- Original art is the style anchor. Chris starts with hand-drawn art, then uses AI to iterate from that base so the mascot does not collapse into the default AI-image look.
- Prompt slowly, not all at once. Big multi-change prompts can obey the instruction while destroying the style. Change one thing at a time, and restart a new chat when the direction drifts.
- Use the mascot throughout the product. The real payoff is not only the app icon; it is a library of state-specific illustrations for search, processing, loading, no-data screens, and other moments that usually feel dead.
- Name fast, but keep the category legible. Chris uses memorable names, but usually appends or pairs them with a category word. He is also comfortable renaming when the product direction changes.
Why it matters
- This source expands app-product-craft: brand is part of product feel, not a marketing layer pasted on top.
- It connects to product-led-growth because a distinctive mascot can make repeated product usage feel more personal.
- It also sharpens vibe-coding: AI image generation works best when the founder has a taste direction and decomposes the prompt.