Design system
One system.
Four interfaces.
Three markets.
The design language behind the Magic Transports freight platform — defined in Figma, shipped as code tokens, and running live across a shipper portal, a carrier console, a driver mobile app, and an operations back-office.
How it works
From Figma to production
Design decisions live in one place and flow outward. Nothing in the product is hand-picked — every colour, size and radius resolves to a named token.
Figma library
Colour & text styles, logo components and 9 guideline boards define the brand foundation.
CSS custom properties
Tokens land as :root variables — one contract every surface imports.
Shared primitives
Buttons, badges, fields, cards and tables are built once from those tokens.
Four interfaces
Shipper, carrier, driver and operations compose the same primitives — so they always agree.
Foundations
Colour
Two layers on purpose. The brand palette is the identity (print, deck, marketing). The product palette is the UI system the apps run on — tuned for interface contrast and long screen sessions. Click any swatch to copy its value.
Brand palette — identity
Product palette — brand & surface
Text ramp
Semantic — shipment lifecycle states
Foundations
Typography
Plus Jakarta Sans carries the interface — geometric, high x-height, legible at 12px in dense freight tables. DM Mono is reserved for identifiers: shipment IDs, plate numbers, tax registrations, timestamps. Numbers that must be scanned, never guessed.
44 / 48 · 800
30 / 36 · 800
22 / 28 · 700
17 / 24 · 700
15 / 24 · 400
13 / 20 · 400
13 · DM Mono
10.5 · .09em
Foundations
Space & radius
A 4px base grid keeps dense operational screens rhythmic. Radii stay soft but never playful — rounded frames are part of the brand's graphic language.
SPACING SCALE
RADIUS
ELEVATION
Foundations
Iconography
Monoline, rounded, 1.6px stroke on a 24px grid. Freight-native — the vocabulary of the domain, not generic UI clip-art.
Components
Status & badges
The lifecycle a shipment moves through — one visual language across all four surfaces, so a status means the same thing to a shipper, a carrier, a driver and an ops controller.
Components
Forms
Region-aware by design — the same field renders GSTIN in India, UEN in Singapore, or a Trade Licence number in the UAE.
Components
Data display
Freight is a numbers business. Stat cards for the glance, tables for the work — IDs always in mono so they can be read aloud over a phone call.
Delivery
Token export
The single source every surface consumes. Copy as CSS custom properties, JSON, or Tailwind theme config.
Delivery
The four interfaces
Every screen below is built from the tokens and primitives on this page — and adapts its currency, tax logic, identity fields and language by region.
Shipper
Book & quote across road, air and sea. Live tracking, invoices, documents.
Web · fleet operatorsCarrier
Load board, dispatch, fleet & driver compliance, settlements.
Mobile · driversDriver app
Offline-first trip execution, POD capture, earnings — multilingual.
Web · operationsOperations
KYC, oversight, rate matrix, reconciliation, fraud & intelligence.
Designed and built by Praveen Kumaar · Figma foundations → CSS tokens → four shipped interfaces.
Design prototypes with mock data — no backend.