TripLink Design System
One unified design language for Passenger, Driver, and Operations — built for trust, safety, and clarity before any feature development begins.
Cover & Design Principles
Every subsequent phase consumes this system. Priority: Usability → Trust → Safety → Clarity → Accessibility → Consistency → Scalability → Visual polish.
Approval gate
STOP after Phase 0. Do not begin Phase 1 — Registration & Identity Verification — until this design system is reviewed and approved.
Full documentation lives in design-system/docs/ and README.md.
Foundations
Color, type, space, radius, and elevation. Brand purple is used strategically — never flooded.
Brand — Deep TripLink Purple
Accent — TripLink Orange
Semantic
Typography — Inter
Spacing — 8px base
Radius (restrained)
Elevation
Design Tokens
Runtime CSS variables in tokens.css; machine-readable source in tokens.json. Never invent arbitrary values.
| Category | Prefix / examples | Use |
|---|---|---|
| Color | --tl-purple-*, --tl-color-primary | Brand, semantic, aliases |
| Type | --tl-text-h1, --tl-fw-semibold | Hierarchy & buttons |
| Space | --tl-space-1 … --tl-space-8 | Layout rhythm |
| Motion | --tl-duration-fast, --tl-ease-standard | Purposeful, reduced-motion aware |
| Z-index | --tl-z-safety, --tl-z-sos | Safety above chrome |
| Map | --tl-map-marker-*, route widths | Consistent map language |
Business state colors
Components
Reusable building blocks first. Interactive components support default, hover, focus, pressed, selected, disabled, loading, success, and error.
Buttons
Inputs
Password strength: Strong
OTP
Selection & controls
Badges, avatars, alerts
Product components
Seat selector
Held in escrow until arrival is confirmed.
Passenger App
Mobile-first. Primary action: Find a Travel Buddy. Nav: Home · Trips · Messages · Activity · Profile.
TripLink
Where are you travelling?
Suggested matches
Trip Pass
Driver App
Mobile-first. Primary action: Create Trip. Nav: Home · Trips · Requests · Messages · Profile.
Requests
Verification
Under review
We’re reviewing your identity, vehicle and screening. This usually takes 24–48 hours.
- ✓ Phone verified
- ✓ Identity documents
- … Vehicle inspection
- ○ Background screening
Safety & Live Trip
SOS is highly discoverable, requires intentional activation, and severity is never color-only.
Live map language
SOS control (press & hold demo)
Press and hold to arm SOS
Confirm emergency alert?
TripLink Safety and your emergency contacts will be notified with live location.
Severity levels (label + color + icon)
Safety panel (active trip)
Payments & Booking
Escrow must never be ambiguous. Always explain hold → release → refund states in plain language.
Trip lifecycle timeline
Admin Operations
Desktop-first sidebar: Overview · Operations · People · Verification · Safety · Finance · Trust · Analytics · System.
Responsive Variants
Mobile highest priority for apps. Desktop highest for Admin. Breakpoints: 480 · 768 · 1024 · 1280 · 1440.
| Surface | Priority | Patterns |
|---|---|---|
| Passenger / Driver | Mobile highest | Bottom nav, bottom sheets, 44px targets, safe-area, one-handed SOS |
| Tablet | Adaptive | Flexible cards, expanded maps, 8-column grid |
| Admin | Desktop highest | Sidebar, dense tables, filters, multi-column dashboards, ops maps |
Empty, Loading & Error States
No major feature ships without these states defined.
Prototype Standards
Clickable flows must consume system components. See design-system/docs/09-prototypes.md.
| Flow | Surface | Key states |
|---|---|---|
| Passenger registration → verification | Passenger | OTP, pending, approved, rejected |
| Find Travel Buddy → book → pay → pass | Passenger | Empty matches, escrow held, payment fail |
| Pickup QR/OTP → live trip → SOS → arrival | Both | Mismatch, deviation, SOS confirm |
| Driver create trip → request approval → execute | Driver | Draft, published, awaiting, completed |
| Admin verification · live monitor · safety alert | Admin | Queue, critical, resolve, escalate |
Developer Handoff
Engineers implement against tokens and tl-* components — not one-off screen styles.
Phase 0 complete — awaiting approval
Next: Phase 1 — Registration & Identity Verification, only after explicit approval of this design system.