Enter password to view case study
Design system · Web, iOS, Android
MyBrightDay App design system
Turning sprawling component files into one system that designers and developers across product, web, and mobile can pull from with confidence.


Role
Senior Product Designer, solo
Tools
Figma variables, styles, and components
Platforms
Web, iOS, Android
Deliverables
Tokens, components, platform kits, and guidance
The problem
The MyBrightDay App grew so quickly that its organization became a mess. Components lived in tons of different files, and no one knew which version was the most up to date or approved. Colors were hard-coded hex values, so even a single button could exist in several versions.
No single source of color
Brand names like Afternoon Sun and Riverboat existed on a sheet, not as tokens, so the same blue showed up a dozen slightly different ways.
Accessibility was guesswork
Nothing showed which color pairs passed WCAG contrast, so designers checked by hand. Even the error color, a magenta, failed on light backgrounds, making the most important messages the hardest to read.
Pages split by team, not by purpose
“Product” and “Web & Brand” pages mixed buttons, cards, and nav, so designers searched instead of browsing.
No mobile starting point
iOS and Android work began from blank frames every time.
My task
Rebuild the existing library into a design system that works across web, iOS, and Android without losing anything designers already relied on. Along the way, simplify components and set up a governance plan so the team can maintain the system without it eating up their time.
The ask
One file with tokens, components, and guidance, built from the existing source library.
My role
Solo designer: audit, token architecture, components, platform kits, and documentation.
What success looked like
Every old component accounted for, every color pair accessible, and a designer can find what they need in one click.
Key decisions
Decision 1
Start with the designers who’d use it
I met with the designers on the team to learn what was working for them in the old library and what wasn’t. Their pain points shaped the structure, so the system fits how they already work. That makes it one they’ll actually use and keep up to date.
Decision 2
Pull developers in from the start
I brought developers into the process early so design and code would share one source of truth, not two systems that drift apart. Every Figma token maps to a matching CSS variable and iOS and Android name, and each Usage & Specs panel includes React, SwiftUI, and Compose snippets.
Decision 3
Two token layers, not one
55 primitives hold the brand palette by its real names. 60 semantic tokens (bg/surface, text/primary, border/subtle) point at them, with Light and Dark modes. Designers pick by purpose; the brand can change underneath.
Decision 4
Accessibility built into the palette
I tested every brand pairing and documented the 270 that pass WCAG. Error moved from magenta to Fire Ant red so every semantic pair passes AA in both modes.
Decision 5
Organize by what it does, not who made it
I dissolved the team-based pages and regrouped components into Inputs, Selection, Feedback, Navigation, and five more. Each page has labeled sections and a Usage & Specs panel beside it.
Decision 6
Meet mobile designers where they work
iOS and Android kits use native patterns (nav bars, tab bars, sheets, Material app bars) on the same tokens, with starter screens and device frames.
Built to flex and scale
Instead of a separate copy for every look, each component is built once and configured with properties. Designers change a setting instead of detaching or redrawing, and the system can grow without the file getting messy again.
94
Component sets, each one configurable
663
Variants designers can switch between in one click
2
Modes, Light and Dark, from the same tokens

One button, 48 variants
Style, size, and state are settings, not separate components. A label field and two swappable icon slots cover every button in the app, from “Check in” to a loading state.

Text fields that handle every state
Three sizes and six states, including error, success, and warning, with toggles for the label, helper text, and trailing icon. Form screens use one field instead of a handful of look-alikes.

Alerts from a gentle note to an emergency
One banner covers info, success, warning, and emergency messages. Toggles show or hide the timestamp, the actions, and the close button, so it fits a quick reminder or an urgent closure notice.

List cards that adapt to their content
One or two lines, four interaction states, and optional icon and chevron. The same card works for a child’s daily report, a menu row, or a settings link.
Why it scales
Scales by design
Icons swap, they don’t multiply
Icon slots are swappable, so adding a new icon never means adding new variants to a component.
Scales by design
Tokens carry the theme
Every fill, text color, and border points to a semantic token. Dark mode and future brand changes flow through all 94 sets at once.
Scales by design
One system, every platform
Shared components like the Switch have a Platform setting for iOS and Android, and both kits use the same tokens, so new platforms extend the system instead of forking it.
What’s inside
A look at the file, from the foundations up. Every frame here is live in the Figma file.



Semantic color tokens
Purpose-named tokens sit on top of the brand palette: backgrounds, text, and borders each have their own set.


Light and dark modes
The same tokens switch cleanly between Light and Dark, and every key pair is re-measured for contrast in both modes.


Accessible combinations
Real UI built from token pairs, checked in both modes. 270 brand pairings pass WCAG.

Usage & Specs panel
Every component comes with do’s, don’ts, accessibility notes, and React, SwiftUI, and Compose code, right next to the component itself.


iOS and Android kits
The same Today screen built from each kit: native patterns like nav bars and Material app bars, on one shared set of tokens.

App icon set
Rebuilt as clean vectors across five brands and a light style.

Linked file map
Every tile on the Getting Started page jumps straight to its section.
Results
The old library now lives in one organized system, and a source coverage audit maps every original component to its new home.
115
Color tokens: 55 primitives and 60 semantic, in Light and Dark
270
Brand color pairings documented as WCAG-passing
44
Text styles, all in Mulish, including iOS and Android type scales
33
Platform kit component sets for iOS and Android
17
Linked tiles in the file map, one click to any area
The governance plan keeps it that way: a versioned changelog (1.0.0 to 1.4.3) and a decision record for the trickier calls.
Reflection
The biggest win wasn’t a new component. It was making the right choice the easy one: document accessible pairs up front, and put each component’s guidance right next to it. Bringing designers and developers in from the start is what gets people to actually use it.