OPERATIONAL PRODUCT · FULL STACK · INFRASTRUCTURE
A web/PWA platform for airport-transfer operations where passengers, drivers, and the operations team work through connected role-specific interfaces and one controlled order lifecycle.
Business problem
Airport-transfer operations require more than an order form: the product needs separate permissions, lifecycle states, assignment rules, pricing references, notifications, and controlled exception handling.
Solution
A web/PWA platform for airport-transfer operations where passengers, drivers, and the operations team work through connected role-specific interfaces and one controlled order lifecycle.
Responsibility
My responsibility spans product workflows, full stack implementation, and evidence-led delivery.
Roles, user flows, truthful states, and MVP boundaries.
APIs, business rules, Prisma models, migrations, and audit.
Passenger, driver, operations, and admin UX.
Tests, builds, smoke checks, deployment, and recovery evidence.
15 · Public interfaces
Screens from an explicitly marked demo environment. All values are synthetic; no production data was used.
04 · Privacy reviewed
User roles
SYSTEM OVERVIEW
Separate roles. One shared lifecycle.
Passengers, drivers and operations work with the same order through separate interfaces and permissions.
Hover or focus to preview. Click to keep the selection. Click again or press Escape to clear.Tap a node to explore its connections. Tap it again to clear the selection.
Passenger
Direction
To or from the airport
Address and point
Passenger-readable stops
Time and party
Date, time, passengers
Create order
Server validation and lifecycle
Status
Waiting, assigned, in progress
Completion
History and notifications
Driver
Availability
Working state and zone
Order board
Eligible scope only
Accept
Assignment validation
Pickup
Allowed transition
In progress
Operational state
Complete
Finance snapshot and audit
Normal work remains self-service. Dispatcher and administration surfaces provide visibility, configuration, and controlled exception handling.
User-facing states are derived from server order state, driver assignment, and audit events; the UI does not invent decorative lifecycle states.
Created
Validated order
Waiting for driver
Available to eligible drivers
Driver found
Assignment confirmed
Pickup
Driver approaches
In progress
Active route
Completed
Final state and accounting
Key decisions
Infrastructure
Production delivery separates frontend, backend, and data responsibilities, verifies release identity, and maintains reproducible recovery steps.
Separated role interfaces share application contracts, a relational model, and bounded integration adapters.
Passenger, driver, dispatcher, and admin interfaces.
Orders, rides, roles, assignments, and transitions.
Relational models, migrations, audit, and finance ledger.
Notifications, Telegram gateway, and provider boundaries.
Build gates, release identity, and operational runbooks.
Passengers choose an address and airport point. Zones remain internal units for matching, positioning, and tariff logic.
The finance layer uses accepted ride snapshots and an append-only ledger instead of recalculating historical values in the interface.
Public boundary
The public case explains the product without exposing operational data or sensitive configuration.