Skip to content
Back to homeAajil Design System

Aajil Design System: one language across products, scripts and themes

As Senior Product Designer, I owned Aajil’s design system end to end and built it from zero in one month with an art director and a graphic designer: one visual language for the web and mobile apps, designed Arabic first, in light and dark.

My role
Senior Product Designer
Timeline
1 month (Jan to Feb 2026)
Team
3
Used by
The web app and mobile app designs

From the Aajil Figma library

287 tokens2 scripts2 themes40+ components

The system composed from the Figma library: a credit request in the stepper, a credit table, a verification modal, a dropdown, alerts, badges and the button colors. Switch the language and the theme under the chapters.
Chapters
  1. Why Aajil needed a system
  2. A month, three people
  3. Principles
  4. Foundations
  5. Tokens
  6. Shaped for financing
  7. The component library
  8. How the teams use it
  9. Learnings

Evidence

1 month

From no shared system to a library the web and mobile apps are designed on.

287

Variables in two collections: 153 raw values, 134 named by role.

2 × 2

Every component in Arabic and English, each in light and dark.

Why Aajil needed a system

Every product spoke its own dialect.

The cost of designing as you go

Aajil finances construction businesses in Saudi Arabia. At the time it ran a website, a web app, a mobile app and internal dashboards, each designed when it was needed, by whoever was free. Nothing tied them together: buttons, spacing and colors drifted from one product to the next, and every new feature reopened the same question: which version is right?

Arabic first, twice the work

We designed Arabic screens on their own, never as a mirror of the English.

That is right for Saudi businesses, and costly without shared parts: every screen existed twice, kept in step by hand.

The goal

One visual language across every product, and a base for every feature and experiment after it. The rebrand from Buildnow to Aajil strengthened the case. Consistency was the reason.

Earlier at Aajil, I had redesigned the website in one week.

A month, three people

Speed came from clear ownership, not shortcuts.

Who owned what

Zayed, our art director and Aajil’s creative lead, set the graphic foundations: color direction, gradients and visual patterns. Our graphic designer owned illustrations and icons. I owned the system end to end: its architecture, principles, tokens and variables, components, documentation and the handover to engineering.

Speak the engineers’ language

Engineering was moving to a new front end, so the system speaks its language: text-sm, shadow-md and rounded-lg mean the same in Figma and in the front end engineering was moving to, so building it needs no glossary.

AI for the documentation, me for the decisions

I used AI for documentation, mostly for the tokens, and reviewed and decided every value myself. The components are not generated: they come from the UI components and patterns already used across Aajil products.

Principles

Four rules behind every decision.

  1. Arabic is not a translation

    Each script is set on its own terms, with its own type roles and taller Arabic line heights.

    Typography tokens exist twice: one set for English, one for Arabic.

  2. Name by role, not by value

    Components ask for a job, like the brand background, never a hex code. A theme only changes what sits underneath.

    bg-brand is yellow 400 in light and yellow 300 in dark; no component changes.

  3. One vocabulary for design and code

    Tokens use the same names as the code, so a handover is a lookup, not a translation.

    text-sm, shadow-md and rounded-lg mean the same thing in Figma and in code.

  4. Calm where money moves

    The components a business uses to verify, apply and pay get the most states and the most care.

    The code field alone has 28 variants: four sizes, seven states.

Foundations

Color, type, space and icons: the parts everything else is made of.

Color

A confident yellow on true neutrals. The brand scale runs from 50 to 950 with 400 as the brand color; the neutrals carry no tint, so the yellow always leads. Green, orange and red are kept for status.

Rebuilt in code from the Aajil tokens

A preview of Aajil’s colors: the key roles for the current theme, then the scales. The Figma file holds the full set.

Type

IBM Plex Sans and IBM Plex Sans Arabic are one family, so both scripts share a weight and a voice. Each has its own scale of nine roles, from display to caption, and Arabic gets taller line heights so its marks never collide.

Rebuilt in code from the Aajil tokens

