People meet your product as a tiny icon on a crowded home screen, then as a store listing, then as the app itself. If those three moments look like different companies, trust drops before the product has a chance to prove itself.
Consistency is not pasting the full logo everywhere. It is a small set of decisions — mark, color, type, and tone — applied at the size and job of each surface.
The icon is a mark, not a brochure
An app icon is seen at a very small size, next to other icons, and often without your name if the label is truncated. It needs one recognizable shape. Fine lines, tiny words, and photographs of the full logo fail here. Test the icon at the actual size on a real phone, on both light and dark wallpapers, before you fall in love with the large version.
- One symbol. If you need a sentence to explain the icon, it is not done.
- Colors that still separate from common system icons around it.
- No text, unless the wordmark is the entire brand and still readable when tiny.
- A simplified version for notifications and favicons, drawn on purpose, not scaled blindly.
Carry the same decisions into the product
Inside the app, the brand should support the task. Use the brand color for primary actions and status, not for every surface. Pick a type family that is readable at interface sizes. If the display face used on the website is too loud for a form, use it for headings only and pair it with a quieter text face. That is still one brand.
A consistency pass we run before launch
- Place the icon, the store screenshot, and the first in-app screen side by side.
- Check that the primary color matches, including the pressed and disabled states.
- Read the store subtitle and the in-app empty state out loud. The voice should match.
- Confirm the wordmark, the short name, and the legal name are used in the right places.
- Export the icon sizes the stores actually require, from the source file, not from a screenshot.
The icon promises a product. The first screen has to be that product, in the same voice.
Store screenshots are brand, too
Screenshots are often designed like ads and then show a UI the build does not contain. Use real screens, with real copy, and a caption that states the benefit in the same language as the app. Decorative backgrounds are fine. Fake buttons are not. Reviewers and customers both notice the gap.
What to hand the next designer
Source files, the icon set, color values, type rules, and examples of correct and incorrect use. A PDF logo on a white square is not a system. The next feature will be designed by someone in a hurry. Make the correct choice the easy one.
Leave a Reply
Your email address will not be published. Required fields are marked *
More from the studio
Comments(00)
No comments yet. Be the first to join the conversation.