← INDEX

CASE 03 · PRODUCT · FULL-STACK · UX

Taxino

Intercity ride-sharing that fills the empty seats between cities.

YEAR
2025
ROLE
Product design, full-stack development
STACK
React · Node.js · Database & auth · Maps
Taxino, exploded technical cover plate
CASE 03 · EXPLODED VIEW
00

BRIEF

Cars travel between cities with empty seats

Intercity travel runs every day on half-empty cars while other people wait for buses. Taxino's brief: connect the two sides with the least possible friction, and make trusting a stranger feel reasonable.

  • N-01Trust identified as the real product; matching is just the mechanism.
01

STRUCTURE

Three flows, no detours

The product was reduced to three flows before any interface existed: post a trip, find a trip, book a seat. Every screen had to belong to one of them. Search was structured around the only two questions that matter: from where, to where, when.

FIG 01-A · TRIP SEARCH RESULTS
FIG 01-B · BOOK-A-SEAT FLOW
  • N-02Any feature that served none of the three flows was cut from scope.
02

SYSTEM

A route you can read at a glance

The interface system centers on the trip card: origin, destination, departure, seats left, driver. Seat availability is shown as discrete units rather than numbers, and driver profiles carry the verification and history that make booking feel safe.

ROAD#FFFFFFASPHALT#101418GO#14B87AROUTE#0E63F4AaGEOMETRIC SANS, NUMERIC-FIRSTCASABLANCA → AGADIRPRIMARYGHOST
FIG 02 · PLATFORM SYSTEM
  • N-03Seats drawn as objects, not counts: three circles read faster than a 3.
03

CRAFT

States that answer before the user asks

The craft pass went into product states: the live route trace as a trip fills, booking confirmations that read instantly, empty states that tell a new city what to do first. Motion is small and purposeful, a booked seat clicks into place.

  • N-04Every async action has a designed pending, success, and failure state.
04

BUILD

Matching, booking, and both dashboards

Full-stack build: authentication, trip publishing, search with route matching, seat booking with conflict handling, and dashboards for both drivers and passengers. The booking engine guarantees a seat is never sold twice, the kind of problem that is invisible when solved.

  • N-05Concurrency handled at the data layer: two users cannot book the last seat.
05

SHIPPED

From empty seat to shared trip

Taxino ships as a complete two-sided platform: post, find, book, ride. The whole machine you just watched assemble runs on every search.

FIG 05-A · TAXINO, PRODUCT
FIG 05-A · TAXINO, PRODUCT
  • N-06Platform designed to add cities as data, not as development work.

A working platform where posting a trip, finding one, and booking a seat each take under a minute, with the trust signals both sides need to say yes to a stranger.

REACT · NODE.JS · DATABASE & AUTH · MAPS
TAXINO · PROCESS
000%

GALLERY

Taxino, up close

FIG 01-A · TRIP SEARCH RESULTS
FIG 01-B · BOOK-A-SEAT FLOW
ROAD#FFFFFFASPHALT#101418GO#14B87AROUTE#0E63F4AaGEOMETRIC SANS, NUMERIC-FIRSTCASABLANCA → AGADIRPRIMARYGHOST
FIG 02 · PLATFORM SYSTEM

NEXT · CASE 04

Tasstify