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.

BusyBus wordmark on a yellow city map, with a dashed bus route leading to a cartoon bus, beside a phone showing the Washington & State stop screen
BusyBus wordmark above a yellow city map with a dashed bus route and a cartoon bus, and a phone showing the Washington & State stop screen

The 30-second version

Role

Research, UX/UI, front-end build

Company

Bloc UX/UI program (coursework)

Timeline

2018

Tools

Google Forms, paper prototyping, HTML/CSS

Problem

Riders couldn't trust bus apps to tell them when the bus was really coming.

The 30-second version

Role

Research, UX/UI, front-end build

Company

Bloc UX/UI program (coursework)

Timeline

2018

Tools

Google Forms, paper prototyping, HTML/CSS

Problem

Riders couldn't trust bus apps to tell them when the bus was really coming.

The 30-second version

Role

Research, UX/UI, front-end build

Company

Bloc UX/UI program (coursework)

Timeline

2018

Tools

Google Forms, paper prototyping, HTML/CSS

Problem

Riders couldn't trust bus apps to tell them when the bus was 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

Paper prototype, home screen: search, a delay alert, the map and nearby stations with their bus numbers
Home screen
Paper prototype, selected stop: Washington and State with a delay alert and the routes that stop there
Selected stop
Paper prototype, selected route 60: the route on the map and its next stops with arrival times
Selected route

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

First iteration of the BusyBus stop screen: colored route badges and a close (X) button
Iteration 1
Second iteration: yellow header with a back arrow and dark route badges
Iteration 2
Third iteration: the same layout with tighter type
Iteration 3

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.

Brand2 colors
01Copy
Yellow
#FFCC00
RGB255 204 0
02Copy
Ink
#282C37
RGB40 44 55
Directions3 colors
03Copy
Eastbound
#0075FF
RGB0 117 255
04Copy
Northbound
#8F00FF
RGB143 0 255
05Copy
Southbound
#50B637
RGB80 182 55
Status2 colors
06Copy
Reroute
#E74D72
RGB231 77 114
07Copy
Out of service
#92949A
RGB146 148 154

Hiring? Let’s talk.

hi@nshanpetrosyan.com

Click to copy

Hiring? Let’s talk.

hi@nshanpetrosyan.com

Click to copy