Stripe logo

Implement consistent core tokens, ship new work, org-wide, faster

Helm and Sail are already almost the same. Why not make them one? Or, at least, make them share the same foundations? In this prototype, I loosely explore what it would take to get us there.

Search
Gross volume
$4,242.42
10:19 AM
Yesterday
$4,242.42
Excludes payment record data.
12:00 AM
12:00 PM
New
Reopen paid invoices.
Fix reconciliation mistakes.
You can reopen paid invoices to fix reconciliation errors by applying or unapplying payments.
View the docs

Your overview

Date range
Last 7 days
Daily
Compare
Previous period
Proto controls
Stripe Assistant
Why do this?
Thought for 12s
Implementing globally standardized tokens allows for a truly unified chat experience across all of Stripe's products.
This will save time and effort by removing the need to create unique instances of components per surface.
At the same time this adds flexibility as both designers and developers will be familiar with the core design language across surfaces.
Why now?
Thought for 2s
Mostly, because I heard Inter might be used in Dashboard 😂. Adding another custom font into the mix will only make fragmentation and portability worse.
As a designer who frequently works across surfaces, I've seen how much time and effort is wasted by having to create unique instances of components per surface.
Since Helm is the newest design system, building upon it seems to be sensible.