icon set design

icon set design

icon set design

icon set design

Category

Design System

Category

Design System

Category

Design System

Category

Design System

Year

2022

Year

2022

Year

2022

Every Design System
Needs an Icon Set

Every Design System
Needs an Icon Set

Every Design System
Needs an Icon Set

About Project

Every Design System needs an icon set as part of its ecosystem, so I delved into creating a set of over 600 icons that were designed and componentized to be used across multiple products.

Used by

Every Orbita's
Component

16+ Designers

30+ Developers

Content

+600 Icons

3 Size Variants

Guidelines

Based in

Figma

Frontend Repo

Duration

4 weeks

The Challenge

The Challenge

One of my first tasks on the team was to create a unified icon library for all of our products, as each product was using a different morphological and semantic style for its icons.

One of my first tasks on the team was to create a unified icon library for all of our products, as each product was using a different morphological and semantic style for its icons.

The first thing I did was to map out the current state of the icons at a high level. I found that not only did the icons not match between different products, but there were also inconsistencies in line weight and complexity within the same products. This was due to a mix of multiple icon libraries being used.

The first thing I did was to map out the current state of the icons at a high level. I found that not only did the icons not match between different products, but there were also inconsistencies in line weight and complexity within the same products. This was due to a mix of multiple icon libraries being used.

The Approach

The Approach

I started by compiling a list of the icons already being used in various product sections. This was the most extensive task, as we're talking about countless icons. The goal of this step was to not leave any use cases out of the new library, which would have forced designers to continue using the old library.

I started by compiling a list of the icons already being used in various product sections. This was the most extensive task, as we're talking about countless icons. The goal of this step was to not leave any use cases out of the new library, which would have forced designers to continue using the old library.

Once I had the mapping of the required icons, I did an extensive search for the best free icon libraries on the market. My goal was to have a basic set of editable icons that I could adapt to our needs, thereby avoiding the manual work of creating each icon from scratch. Once I found the set, I made sure the visual language aligned with the visual north star we were aiming for with the product.

Componentization

Componentization

Now for the fun part. I componentized the icons and generated size variables.

  • 16px: The smallest size, used for lower-hierarchy elements that serve as accompaniments.

  • 24px: The size generally used within components. This is the default size from the library, as it's the most commonly used.

  • 32px: This size is typically used as ornamentation in designs with iconography, such as cards or feedback screens.

Then, I grouped all the components into different categories based on the previous survey, and went to validate them with other designers. While Figma has an icon search, we need to ensure the icons are grouped into self-explanatory categories to make manual searches efficient.

Then, I grouped all the components into different categories based on the previous survey, and went to validate them with other designers. While Figma has an icon search, we need to ensure the icons are grouped into self-explanatory categories to make manual searches efficient.

Icons Across the Mirror

Icons Across the Mirror

With the categories validated, I put together an Excel file with the SVG files for the development team. They would take the icon library to the frontend repository to make it available in code.

With the categories validated, I put together an Excel file with the SVG files for the development team. They would take the icon library to the frontend repository to make it available in code.

Icon Guidelines

Icon Guidelines

As an added bonus, I also created the documentation used to generate new icons as needed. It has a detailed description of the approval criteria for adding an icon, the technical specs, a base grid, and basic shapes to use as references.

As an added bonus, I also created the documentation used to generate new icons as needed. It has a detailed description of the approval criteria for adding an icon, the technical specs, a base grid, and basic shapes to use as references.

Results & impacts

Results & impacts

  • This library was used to build all the components of the Orbita Design System, and continues to be used today.

  • It improved the visual quality of the products by unifying the style and morphology of the icons used.

  • It improved the findability of icons in the Figma library.

  • It helped define an organized handoff to the development team.