BlueSky Design System

help
Guiding question
How might we reduce design decisions and build quality products faster?
wb_sunny
Highlights
One system, two brands, endless possibilities.
assignment
Define · Context
Bell was getting a new look.
The MyBell app was mid-redesign, moving to a more modern, airy UI. Virgin Mobile would follow. Both apps shared most of the same UX, so the opportunity was clear: build one system that supports both brands instead of designing everything twice.
One problem. No shared component library, no token structure, no documentation process. We were starting from zero.
route
The process
From first token to two brands
BlueSky grew through four stages. Every section below maps back to one of them.
flag
Define
Set the goals, principles, and architecture before building anything.
build
Create
Tokens, icons, and components. Built once, flexing across two brands.
rocket_launch
Adopt
Intake, quality bars, and handoff so the system actually gets used.
auto_graph
Evolve
Use feedback and real usage to decide what’s next, then grow from app to web.
token
Create · Tokens
Tokens that flex without breaking
Tokens powered everything BlueSky could do: two brands, light and dark, platform differences, breakpoints. Building a token structure was the easy part. Building one that could keep growing without becoming a mess was the real work.
We split tokens into layers, each with one job.
token
Core
unfold_more
brand_family
Brand
unfold_more
ios
Platform
unfold_more
responsive_layout
Breakpoint
unfold_more
contrast
Theme
unfold_more
widgets
Component
unfold_more
globe
Global
unfold_more
Token Studio first, Variables later
We started with Token Studio before Figma Variables existed.
When Variables launched, we synced Token Studio with them, so designers could switch brand, theme, platform, and breakpoint right in their files. Devs inspecting a design saw variable names that matched our token names 1:1.
From Token Studio, our tokens were exported to GitLab and transformed for iOS (SwiftUI) and Android (Jetpack Compose).
Spacing needed rules as much as colour
We also created semantic spacing tokens to reduce guesswork around common layout patterns.
Our spacing scale was built on a 4px base: spacing.x1 = 4px, spacing.x2 = 8px, and so on. This gave designers a consistent set of values to work from, and semantic tokens like spacing.semantic.vertical.betweenFields mapped directly to that scale for specific use cases.
Without them, designers were making independent spacing decisions for the same patterns. A dedicated token meant everyone was working from the same value, every time.
lightbulb
Key takeaways
grid_guides
Create · Iconography
Icons anyone could add to
The app kept needing new icons. Instead of routing every request through the design system team, we wrote guidelines so any designer could contribute and the library still felt like one family.
They covered key shapes, grid, stroke width, vector construction, and stroke ends.
flowchart
Adopt · Intake
Sorting requests before they pile up
Requests came from every direction, each one urgent to whoever sent it. Without a process, prioritizing was guesswork.
So we built a repeatable intake. Design, our product owner, and dev reviewed requests together so the highest-impact work moved first.
brick
Adopt · Criteria
Every component had to earn its spot
Not every request made it in. Each one had to pass four checks, then got ranked by urgency and demand.
cycle
Reusability:
Can the component be used across multiple features and brands?
Are there any existing components or patterns we can use?
format_shapes
Consistency: Does it align with the rest of the design system and visual style?
code_blocks
Complexity:
Is it simple to build in dev?
Is it easy to maintain in design?
accessibility_new
Accessibility:
Does it meet accessibility standards for all users?
If interactive, does it have a big enough touch target?
docs
Adopt · Documentation
Sweating the details for a smooth handoff
None of this mattered if engineers couldn’t build from it. Every component shipped with a doc covering five things.
wb_sunny
Results
What changed after BlueSky shipped
The biggest win wasn’t a perfectly organized file. It was giving teams a shared way to make decisions, ship patterns, and keep the experience consistent as the product kept moving.
Less duplication
Redundant component versions were folded into leaner, more flexible structures.
Faster layout work
Designers could move from screen to screen faster because common responsive decisions were already baked in.
More shared language
Tokens, criteria, and documentation gave design and dev a clearer way to talk about what should be built, and why.
fast_forward
Evolve · Next steps
From app to web
BlueSky’s impact on the apps got stakeholders thinking bigger. Bell’s web products were inconsistent, disconnected from the app, and overdue for a refresh.
The other BlueSky lead and I were asked to help kick off that work, taking what we learned to a much larger surface.
It’s ongoing. But it started here.


















