Bloc UX/UI program (coursework)
·
UX/UI
·
2018
BusyBus
A bus app concept built around what riders actually asked for: knowing when the bus is really coming.
Brief
As Bloc's UX Challenge, I designed a transit app from research through a working screen. I surveyed 20 people about how they ride and plan, and the complaints were consistent: schedules that run behind, apps that don't show delays, and too much going on. One rider put it simply: "Simple bus information, nothing else."
Approach
I studied Transit and Google Maps, then made a call against the trend. My research showed that live bus tracking was unreliable, so I dropped it. The app shows what riders can act on instead: whether a bus is on time or delayed, and by how long.
User stories set the core features: nearby stations, arrival times, delays, and alternate routes.
I tested a paper prototype with three people on three tasks. Two problems stood out. Bus numbers at nearby stations were hard to pick out. And the close (X) button didn’t read as a way back: two of the three testers reached for the browser’s back button instead.
Paper Prototype
Three rounds of visual design followed. Bus numbers moved into heavier, easier-to-spot badges, the X gave way to a back arrow, and the last round grouped routes by direction.
Iterations
Outcome
The final screen gives bus numbers more room and a clear hierarchy. Routes are grouped by direction, and the list flags delays, reroutes, and out-of-service routes with the time they resume. The X became a back arrow.
I built it in HTML and CSS and published it on GitHub Pages.
Final screen
The live build, scrolling from arrivals to a reroute to routes out of service.
Color Palette
Yellow for the brand, one color per direction so riders can scan routes at a glance, and two status colors for reroutes and stopped service.









