Capital Metro is Austin’s regional public transportation provider and its official application “CapMetro” offers quick trip planning tools, online ticketing, real-time arrival information and other features to make transportation easy. The current issues that we are aiming to solve are based on our interpretation of the inconsistent or mismatch of information between Capital Metro’s online website and mobile application system, inaccurate time arrival and schedule information (does not always provide real time information), overlap of features that serve the same purpose, and features that are not intuitive for users.
Our team gathered information regarding the CapMetro mobile application through browsing and exploring through the application by using the system. Before we could decide on the sample size for our data gathering and the interview questions, we used this method in order to familiarize ourselves with the application system. We found that the application mainly allows users to do the following tasks:
After we had familiarized ourselves with the application system and what user tasks are made possible through the system, we decided to gather user data through conducting interviews to learn about how actual users of the application respond and interact with the system to gain a good idea of thinking about the redesign of the system for users. These interviews allowed for observation of user behavior, what steps and routine users take to interact with the application and their attitude and feeling toward their usage of the system.
12 Participants
10 Female Participants
2 Male Participants
Age: 20-27
Four types of occupation status:
The Work Activity Affinity Diagram (WAAD) was created as soon as we had completed the interviews.Then we took a close look into all the responses of each interviewee and created the activity notes based on what they had said. We had categorized the notes into clusters based on related themes that we identified from the interview data collected.
We did a walk-through of the Work Activity Affinity Diagram (WAAD) and extracted 14 representative work activity notes to develop requirements implied in the notes.
Our team decided to focus on four major user tasks to build our prototypes. These user tasks came from our hierarchical task inventory. We focused on user interacting with the main features of the applications. These four major user tasks are using the following features of the application: “Schedule”, “Trip Planner”, “Ticketing”, and “Next Departure”.
In order to view the schedule, the user first selects the schedule feature on the main menu bar. Then, user selects a type of service (Figure 1 - Schedule Home), enter the bus information by number or name such as “Downtown Austin” or “Lake Austin” (Figure 2 - Select route), and the date of service (Figure 3). Then, user views the schedule for that particular transit service by time and/or location (stop location) in a drop down menu. The estimated number of minutes for the bus to arrive at the stop location (Figure 4 - View Schedule) will be displayed.
To plan their trip, the user will need to enter both a starting and ending location (Figure 5). then the screen will display details related to the current trip (Figure 6), this includes a map of the route and a step-by-step guide. Both secondary-screens can be clicked on to expand their screen-size. Within the step-by-step guide, text descriptions of each event will include a clickable icon that will allow further details about the trip to be accessed by the user.
To buy tickets and use tickets, the user needs to go to the tickets homepage (Figure 8). If they are not logged-in and want to proceed, there will be a pop-up message to ask them either sign up for an account to sign in (Figure 9). After the user go through the sign up/in process (Figure 10, Figure 11), they can click the right-arrow icon to view different ticket packages (Figure 12) to choose the most appropriate one to add to the shopping cart.
Then the user needs to enter credit/debit card information (Figure 13) to add a new card by clicking the plus icon. The user can enter the card number either manually or just use the camera icon to scan the card. If the user successfully scan the card number, he/she will hear the crack of camera and the card number will automatically appear in the entry box. The user also needs to add a billing address for the card (Figure 14). After they add a card in their account, they can checkout and they will get a message if they successfully purchase tickets (Figure 15). Then the user can use the tickets purchased to scan the bar code (Figure 16) when they board the bus.
In the homepage, user can add a shortcut to quickly access the next departure time by choosing stop id and route number. To find the next departure times, the user first selects the next departure feature on the main menu bar at the bottom of the home screen with the bus symbol . Then the user will get into the main page of next departure (Figure 17). The user can choose to select the bus stop on the map (Figure 18), which is indicated by a bus with a circle . If the bus stop is selected, the icon will turn red . Or the user can choose to input the bus stop name manually (Figure 19), and the system will automatically detect a list of names of possible bus stops. After the user has chosen the bus stop, the user can touch the check mark to confirm his or her selection, and the list of next departure time will show up (Figure 20).
After we built our prototype, we took a careful review on every page first to make sure the links and interactions work well. Then we recruited a participant that resembled the characteristics of our primary persona.
The test took about 10-12 minutes. As the participant was looking at the screen interacting with the application, team member took notes on their responses to the questions as well as their general behaviors. During the 5 minute free interaction part of the test, one difficulty that user had was figuring out what each symbol on the main menu meant (what feature is represented by each symbol). The picture symbols did not seem intuitive for user to figure out what features they represented so the participant asked during the pilot testing where she needs to go to plan out a trip to go somewhere. She clicked on a few options before finding the next departure feature on the homepage main menu.
After interacting with the application for five minutes, the user was able to identify the main features that were made available through the application and was able to complete the tasks asked of her during testing and gave feedback based on her experience with the application depending on the prompting questions that were asked.
Our prototype was evaluated by another group of designers and here is a list of findings from their evaluations.
After discussing about the pilot test result and the recommendations we got from the heuristic evaluation, we decided to made some changes to our prototype. Below are a few examples of direction to be taken on redesigns of the application.
Previous Homepage
Redesign 1: Homepage with clear labels, locations of stops and improved cognitive affordance.
__________
Previous Schedule Page
Redesign 2: Schedule page with the nearest multiple bus lines approaching the current stop.
__________
Previous Next Departure Page
Redesign 3: Next departure page with a intuitive time line displaying the time and location for a bus
__________
Previous Use Tickets Page
Redesign 4: Users can be alerted after geting on the bus.
__________
Previous Ticketing Page
Redesign 5: Ticketing page with a more clear layout and call to action buttons.
__________
Previous Use Tickets Page
Redesign 6: Added a screen with a list of bought tickets.
__________