Rework of a shipped system

EmCan design system rework

From a library of styles to primitives, semantic tokens and components.

EmCan’s design system was a set of text styles and colour styles. I started a semantic token layer on top of it but didn’t maintain it: as the only designer, I had to choose between shipping deliverables and keeping the system up, and the deliverables won.

In 2026, after leaving, I rebuilt it in three layers: primitives, then semantic tokens, then components.

Company
SiaXperience / Emarat EmCan
Role
Independent rework, after leaving
Duration
2026
Focus
Design systems · iOS, Android, web
EmCan semantic design system: primitives, semantic tokens and components
01

The brief

Product
EmCan is a national fuel and retail loyalty super-app with more than 100,000 users on iOS, Android and web. I was its Lead Product Designer and governed its design system across all three platforms.
Business model
EmCan is free for customers. Emarat runs it to drive repeat fuel and convenience-store spend at its stations, and to build direct, data-driven customer engagement.
Why it mattered
Every screen was designed in English first, then rebuilt by hand for Arabic: each layout mirrored from left-to-right to right-to-left, and every text style swapped to the Arabic font, screen by screen. With direction-aware tokens and components, that would have been one switch per component instead of a rebuild of every screen.
02

The problem

I traced every style in the shipped file back to a role. The app is light mode only, so the rework covers the light theme. It lands as 53 primitives, 84 semantic tokens, a Script collection with Latin and Arabic modes (26 tokens covering typeface, weights, line heights and reading direction), and an icon-tone collection.

  1. Styles without a layer of meaning

    The original system had text and colour styles only, with no way to handle direction. I started a semantic layer, but as the solo designer I had to choose between shipping and maintaining it, so it drifted. Colour wasn’t the roadblock, since the app was light mode only. Left-to-right to right-to-left was.

03

The decisions

  1. Three layers, each with one job

    Primitives hold raw values, semantic tokens give them meaning, and component tokens say where they’re used. I first tried separate English and Arabic text styles, but every screen still had to be swapped style by style and mirrored by hand. The trade: more setup up front, so a language switch happens at the component level instead of on every screen.

04

Deep dive

From primitive to component

Pick any token to see what it’s built from and what uses it.

The constraint is direction. Spacing is start and end rather than left and right, components mirror, and each semantic text token pairs a Latin style with an Arabic one.

Primitives 53

Semantic 84

Component · icon tone 8

Script 26

TokenLatinArabic
font/family/baseRed Hat DisplayNoto Sans Arabic
flowLTRRTL
weight/display/heroBoldSemiBold
line-height/display/hero6472
weight/display/subtitleRegularRegular
line-height/display/subtitle2632
weight/heading/h1MediumSemiBold
line-height/heading/h13236
weight/heading/h2SemiBoldSemiBold
line-height/heading/h22632
weight/heading/h3SemiBoldMedium
line-height/heading/h32428
weight/title/sectionSemiBoldMedium
line-height/title/section2428
weight/title/componentSemiBoldMedium
line-height/title/component2226
weight/body/defaultRegularRegular
line-height/body/default2226
weight/caption/defaultLightExtraLight
line-height/caption/default2024
weight/caption/strongMediumMedium
line-height/caption/strong2024
weight/caption/smallLightLight
line-height/caption/small1620
weight/label/microRegularRegular
line-height/label/micro1416
05

Final design

EmCan redesign: home, tier and transfers screens built from the reworked tokens
  1. One balance card across home, tier and transfers. The tier changes its badge and header colour, not the component.
  2. Earn, Burn and Send sit in a single action bar under the balance.
  3. Light theme only, as scoped.
06

What I’d measure

How many edits a brand-colour or typeface change takes before and after, and how many hardcoded values a script audit finds per screen.