Time, vehicle, and payment are handled as three reviewable steps.
SpotON
Parking, minus the friction.
A parking companion that takes drivers from live availability to a reserved spot, QR pass, vehicles, guest access, and payments in a few calm steps.
My roleProduct redesign, architecture, and Flutter development
Driver journey01 / 07
Use arrow keys · swipe on touch · tap the screen rail
Live navigation
The journey behind a confident arrival.
Audience
Drivers who need to find, reserve, enter, and manage parking with minimal distraction.
Delivered scope
End-to-end mobile redesign covering discovery, booking, passes, vehicles, guests, and preferences.
Defining constraint
The product must surface price, distance, time, and availability without becoming another dashboard to study.
The portfolio documents the connected discovery-to-pass experience.
Light and dark experiences retain the same navigation and priority cues.
Verified evidence · The numbers reflect the designed booking flow and implemented interface coverage.
Remove uncertainty from the drive.
Parking apps often expose the system instead of helping the driver. The key was reducing choice at the right moments while keeping availability, distance, price, and timing visible.
Own every turn from search to park.
Product redesign, architecture, and Flutter development
03 / Route choices
Signals that guide the shortest path.
- 01
Made the best next action dominant on every screen.
- 02
Turned booking into a short, reviewable three-step flow.
- 03
Kept maps, lists, passes, vehicles, and guest access inside one navigation model.
- 04
Created a shared visual system that remains crisp in light and dark modes.
System architecture
Every screen answers the next driving question.
The interaction system is organised around progress toward a confirmed, usable parking pass.
Locate
Availability, distance, and price help the driver choose without opening several tools.
Reserve
A short sequence captures only the decisions required to secure the spot.
Arrive
The QR pass, directions, vehicle, extension, and cancellation remain together after booking.
04 / Route plan · SDLC
Four waypoints to an effortless arrival.
Audit the drive
Removed decisions that distract a driver from finding and securing the right spot.
Prioritize context
Balanced availability, distance, duration, and price without turning the screen into a table.
Design the flow
Compressed reservation into three calm, reviewable decisions with a clear final check.
Build for return use
Connected passes, vehicles, guests, payment references, and preferences around repeat visits.
05 / Arrived
A complete demo-ready mobile experience with persistent local sessions, booking states, QR passes, vehicle management, and accessible appearance controls.
Next validationThe next study should compare completion time and booking errors against the original multi-screen flow.FlutterDartResponsive UIMotionProduct UX