Book a call

Work / IBM × Riyadh Air

IBM×Riyadh Air

A design system for an airline that started from zero

A pilot first, then 71 components that every Riyadh Air team built from, in English and Arabic, light and dark.

71
components in 13 families
2 × 2
EN and AR, light and dark
6
breakpoints, watch to desktop
8+
apps from one library
Role
Design system designer, IBM
Client
Riyadh Air
Partners
Publicis Sapient, IBM engineering
Timeline
2023–24
The Riyadh Air design system: Canopy Twist line art, a booking card and component sheets on indigo

01 the client:

An airline with no past to inherit

Riyadh Air is Saudi Arabia's new national carrier, founded by the Public Investment Fund and built digital-first.

2023
founded, with IBM named lead digital partner
100+
destinations planned by 2030
787-9
a new Boeing Dreamliner fleet
Oct 2025
first flight, Riyadh to London Heathrow

Most airlines carry decades of booking engines, loyalty platforms and check-in kiosks. Riyadh Air started with none of it. Every screen a guest would touch, from booking to boarding, had to be designed and built for the first time, while the airline itself was being stood up.

IBM was the lead digital partner. Its design team proposed the design system and built it with Publicis Sapient, and IBM engineers turned it into code. Riyadh Air's product owners, brand and engineering teams reviewed and signed off. Aniket worked on the system as a design system designer at IBM.

Client

Riyadh Air

Product owners, brand and engineering, standing up an airline and its digital estate together.

Lead digital partner

IBM

The design team proposed the system and built it. IBM engineers built the components in code.

Agency

Publicis Sapient

Our partner on the design system, shaping and reviewing the library with us.

02 the problem:

Many apps, many teams, one launch date

Booking, check-in, loyalty and the trip itself, across web, phone and watch, all designed at once.

Scale8+

web and mobile apps, designed at once

Language2

scripts, reading in opposite directions

Devices6

breakpoints, from a watch to a wide desktop

Deadline1

launch date that couldn't move

Five to six web apps and two to three mobile apps were being designed in parallel, each with its own team. Left alone, every app would drift into its own version of the brand, and every team would rebuild the same button under a deadline set by the first flights.

Two things made it harder. Every screen had to work in English and Arabic, which read in opposite directions and need different line heights. And the brand was brand new: a lavender identity made for liveries and billboards, with nothing yet that could carry a seat map, a price or an error message.

How might we give every team, on every device and in both languages, one way to build Riyadh Air, before there was a Riyadh Air to copy?

Every app team designing its own interface

One library every team builds from

Arabic as a translation pass at the end

Every component drawn in English and Arabic

A lavender brand made for liveries and billboards

A brand that can carry a seat map and an error

03 the work, in twelve frames:

Swipe through it

Foundations, components and brand, as the library shows them. Select any frame to see it full size.

Colour. From a lavender brand to product UI.
01ColourFrom a lavender brand to product UI.
REX button. The AI assist, in English and Arabic, light and dark.
02REX buttonThe AI assist, in English and Arabic, light and dark.
Typography. Two scripts, one scale.
03TypographyTwo scripts, one scale.
Counter. Mirrored for right to left.
04CounterMirrored for right to left.
Grids. Six breakpoints, from wrist to wide screen.
05GridsSix breakpoints, from wrist to wide screen.
Avatar. Five sizes, four statuses, aircraft included.
06AvatarFive sizes, four statuses, aircraft included.
Iconography. Material Symbols, used everywhere.
07IconographyMaterial Symbols, used everywhere.
Swipe button. Idle, confirmed and loading.
08Swipe buttonIdle, confirmed and loading.
Increments. Thirteen steps of space, 1 to 64px.
09IncrementsThirteen steps of space, 1 to 64px.
Brand logo. English-first and Arabic-first lockups.
10Brand logoEnglish-first and Arabic-first lockups.
Effects. Four shadows and two blurs, each with a job.
11EffectsFour shadows and two blurs, each with a job.
Canopy Twist. The brand's line art, as a component.
12Canopy TwistThe brand's line art, as a component.
01 / 12

04 the pilot:

Prove it on one project, then scale

Rather than pitch a system on a slide, the team ran a small one on real work and let the results make the case.

A design system is a big ask of a client building everything else at the same time. So the team didn't pitch it on a slide. It ran a small system on one IBM project, watched whether it helped, and let the results make the case. The teams outside the pilot asked for it, and it delivered a clear efficiency gain on real work. That was enough to build the full system.

  1. 01

    Propose

    A shared system to speed up delivery

  2. 02

    Pilot

    One IBM team builds with an early library

  3. 03

    Measure

    Faster? Consistent? Do teams want it?

  4. 04

    Scale

    The full system, with Publicis Sapient

Result
Faster

A clear efficiency gain on real work.

Result
Wanted

Teams outside the pilot asked for it.

Result
Approved

The go-ahead to build the full system.

Partner
Publicis Sapient

Shaped and reviewed the library with IBM.

05 brand to UI:

A lavender brand, made usable

Indigo and mist carry every screen. Violet does the work. Lavender and peach stay for brand moments.

Dark theme surface
Indigo
#240852
Actions, badges
Violet
#6A67E1
Brand moments
Lavender
#DAD8FC
Brand moments
Sunset peach
#FBD8D6
Light theme surface
Mist
#F6F7FC
Success
Warning
Error
Highlight
Social proof
Canopy Twist · G02/B03 · move across it to twist
Canopy Twist uniform pattern
Canopy Twist uniform pattern
Logo lockups, chosen by page language
Logo lockups, chosen by page language

06 foundations:

Styles that travel through all 71 components

Pick a breakpoint, switch the script. The grids and the type are drawn from the library's own values.

