For our next step, we conducted usability tests in an effort to determine the strengths and weaknesses of our MBTA app prototype. We talked to six different people, all in different professions; a couple students, a professor, a cyber security software employee, and a pharmacist. Participants ranged from 21 years old to 55 years old.

​

We started by asking our users a few questions:

How often do you travel on the MBTA?

Just from looking at our initial screen, what type of info do you think you will get from this app?

 

A few of the people we talked with were regular T-users while others were infrequent users. User’s initial impressions of the landing screen were that our app would be able to display scheduling information and provide alerts for the subway, commuter rail, and bus lines. It appeared that although they were only a tap away, some of the apps key features were not available for immediate interaction.

​

To test our prototype, users used one of our designers' computer with the prototype already pulled up. The first task we instructed users to complete was to view the bus map. A straightforward process requiring only two clicks, users had no trouble distinguishing between the subway, bus, or commuter rail in the hamburger menu and deemed it was clear that you could click on said sections to bring you to a coinciding page.

​

Of those we talked to, two were regular MBTA users. They questioned why our initial screen brought you to three main options; subway, bus, and commuter rail, instead of adapting to the preference or most used form of transportation of the user. An infrequent T-user brought up that they would like the ability to plan a trip or route without being in or near a station or stop. Using this feedback we decided to revise our app’s landing screen. Now, instead of opening to a screen with transportation options, users open to a map. At the top of the map is a search bar to allow the user the ability to search for a desired location and, using a step by step format, our app will direct the user to their destination using the fastest/closest MBTA methods. Further, we decided to include the users most recent destinations or most visited stations at the bottom. This provides the user, often a busy commuter traveling the same route, with a quick shortcut.

​

Next, we decided to rework the subway page. Users struggled with understanding what information was given on this page. They wished that there was a pin showing their location or the station in mind as well as where the train is located on the line. An easy fix but something our designers accidentally missed. With this, there was a comment on the look of the train capacity representation. Users felt that it was out of place, and they did not fully understand the information it was displaying. Our designers decided to revamp this to provide a more realistic / more informative graphic that matched the feel of the app. Now, the train capacity illustration displays crowdedness in the same way that people gauge it normally: by looking at the people through the windows. Without confusing color gradients or box heights, the illustration now provides a symbolic side view of the train and where it is crowded before the train pulls into the station. To further clarify this information, the feature will give the user information such as “More space in rear.”

​

In an effort to make our design unique, our designers initially choose a dark maroon accent color for tabs and other highlights within the app. After some feedback and careful consideration, we decided to switch our color to a dark blue. While this change was more pleasing aesthetically, our designers also wanted users to feel like they could trust our app when they add money to their accounts and navigate the city. Especially for people who don’t use the T-often, we want their travel experience to be easy and safe. Blue evokes all of these emotions. Additionally, while we originally hesitated to use a color that had a designated subway line, blue seems like the most appropriate because it is by far the least traveled line.

​

Finally, we ended with a few closing questions: What is your overall impression of the app? What is your favorite feature/function? Least favorite? Is there anything you feel like is missing? From these questions, we came to the conclusion that our app is on the right path, but seems a bit incomplete. There are a few important concepts (such as being able to plan a route ahead of time) that are missing and would make the experience much better. Users loved the ability to see how far away trains/ buses were and their ETA but were a bit confused whether or not you had to be in the geolocation of the station to view this or could search a specific station/stop.