Put the stop
before the ride style.
The team’s prototype testing called for moving “Add Stop” earlier. The route is now assembled before the vehicle and preference decisions.
Route → Preference → ReviewChicago / Make it yoursTeam project · Cross-device UX / UI
CHECKER
Every ride.
A little more city.
A connected taxi experience for the journey
and the discoveries along the way.
01
THE CITY
IS YOURS.
THE CITY
IS YOURS.
01 / The ideaA connected city journey
Getting there
is part of the visit.
A taxi can connect more than two points on a map.
Checker explores how visitors could plan a route, discover places during the ride and keep those discoveries for later.
I contributed across the original undergraduate team project, with my primary focus on UI/UX. This revisit connects the phone, passenger screen and driver screen through one shared journey.
- My contribution
- Contributed across phases
Primary focus: UI/UX
Original credit: Interactive Designer - Project
- Undergraduate team concept
Chicago taxi experience - This edition
- Three touchpoints, distinct priorities
/ One trip. Different perspectives.Passenger view
Discover in the cab. Find it again on your phone.
02 / The design directionDocumented team testing
Fix the order.
Focus the attention.
Two observations in the archived team presentation give this revisit its priorities.
Put the stop
The next move
comes first.
The source asks for driver-only tasks and larger type. Discovery stays on the passenger screen, while the driver view leads with the next manoeuvre.
Manoeuvre → Next stop → Trip contextEvidence & attribution ＋
These findings come from the archived team presentation. Survey sample size and individual participation in testing still need confirmation. The revised interfaces have not undergone a new study. Driver attention and safety remain unvalidated design hypotheses.
03 / Try the experienceAn interactive concept
One journey.
Three perspectives.
Plan on the phone. Carry it into the cab.
Add the museum stop, choose a ride style and review the request. Switch to the passenger screen to save a place, then find that same place on the phone. The driver screen reflects the planned route.
All locations, ETA and fare values are demonstration content. The map is schematic; no ride is requested.
A simplified, local demonstration. No account, payment or external service is connected. Changes reset when the page reloads.
04 / The interfacesPlan, choose, review
Your route.
Your rhythm.
The trip summary keeps the route, optional stop and ride preference in view before the request.
Interface collection / tap to enlarge
05 / Behind the wheelA different attention budget
Less to scan.
A clearer next move.
A large direction cue and distance lead the driver display. A shared identity does not mean every screen should show the same information.
01 Lead with the next turn02 Keep the next stop visible03 Separate parked and driving states
06 / Looking backA proposal, with a next step
A connected journey.
With room to test.
Design decision
Design the handoff, not just the screen.
The revisit makes saved places and trip preferences consistent across touchpoints. Taxi yellow and checkerboard details connect the identity while each device gets its own information hierarchy.
Next validation
Follow the journey across devices.
I would test whether passengers can find a place saved in the cab on their phone, and whether adding a stop causes backtracking. The driver hierarchy needs evaluation in a simulator.
Project & image credits ＋
Undergraduate team project. I participated in all phases, primarily UI/UX. Research and service strategy were team efforts; no sole ownership is claimed. Map graphics, names, fares and trip details are illustrative. The 2026 portfolio revisit uses AI-assisted interface refinement and presentation production under my direction. No launch or measured usability improvement is claimed.