VAYAVAYA Drive Club
Branding, UX & architecture

A premium driving platform, designed before it is built.

VAYA Drive Club connects passengers with verified professional drivers, and gives those drivers a club, a learning centre and a wallet. This blueprint fixes the brand, the flows and the architecture so later phases are pure execution.

Passenger app Driver appAdmin dashboard
4
User roles
43
Screens mapped
23
Tables proposed
8
Week roadmap
Live trip
In progress
Component preview — passenger active trip card
CO

Chinedu O.

Toyota Camry · Silver · Verified driver

4.9
  1. Lekki Phase 1Picked up 09:12
  2. Victoria IslandArriving shortly
Trip progress72%

Platform structure

Three products, one backend

Each shell below is a navigable UX blueprint with real layout and placeholder data — no business logic yet.

Passenger App
Book a professional driver, track the trip, pay from the wallet.
13 screens
Driver App
Onboarding, verification, requests, earnings, Club and Learning.
16 screens
Admin Dashboard
Verify drivers, run operations, money, memberships and the LMS.
14 sections

Design system

Tokens, type and components

Every colour, radius and shadow is a semantic token. Components below are the exact primitives the apps use.

VAYA Navy

#01004C — from the logo field

VAYA Gold

#FDD901 — from the V mark

White

#FFFFFF — type on navy

Navy soft

Navy tint — selected states

Success

Verified, completed, paid

Warning

In review, pending

Destructive

Rejected, failed, cancelled

Info

In progress, informational

Typography
Sora for display, Manrope for interface text.

Display / 36 Bold

Heading / 24 Bold

Subheading / 18 Semibold

Body / 14 Regular — legible at arm's length in a moving car, with generous line height and no decorative flourishes.

Caption / 12 — metadata and hints

Eyebrow / uppercase tracked

Buttons & badges
One primary action per screen.
VerifiedIn reviewRejectedTrip activeFounding memberDraft
Forms & inputs
Labelled, hinted, validated.

Used for trip updates and verification codes.

Licence number must be 12 characters.

Available for trips
Feedback & states
Success, error, empty and loading are designed, not improvised.

Platform deliverable

Architecture documentation

Written specifications live in the repository under /docs — journeys, screens, database, security and the roadmap.

docs/architecture.md
Platform, roles and technical architecture
docs/user-journeys.md
Every journey with success/error/empty/loading states
docs/screen-inventory.md
Complete screen list across the three apps
docs/database.md
Proposed tables, keys, relationships and RLS intent
docs/wallet-payments-notifications.md
Wallet ledger, payment and notification flows
docs/club-and-learning.md
Drivers Club and Learning Centre flows
Decisions we still need from you
Nothing below has been assumed anywhere in the design or documentation.
  • Pricing, fees and commission model
  • Payment provider selection and payout rails
  • Founding member price, cap and benefit list
  • Drivers Club entry requirements and tiers
  • Required vs optional courses, pass marks, certificates
  • Withdrawal limits and settlement timing
  • Launch cities and service catalogue
  • KYC document checklist and verification SLA
  • Cancellation and refund policy