Create an app that can ...

• Track Bus Routes
• Track Delays
• See Stop Schedules

Design Process‍

1. Discovery Phase

Quantitate Research - User Survey

I created a public transportation survey that allowed me to get insight on the demographic using apps now for their travels and gain insight on some of the pain points that they encounter.

Key Findings

• 60% of users plan their trip 1-8 hours before.
• 40% of users have trouble navigating current transit apps. (on a scale of 1-10, users were asked how easy it is to use their current app of choice for public transportation)

User Persona:

Once I gathered Data from the user surveys, I went ahead and created a user persona to help begin designing mock-ups for potential solutions.

Define Phase

HIGH-PRIORITY USER STORIES

With a competitive analysis and user persona done, I started to build out what the High-Priority user stories should be. I settled with these three in mind.

1. As a bus rider, I want to know when my bus is arriving at the Washington & State bus stop, so I can calculate how much time I have to reach the bus stop.
2. As a bus rider, I want to know the next bus arriving at the Washington & State bus stop, so that I don’t rush to the bus stop if it is not my bus.
3. As a bus rider, I want the ability to view future arrival times for any of the seven bus lines (serving Washington & State), so that I know when my bus arrives.

User Flows / Information Architecture

Next, we can start working on the user flows and how might a user get to their desired solution.

Develop Phase

Usability Testing

To get a better understanding of what needed to be iterated on I decided to use Maze for Usability testing. I received over 10 responses.

Main Takeaways

• 80% of users misclicked when attempting to track a specific line.
• 30% of users were not able to complete the second flow of following up on the Washington and state line
• 50% of users did not think the colors were easy to see in dark mode