Affinidi identity apps on four iPhones
Selected work
Nº 04 · Case study
Affinidi

A design system for Affinidi's identity apps.

  • Design system
  • Design leadership
  • Responsive design
  • UX/UI
  • Web 3.0
Company
Affinidi
Role
Lead Product Designer
Year
2022 – 2023
Team
3 designers, 1 PM

01 · Brief

Multiple product teams had spent years on what was supposed to be one product. Each had drifted into its own visual language. We built one design system to pull them together under a single developer console. It took about six months, in 2022 and 2023.

02 · Outcome

The design system was adopted across 3 product teams. It was also the foundation for 4 white-label credential applications. Design-to-dev handover went from weeks to days.

03 · What I did

What I did.

As Lead Product Designer, I was the link between the Berlin and Singapore teams. I had worked on most of these products at some point. I could see exactly where the experiences had fragmented.

I led the team in designing and building the design system’s components, using atomic design. I managed the handover to the developers building out the system. I also owned the final product: the developer console that brought everything together.

04 · Key decisions

Key decisions.

  1. Atomic design from the start

    We had 4 products and hundreds of misaligned components. Starting at the atom level meant any future product could compose from the same building blocks instead of duplicating them. It also gave us a shared vocabulary across the Berlin and Singapore teams.

    Four Affinidi apps on iPhones
    Multiple products with one system underneath
  2. White-label as the proof of concept

    To me, the test of a design system is whether it can adapt without forking. So we duplicated ours and swapped the style guide. We used the copy to build new branded applications in a fraction of the original time. The architecture held up.

05 · The system

Building a design system for Affinidi's privacy-preserving applications.

A design system gives every team the same reusable components and guidelines. That way all platforms and products look and feel consistent. It also makes products faster to build and easier to scale.

Design and development get simpler, with less duplicate work and fewer errors. Teams also find it easier to work together.

With a design system in place, organisations can try new ideas sooner and ship what users need and expect.

06 · Atomic design

Atomic design.

For our design system we used atomic design, a method with five stages that work together. It lets you build an interface design system in a more deliberate, hierarchical way. The stages are atoms, molecules, organisms, templates and pages.

Style guide

The style guide below was the foundation of our design system. Most elements were already defined, and we added more as we needed them.

The Affinidi style guide: brand, utility and neutral colours, text styles and icons
01 / 05

Atoms

Atoms are the most basic components, the building blocks of a design system. They include buttons, lines, shapes, icons, text fields, text labels and so on. Here are some of the atoms we used.

Message atoms: info, warning, error and success
Messages
Input and select atoms: text fields, a pin input, dropdowns, a search field, checkboxes, toggles and radio buttons
Inputs and selects
02 / 05

Molecules

Molecules combine two or more atoms. An input field and a button, for instance, can combine into a search form. Below are some of the molecules from our design system.

Molecules: an attribute form, a project card, an upload field, a schema card and a drawer
03 / 05

Organisms

Several molecules together form an organism, like a header, sidebar or signup form.

The console header with its project switcher open
Header
The console sidebar navigation
Sidebar
A nested attribute form
Form
04 / 05

Templates

Templates are the glue that combines organisms or individual sections into a complete design.

A page template with a headline
01 / 03
A page template with a drawer
02 / 03
A page template with tabs
03 / 03
05 / 05

Pages

The highest level in an atomic design system is the actual pages that make up a product. Below is a selection of the pages of our developer console.

  1. Developer console page: log in
    01 / 06
  2. Developer console page: my projects
    02 / 06
  3. Developer console page: bulk issuance
    03 / 06
  4. Developer console page: analytics
    04 / 06
  5. Developer console page: schema manager
    05 / 06
  6. Developer console page: qualification criteria
    06 / 06
07 · Final designs

Final designs.

Affinidi developer console
Final design 01

Developer console

We first built the design system for the developer console. The console gives Affinidi’s customers tools to improve data privacy and portability in their own apps. The primary application built on the design system
White-label credential applications across four phones
Final design 02 White-label credential apps: the same system with a different brand, built in a fraction of the time The design system was flexible enough to reuse in other applications. We duplicated it and updated the style guide to give each new application its own look and feel.

Next project

Selected work