The same roles in each script, in the current theme. Switch to Arabic to see its own, taller line heights.

Space and shape

Spacing steps by four pixels, from 4 to 96. Corners, borders and shadows each have a short scale, so a card, a field and a modal clearly belong together.

Rebuilt in code from the Aajil tokens

Spacing on a 4-pixel base, with the radius scale, in the current theme.

Icons

Two styles on one 24 px grid: bold for emphasis and outline for quiet interface. The library holds more than 18,000 icons in 57 categories, so the set mixes common interface icons (search, settings, lock, calendar, share) with ones for the product itself: credit cards, accounts, wallets, invoices, shipments and property.

From the Aajil icon library

The Aajil icon library as a reference sheet: six of its 57 categories, each icon in bold and outline, in the standard black and white.

Tokens

Two layers, so a theme is a switch and each script keeps its own scale.

Primitives hold raw values: yellow 400, black 900, 16 pixels. Semantic tokens name them by job: the brand background, the default text, the subtle border. Components only use the semantic layer and never touch a raw value, so a change lands in one place and travels to every component.

Themes and scripts are handled differently, on purpose. A theme is a mode: the Semantic collection has a Light and a Dark mode, and 38 of the 44 semantic colors point at a different raw value in dark. A script is not a mode: typography holds two parallel groups, Arabic and English, each with its own family, sizes, weights, line heights and letter spacing, and every component is built twice, once per language, so Arabic is designed rather than mirrored. On the canvas this reads simply: a component has a Dark Version property and a Breakpoint property, and changing language is a swap between its English and Arabic sets.

Dark mode swaps the values. Arabic gets its own design.

A name reads from the general to the specific: color.background.bg-brand-hover is a color, for backgrounds, in the brand family, in its hover state. Each token keeps the name it has in the Figma file, where the variables panel shows a role per row, a value for each mode, each pointing at a raw value. The Primitives collection holds 153 variables and the Semantic one 134.

The variables panel of the Aajil Figma file

The variables panel of the Aajil Figma file: the Semantic collection, its groups, and the background roles in light and dark. A few rows are shown.

Ready for code

Implementation came after my time, so the tokens were shaped for it: in the W3C design-token format a token keeps its name, its type and its description when it leaves Figma. A role points at a raw value, and dark mode is one extra line on the same token: the component never changes.

Rebuilt in code from the Aajil tokens

Three roles and the raw values they point at, written in the W3C design-token format for the handover. Dark mode is an extension on the same token.

Shaped for financing

Where generic components became Aajil’s: verifying a business, applying for credit, reading the numbers.

A stepper is common. A credit application in Arabic is not. These are the parts we shaped around Aajil’s work.

Verify

Every session that touches money starts with a one-time code. The code field comes in four sizes and seven states, from empty to error, for six- or nine-digit codes, grouped or apart. Each product picks the one that fits its screen.

From the Aajil Figma library

The code field and its seven states, from the Figma library.

Apply in steps

A credit request is long, so the stepper names each step and shows what’s done, what’s next and what needs fixing. Seven styles, from a compact line to full cards, cover the website, the apps and the dashboards. In Arabic, progress runs right to left.

From the Aajil Figma library

Two of the seven stepper styles, from the Figma library.

Read the numbers

Finance teams live in tables. Ours put the riyal beside every amount, give every status a word as well as a color, and keep search, filters and the main action in one row above the data.

From the Aajil Figma library

A credit table from the Figma library: riyal amounts, worded statuses, search, filters and paging. Sample data.

The component library

About forty families, every one in Arabic and English.

Actions, forms, navigation, feedback, data and overlays: what a product needs, built twice, once per language, and themed through tokens. The button is the deepest: eight colors, five sizes, four states, with or without icons, 440 variants per language. A product team picks a color and a size; the system handles the rest.

One component, web and app

Web and app share the same tokens, and each component carries a Breakpoint property, so the same component fits a desktop or a phone screen. Where a pattern behaves differently on a phone, the family has its own mobile version: tabs, navigation that folds into a mobile menu, tables that become cards or lists, and modals that become bottom sheets or full-screen views. The mobile versions read the same tokens, so a change to a role reaches both.

