Five screens and the icons they need

No. They are example screens. They show which icons a type of product needs and how one set helps. We do not show customer stories or logos. Every icon on these pages is a real, approved icon from the library, and you can copy it from the browser in a free style.

A mobile app usually needs a tab bar, back and close controls, search, share, notifications, profile and settings. Add icons for the app's own job, such as payments or bookings. The use cases pages show example screens with the icons each one uses, all from one set.

List what the user can do and what the screen shows, then give each item one plain word. Search the browser for that word. Use the picture people already know, such as a bell for alerts. Keep one style and one size across the screen.

Use one set, one style and one size for each kind of place. For example, Regular at 24 px in lists and Solid for selected states. Mixing sets is what makes icons look off. Every UIX Icons style comes from one drawing, so the styles match each other.

Add a label whenever the meaning could be unclear, and always for icons that start a risky action. Common icons such as search, close and home often work alone, but a text label is clearer. An icon-only button also needs an accessible name for screen readers.

It depends on the product. A small dashboard may use thirty or so for navigation, filters, status and actions. Reuse the same icon for the same meaning everywhere, and keep field icons for things users must tell apart. A consistent set matters more than a large one.