Run-On
Navigating public transport, particularly bus transit, can be stressful. So when making it to work on time can mean the difference between a promotion and the ire of your boss, you want to be able to travel with maximum efficiency. Run-On is an app that makes bus travel easy by giving the user all the information they need to make sure their travel is as seamless as possible.
My Role
Solo UX/UI Designer
UX Research
Information Architecture
UI Design
Usability
Deliverables
User flows
Wireframes
Low-fidelity prototype
Research results
High-fidelity prototype
Tools
Figma
Google Forms
Zoom
Maze
Timeline
3 weeks
Overview
Problem Statement
Confusing stops with multiple bus lines and inconsistent timings of buses makes it hard for people to catch their bus efficiently and on time.
Users and Audience
The thousands of users that can use their mobile devices to track the buses at the bus stops. This app is geared towards those who use public transit in the city the most, the everyday users that need it to get through stops such as the chaotic Washington and State stop, which has 7 bus lines running though it.
Solution
Create an app that makes sure users make it to their bus on time with all the information they need regarding delays or bus lines.
Process
Throughout this project, I made use of the double diamond process to guide me through the process. The Double diamond process contains four parts:
Discover in which I established and tested hypotheses, uncovered user needs, collected and analyzed data, and established problem statements.
Define in which I decided what the problem will solve.
Develop in which I tested solutions, and established branding and style.
Deliver in which I completed the final product.
Goals
These were the main goals of the application:
To create an app that allows people to catch their bus on time.
To remind the user to catch their bus.
To allow people to book tickets.
Discover
The client is a transportation agency for a midsize metropolitan area in the Midwest. The city has a network of public buses, for which they currently list the expected bus schedule on their website and post it at each bus stop. However, in practice, expected bus times are rarely accurate, as factors such as traffic traffic, time-consuming but necessary accommodations for passengers using wheelchairs, or taking a bus out of service for maintenance can impact the schedule. This results in a frustrating experience for passengers who frequently use the bus system to complete time sensitive tasks.
Competitive Analysis
In order to better understand how transit apps work in the market currently, I downloaded the following apps to analyze: City Mapper, and Moovit. I used a SWOT analysis as well as a general observational task analysis on each of the apps.
Strengths
Stations and routes are marked clearly on intuitive map.
Convenient access to nearby stations.
Well organized for favorites.
Lines are shown with visible and intuitive statuses.
Weakness
Not enough contrast in some parts.
Annoying ad placement.
Unclear what some words mean such as “modified service”.
Multiple pop- ups.
Opportunities
Easier/ gradual introduction to the system.
Improve contrast in text.
Unintrusive/ impermanent ad placement.
Threats
Well organized bus route maps.
Strengths
Bus times for stops are displayed clearly.
CO2 emission tracking.
No pop ups, allows for autonomous navigation.
Settings are easy to access and well organized.
Weakness
Large, unnecessary, intrusive, take me home function.
Small text with unclear hierarchy.
Unintuitive map, hard to set start and location.
Elements too close together.
Opportunities
Larger text with more color use for heirarchy.
Intuitive and easy to use map for stops and routes.
More measured use of space.
Threats
Clear and informed description of bus times at stops.
Call an Uber function.
Quantitative Research
To find out what the exact pain points and user experiences were like with the current state of bus transit, and to get an idea of the user base, I conducted a survey using Google Forms. The survey was open to people of all demographics, conditional upon the fact that they had used bus transit in the past. The survey entailed questions regarding demographics, why users choose public transit, and what obstacles they face in their commute.
Key Takeaways:
The problem starts at home. Many people found that leaving home in time to catch the bus was just as difficult, particularly for students who had irregular class times and sleep schedules.
Bus times are not tracked accurately enough to be useful. Buses often do not show up at the times that are designated, making it difficult to rely on them.
Buses arrive at different times weekly at inconsistent intervals. Bus times varied, and as a result getting to the stop on time was immensely difficult for consistent use.
Most bus riders are regular users who take Public transport to school or work. Students and employees make up the vast majority of people that use bus transit. They use bus transit regularly, and oftentimes more than weekly.
Qualitative Research
To get a more in depth understanding of our findings from the survey, I opted to use online interviews. I used zoom to conduct these interviews, which lasted in between 20-30 minutes each. The participants were recruited from these that responded to the survey with further contact information, as well as those from my personal circle. The participants ranged from 20-40 years old, with varying levels of ability and profession.
Personas
Define
User Stories
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.
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.
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.
As a bus rider, I want the ability to know when to leave my home so that I can make it to my bus in time daily for my routine.
User Flow
These were the initial user flows I drew up to build a wireframe of my project around. The amount of features increased once I developed my wireframe, but these flows served as the basis for my design.
Site Map
This site map was the culmination of all the features I thought to add as I was building off of my user flows. The skeleton it provided was the perfect base for me to flesh out with features. As i took reference from other social media sites the amount of features I could include to improve the experience grew exponentially.
Wireframe
This is the initial prototype I made using Figma. By following the blueprint laid out by the user flow and site map, I added the features required to accomplish the objectives laid out in the user stories.
