BART Park

BART Park

 
bartlogo.png

METHODS: User Interview, Comparative Analysis,  Rapid Paper Prototyping, Conducting Usability Tests, UI Design

TOOLS: Marvel, Sketch 3, InVision

DURATION: 2 Days      TEAM: Myself

CONTEXT: Class Project

 

Overview

Daly City BART Station Parking Lot

Daly City BART Station Parking Lot

Problem

Commuters who drive to a BART (Bay Area Rapid Transit) station may not know what time the parking lot becomes full in the morning. As a result, they may not be able to plan trips efficiently.

Solution

A mobile app that would inform users when BART parking lots become full for advanced or on-the-go commute planning.


 
BART Park progress bar-02.png

Research

Target Audience

During a 30 minute interview, the user told one story regarding commuting that high-lighted a challenging experience.

From there, I defined the target audience:

  • Commuters who park at any BART station in the morning
  • Smart Phone Users
 

Defining Pain Points

After drawing a storyboard for the user, I identified 2 user pain points:

  • Users not knowing the availability of a BART station's parking spaces in the morning.
  • Users not knowing the typical time that a specific BART station becomes full.

Key Features Needed

I brainstormed to think of solutions and thought of two features that would address the 2 pain points.

  • A live display of available slots in the morning
  • A record of what time parking lots become full for each BART station
 

Comparative Analysis

By exploring the BART website and installing 5 iOS mobile apps that displayed slot availability for bike share stations or parking lots, I took note of how various digital products designed their interface to serve their user's goals.

 


BART Park progress bar-03.png

Wireframe Sketches

Based on the 2 key features needed, I rapidly sketched multiple layouts before choosing the best to turn into a paper prototype.

 

Rapid Paper Prototype Usability Testing

Following usability testing with 5 individuals, I gained actionable insights including:

  • Unclear meaning of icons/symbols (meter bar)
  • Missing 1 useful data point (number of parking spots available)
  • Navigation has 1 inconsistency (a navigation button switches location)

Iteration

I incorporated the feedback from the usability testing into creating higher fidelity screens using the software, Sketch 3. Improvements in the navigation, added data points, and iconography were made.

Prototype

Those Sketch 3 designs were made into a prototype using InVision in order to be tested in another round of usability testing.


Second Round of Usability Testing

Insights from testing the 2nd prototype:

  • The function of new symbols are unclear
  • The hierarchy of information can be made more distinct
  • I encountered 3 individuals who would find an app like this useful. All of whom have had experience parking at a BART parking lot.

BART Park progress bar-04.png

Next Steps

  • Iterate from the 2nd round of usability testing
  • Determine development viability - Would this be possible or feasible to code?
  • Determine business viability - Would this be feasible to implement?
  • Conduct more usability testing

Retrospective

My strengths during this project was the speed of my creation and iteration cycles.

Our class project's brief was to design an app for a single individual but in doing so, I designed an app that would serve anybody who had the same scenario as this one individual.