XX Large

Large

Body

Family

Increments: 1 to 64px
Increments: 1 to 64px
Effects: depth, used sparingly
Effects: depth, used sparingly
Iconography: Material Symbols
Iconography: Material Symbols
Grids: six breakpoints
Grids: six breakpoints
Library: Typography page
Library: Typography page
Library: Increments page
Library: Increments page
Library: Effects page
Library: Effects page
Library: Grids page
Library: Grids page

07 components, live:

Switch the theme. Switch the language.

Everything flips: direction, arrows, numbers and currency formatting.

Every component shipped in all four versions.

Route headline · Segmented button

RUHRiyadh
LHRLondon

5.0

Counter · Seat selector · REX

1

Rebuilt in HTML from the library sheets, with its colours, shapes and states. Fares are illustrative.

08 the library:

71 components in 13 numbered families

Read the families and you can read the product: an assistant, selling nudges, and the trip itself.

71components, each in English and Arabic, light and dark
G01 · Badges6
  • Avatar
  • Main badge
  • Round badge
  • Rating badge
  • FOMO social badge
  • Location badge
G02 · Branding3
  • Brand logo
  • Canopy Twist uniform
  • Canopy Twist dynamic
G03 · Buttons11
  • Main button
  • Segmented button
  • Loader button
  • Modal button set
  • Menu item button
  • Zoom button
  • Counter
  • Double button
  • REX button
  • Sticky button
  • Swipe button
G04 · Chat3
  • Speech bubble
  • Message input bar
  • Live voice input
G05 · Editorial6
  • Accordion
  • Tooltip
  • Table line
  • Bullet point list
  • Price
  • Route headline
G06 · Controls7
  • Slider
  • Level controller
  • Player controller
  • Chip
  • Seat selector
  • Rating stars
  • Toggle
G07 · Forms10
  • Checkbox
  • Date selector
  • Phone number field
  • Radio button
  • Security input code
  • Price range indicator
  • Text area
  • Text field
  • Destination search
  • Prefilled selectors
G08 · Lists4
  • List item
  • Avatar list item
  • List
  • Dropdown
G09 · Loaders3
  • Progress bar
  • Loader circle
  • Loader dots
G10 · Nudges4
  • Live update
  • Nudge message
  • Live message bar
  • General message
G11 · Navigation5
  • Breadcrumbs
  • Top bar
  • Tab item
  • Banner carousel
  • Tab selector
G12 · Tiles4
  • Main tile
  • Image and text tile
  • Progress tile
  • Action tile
G13 · Structural5
  • Progress segment
  • Progress indicator
  • Divider
  • Carousel dots
  • QR code
REX button · G03/B09
REX button · G03/B09
Counter · G03/B07
Counter · G03/B07
FOMO badge · G01/B05
FOMO badge · G01/B05
Loader button · G03/B03
Loader button · G03/B03
Modal button set · G03/B04
Modal button set · G03/B04
Avatar · G01/B01
Avatar · G01/B01
Zoom · G03/B06
Zoom · G03/B06
Location badge · G01/B06
Location badge · G01/B06
Rating badge · G01/B04
Rating badge · G01/B04
Menu item · G03/B05
Menu item · G03/B05
Double button · G03/B08
Double button · G03/B08
Round badge · G01/B03
Round badge · G01/B03

09 definition of done:

Tested in four languages before it shipped

Arabic for direction, German for long words, Japanese for a third script, and currencies with very long numbers.

Language

Currency

  1. 01

    Build

    Fewest frames; every text on a style, every colour on a variable

  2. 02

    Structure

    Named to convention, every useful variant, placed and described

  3. 03

    Test

    EN and AR, light and dark, long words, long numbers, in a real layout

10 how we worked:

Three companies, one way from idea to code

The system sat between three organisations and many teams. It worked because the path from an idea to a component in code was the same every time.

  1. The pilot

    An early library on one IBM project, to test whether a shared system would speed the teams up.

    IBM
  2. The system

    Styles, structure and components built from scratch in Figma, reviewed with Publicis Sapient and Riyadh Air's product team.

    IBM · Publicis Sapient
  3. Into code

    IBM engineers built the components in code, so every app used the same ones.

    IBM design · IBM engineering
  4. Launch

    The apps launched with the airline. The first flight left Riyadh for London Heathrow.

    Riyadh Air
Rules

One page of rules

The library opened with its own guide: what ready means, how it's structured, how to name things.

Language

Bilingual from day one

Arabic wasn't a translation pass at the end. Every component shipped with its right-to-left version.

Handoff

Design and code in step

Variant names matched the props engineers built, so handoff was a lookup, not a translation.

How the three companies decided what shipped is its own case study: who decides what ships.

11 what changed:

From Figma to code to launch

Speed
Proven first

A pilot showed a clear efficiency gain before the full build.

Consistency
One airline

71 components and six breakpoints, used by every team.

Reach
EN + AR

Every component in both directions, light and dark.

Adoption
Shipped

Built in code by IBM engineering. The apps launched with the airline in October 2025.

01

Prove it small. A pilot on real work persuades faster than any deck.

02

Design the second language first. Arabic and German break what English never will.

03

Start at the smallest screen. A 184px watch made every larger layout simpler.

12 for your team:

The same playbook, as a studio engagement

Each step of this case study maps to how we work with clients now.

Aniket Pandey worked on this as a design system designer at IBM (2023–24), with the IBM design team, IBM engineering, Publicis Sapient and Riyadh Air's product, design and engineering teams. This is IBM client work done as an employee, not Layer One client work. Images belong to Riyadh Air and IBM and are shown for portfolio purposes.

Next case studies