Photon
One language, three platforms.
Angel had a design system, but not one complete enough to help us scale in the months to come. I took it upon myself to start Photon, in close partnership with my fellow mobile product designer and our EVP of Experience. I relied on their expertise to make sure we built the foundation properly. Four years later, Photon spans seven teams.
- Role: Creator & lead
- Years: 2022–2026
- Platforms: Web, mobile, TV



22 components
Across web, mobile, and TV
Not built to scale yet.
When I joined Angel, nearly all the design energy pointed at one title, The Chosen. Web, mobile, and TV each had a look of their own, and the design system we had wasn't complete enough to hold them together as Angel grew.
Before · Web

Before · Mobile

Before · TV

Angel’s home screens before Photon. Each platform had its own type and its own way of presenting a title.
Nobody asked
My directive was web, and I was on track to become PM of web. Nobody asked me to build a design system. TV didn’t have a product designer yet. Its PM and engineers had built a working app on their own.
It wasn't a styling problem. It was a structural one.
Three platforms, each reinventing the basics, without a complete foundation underneath. I believed our experiences had to feel the same on every screen, and the path we were on would never get us there.
The pain was still small, and the company couldn’t see the cost yet. I decided to build the foundation before the org felt the need, on my own nights and weekends. It would already exist when our projects needed it.
Photon Core
Built from the atoms up.
I started at the atomic level, not the screen: type, color, icons, shadows, and blurs. Every component on every platform is built from them.
Grounded before it was built
I didn’t build Photon alone. Two close partners shaped it from the first atom, and an outside expert pressure-tested the plan against scale.
01
My fellow mobile product designer and our EVP of Experience
Close partners from the start. I relied on their expertise to make sure we built the foundation properly.
02
A design system manager at Microsoft
I asked how a system holds up across a large org, and used the answers to plan three platform libraries on one core.
Where it started
The early boards put everything on one canvas: color, type, buttons, navigation, and the first light and dark styles. The Chosen still had colors of its own.

Photon Core v1.5
Each atom got its own board, with the rules for using it. Every platform library draws from these.
Dark for watching. Light for buying.
Every component works in light and dark. Theme wasn't a preference. It was a business decision, and we tested it.

Light
For buying
Transactional pages like buying movie tickets converted better on light.
- Investment pages
- eCommerce pages
- Legal documents
- Blogs
- Job boards
- User accounts

Dark
For watching
Watch experiences converted better on dark, every time.
- Watch and discover
- Show pages
- Episode pages
- Livestreams
- The mobile app, TV, and Angel.com


The split held up every time we tested it. The system encoded what actually moved the numbers.
One language, three platforms.
From Photon Core I built three component libraries: web, mobile, and TV. 22 components in all, every one shaped from the same atoms, every one themeable light and dark.



A title page on web, the mobile app, and TV. The same Guild rating, buttons, and type, each tuned to its platform.
One button, three platforms
The button shows it best. Each library has the same types, the same light and dark themes, and the same Oxide. Each one is tuned for how people use it: hover on web, touch on a phone, focus for a remote, and a square version for Roku, which can’t draw rounded corners.
The starter set
I shipped the core components first, the ones every team needed on day one. Everything after built on them.
- Buttons
- Navigation
- Pill badges
- Lozenges
- Input fields
- Thumbnails
Photon, brought to TV
The timing let me become TV’s first product designer at the start of 2023, and build the new TV experience on the system I had just shipped. It worked in practice, not just in Figma.
See Angel TVAdoption was part of the design.
Then I drove adoption, platform by platform. Each one came online at its own pace, toward one goal: clarity.
01
Core components first
Buttons, navigation, inputs, and thumbnails, shipped first to unblock every team.
02
A plan per platform
An implementation plan with each PM and lead engineer.
03
Every designer equipped
Hands-on enablement for every designer, with the process to build on Photon.
Seven teams today
It started with three platforms. It grew to every team that designs for Angel.
- 01Web
- 02Mobile
- 03TV
- 04Theatrical
- 05Guild voting
- 06Filmmaker
- 07Marketing
Four years of stewardship. As needs surfaced, I updated the system alongside my other work.
The foundation Angel runs on.
One atomic core, three platform libraries, and every team at Angel designing in the same language.
4 years
As the design foundation Angel runs on.
7
Teams building on it: web, mobile, TV, theatrical, Guild voting, filmmaker, and marketing.
22
Components across three platform libraries.
1
Atomic core every component inherits from.
2
Themes on every component. Dark for watching and light for buying held up every time we tested it.
1st
Product designer on TV, building on the system I had just shipped.
In summer 2026 I handed Photon to our new Design System Lead, to take it into the future at scale.
Photon is the system. Building the team that uses it is its own story.
Communication is king- Team
- Seth Taylor, EVP of Experience, and Chad Dant, Mobile Product Designer, close partners from the start. A Design System Manager at Microsoft, and the PMs and lead engineers on every platform.
- My role
- Creator and lead of Photon. Photon Core, three component libraries, the rollout, and four years of stewardship.
- Tools
- Figma.
Up next
Angel TV
As Angel’s first TV product designer, I redesigned the experience for the big screen and helped launch a new profiles experience in 30 days.
Read the case