Other components

Actions Button groups in nine layouts; badges in seven themes, two sizes and five types, with a dot, an avatar or a loader.

Forms Text fields in seven layouts; selects in seven; code fields in four; and upload, search, phone, number, date and time fields, toggles, checkboxes and sliders.

Navigation Tabs in seven types, each with a mobile version; breadcrumbs in six types; navbars, sidebars, mobile menus, pagination and the stepper.

Feedback Alerts in four types and five colors; progress bars in six colors; toasts in nine types; banners, spinners and skeletons.

Data Tables with sortable columns, riyal amounts, status badges, search, filters and paging; cards in nine types; lists, timelines and ratings.

Overlays Modals in eleven types; dropdown menus in sixteen; popovers; tooltips in four positions; drawers and speed dials.

From the Aajil Figma library

Buttons, fields, navigation, data, feedback and overlays composed from the Figma library; the first board covers inputs, actions and navigation.

From the Aajil Figma library

Data, feedback and overlays: a card, a credit table, a verification modal, a dropdown, an alert, a toast, a progress bar and a tooltip, from the Figma library.

How the teams use it

A system only counts when people use it.

The system lives in a Figma team library, so any designer can pull it into any file. The web app and the mobile app moved their designs to it, and the names are ready for engineering to build from. The file documents itself: it opens with an introduction, a getting-started page and a guide to changing tokens, and every component page starts with an About frame on what the component is for and when to use it.

A change starts with a token. Adjust the brand yellow once, and it reaches every component in the library and every screen built from it.

  1. Figma libraryComponents and tokens
  2. TokensNamed by role
  3. CodeNames match the front end
  4. ProductsWeb app, mobile app
How one change travels through the system.

Learnings

What did I learn?

How to build a design system that scales, in three parts.

Tokens in layers. Raw values, then roles named by job, so a decision is made once and every component inherits it.

Variables for themes and languages. Light and dark as modes on one set of names, offered on every component as a Dark Version property; Arabic and English as parallel type groups and separate component sets, swapped like any instance, because a script needs its own scale and layout, not a switch.

One component, two platforms. Knowing when a component should become two: tabs, navigation, tables and modals got mobile versions that share the tokens but behave the way a phone needs.

That structure is what made one month enough: it left the time for what makes Aajil, Aajil, Arabic on its own terms, the money moments and the brand.

What went well?

Clear ownership let three people move in parallel.

Adoption. The web app and the mobile app moved their designs to the library, and new features start from it.

Dark mode. Naming colors by role paid off: 38 of the 44 semantic colors point at a different raw value there, so a component’s dark version uses the same names, not new colors.

What could be improved?

Three things, if I built it again.

Contrast from day one. Three text colors in the Figma file fall short of WCAG AA’s 4.5:1 on white: brand yellow text (2.7:1), success green (3.2:1) and muted gray (2.2:1). This page already draws them one step darker (yellow 700 at 4.6:1, green 700 at 5.0:1, gray 500 at 5.2:1, with subtle gray moved to 600 to keep the order). I’d check contrast when the tokens are defined, not after, and move the library to the same steps.

Adoption from week one. I’d measure adoption from the first week.

Code parity. I’d ship the coded components alongside the library, so design and code never drift.

What makes a design system Arabic-first?

Arabic is designed on its own terms, never as a mirror of the English. At Aajil that meant every component exists in Arabic and English, each in light and dark; each script has its own type scale of nine roles, with taller Arabic line heights so its marks never collide; and one family, IBM Plex Sans and IBM Plex Sans Arabic, gives both scripts a shared weight and voice. Tokens sit in two layers, 153 raw values and 134 named by role, so a theme changes only what sits underneath. Direction is designed too: in Arabic, the stepper’s progress runs right to left.

Need one language across your products?

If your products look different in every corner, or Arabic always comes second, I’d like to hear about it.

Image