INDONESIA | 07:12 GMT+7
← Works

Case studyProduct

Designing Mobile Components for Privy’s Persona Design System

Brand
Privy · Persona
Discipline
Design system · Mobile UI
Timeline
2022–2024
Tools
Figma
Persona typography and colours: DM Sans, brand red, accent blue, and neutral tokensTwo phones showing a payment method screen and an e-stamp top-up screen built with Persona components

Persona is Privy’s open-source design system. As one of its designers, I focused on the mobile platform: designing responsive components that engineers built into the shared library.

89components

In the open-source Persona library

2colour modes

Light and dark, from one set of semantic tokens

11+components

Designed by me for the mobile platform, most now in the code library

Making a shared system work on small screens

Persona is the design system behind Privy’s products. As more of those products moved to mobile, components needed more than a smaller size: they needed patterns built for thumbs, short sessions, and one-handed use.

Problem
Desktop-first components did not always translate to mobile screens.
Need
Responsive components with clear mobile patterns that every product team could reuse.
Goal
A consistent mobile experience across Privy products, built on the same tokens as the web.

Designing for the mobile platform

I was one of several designers on Persona. My focus was the mobile platform, so most of my work was responsive components for small screens.

Team
5 designers on Persona, working with Privy’s engineering team
Focus
Mobile platform: guidance, feedback, and status components that adapt to small screens
Handoff
Engineers built the components in Vue and publish them as an open-source library
Period
2022–2024
Designers reviewing Persona component specs in Figma on a shared screen during a working sessionDesigners and engineers discussing component tickets on a shared screen

Semantic tokens for light and dark

Every colour in a component points to a semantic token from the Crimson Wave theme, such as fg/default, bg/default, or border/default, rather than a raw value. The same component then works in light and dark mode, and focus outlines follow the same six states: default, accent, info, success, warning, and danger.

A bottom sheet beside its colour tokens, and focus outlines in light and dark mode

Guidance, feedback, and status on small screens

Most of my work covered the components that guide people and tell them what is happening: onboarding, confirmations, alerts, and status. On mobile they had to stay readable and reachable on a narrow screen without covering the task underneath.

Guidance
Walkthrough, tour guide, and tooltip, to introduce features without leaving the task
Feedback
Modal dialog, banner and alert, flag alert, and pop-up, to report results and ask for decisions
Status and input
Toggle, label, progress, rating and impression, and pagination states
Persona tour guide dialog and dark and light tooltipsPersona info, warning, and danger banners, and a confirmation modal dialogPersona labels, toggles, progress steps, and pagination on a mobile screen

From Figma to an open-source library

Designers defined components and tokens in Figma. Most of the components I designed, including tour, tooltip, toggle, progress, pagination, modal, label, pop-up, and banner, shipped in the library. The team used a merge request note, changelog, and component status page to manage changes, and Privy’s engineers built them in Vue 3 with a Tailwind preset and publish them as an open-source library with its own documentation site.

Persona in numbers: 89 components, open source since 2022, Vue 3 and Tailwind, and a docs site with browser support

Adapt quickly, but question every new component

Working on Persona taught me to adapt quickly. New features often came with new needs, and the system had to keep up. But not every request needed a new component. Before designing one, I learned to ask whether an existing component could cover the case, or whether something new was really needed. That question kept the library smaller, more consistent, and easier for the whole team to use.