BlueSky Design System

Overview

Bell and Virgin Mobile’s app teams had no shared foundation. Designers worked from scattered files, the UI drifted, and every feature built for Bell got rebuilt for Virgin. With a full app redesign underway, that stopped being affordable.

BlueSky gave design and dev one source of truth for the first time: two brands, iOS and Android, light and dark.

My Role

Sr. Designer. Token architecture, components, documentation.

The Team

2 lead designers working closely with 1 product owner and 6+ engineers.

Timeline

~ 6 months for first implementation of tokens and foundational components.

Overview

Bell and Virgin Mobile’s app teams had no shared foundation. Designers worked from scattered files, the UI drifted, and every feature built for Bell got rebuilt for Virgin. With a full app redesign underway, that stopped being affordable.

BlueSky gave design and dev one source of truth for the first time: two brands, iOS and Android, light and dark.

My Role

Sr. Designer. Token architecture, components, documentation.

The Team

2 lead designers working closely with 1 product owner and 6+ engineers.

Timeline

~ 6 months for first implementation of tokens and foundational components.

Overview

Bell and Virgin Mobile’s app teams had no shared foundation. Designers worked from scattered files, the UI drifted, and every feature built for Bell got rebuilt for Virgin. With a full app redesign underway, that stopped being affordable.

BlueSky gave design and dev one source of truth for the first time: two brands, iOS and Android, light and dark.

My Role

Sr. Designer. Token architecture, components, documentation.

The Team

2 lead designers working closely with 1 product owner and 6+ engineers.

Timeline

~ 6 months for first implementation of tokens and foundational components.

help

Guiding question

How might we reduce design decisions and build quality products faster?

wb_sunny

Highlights

One system, two brands, endless possibilities.

Shared flows, built once for both brands

Semantic colour tokens switch between light and dark

A Primary Button background and its token references

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.

A diagram of the BlueSky token set structure

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.

Semantic spacing tokens for common patterns, like the gap between fields

lightbulb

Key takeaways

  1. Component tokens for everything bloated our token file fast. Use them only where values really differ by brand or theme. Semantic tokens cover the rest.

  2. Naming slips are easy to miss early and painful to fix later. By the time we caught ours, other teams were already using those tokens.

  3. Once other teams consume your tokens, a change is a product decision. Deprecations need communication, migration guides, and lead time.

  1. Component tokens for everything bloated our token file fast. Use them sparingly, only for values that genuinely vary between brands and themes. Semantic tokens handle the rest.

  2. Naming inconsistencies are easy to miss early and painful to fix later. By the time we caught ours, other teams were already consuming those tokens, turning a cleanup into a breaking change.

  3. Once other teams are consuming your tokens, changes become a product decision. Deprecations need communication, migration guides, and lead time, not just an internal update.

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.

Key shapes: Square, Circle, Tall Rectangle, Long Rectangle.

Stroke width, shapes and vectors

Stroke ends are squared

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.

The end-to-end process showing how component requests moved from intake and prioritization through design, development, testing, and out to consuming teams.

Decomposition: breaking down each new request to understand its structure and usage, and flag questions for devs.

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?

From tokens to atoms, molecules, and organisms

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.

Anatomy

Specs for dev handoff

Behaviours

Usage guidelines

Accessibility

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.

80%

80%

Less duplication

Redundant component versions were folded into leaner, more flexible structures.

70%

70%

Faster layout work

Designers could move from screen to screen faster because common responsive decisions were already baked in.

2×

2×

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.

You can reach me here ↓

Copyright ©️ 2026

You can reach me here ↓

Copyright ©️ 2026

You can reach me here ↓

Copyright ©️ 2026