Design challenge
In many big cities like New York, parking is a nightmare. On average, New York drivers spend 107 hours a year on finding parking spots. Nearly 42% of the U.S. respondents said they missed an appointment due to the difficulties of finding parking spots. *source: usatoday.com
More than 200 parking apps are there on the market, but finding parking spaces is still a struggle for many drivers in major cities. ​​​​​​​
How might we help drivers in major cities find parking spaces quickly and easy?
How do drivers park?
It was critical for us to have a better understanding of the drivers' frastructions during the whole process of searching parking spaces. We conducted user interviews, competitor analysis, and workshops to figure out how drivers park and the core pain points.
Step 1: Data collection
We conducted five interviews with who are living and driving in major cities and summarized the reviews of the six most popular parking apps as well. ​​​​​​​

User Interviews Data

First-Round Workshop

Step 2: Analysis & synthesis
​​​​​​​After collecting the raw data, we used affinity diagrams and journey map to synthesize research findings and sights.

User Journey Map

Step 3: Insights from research
•    Need multiple apps
      Drivers need to switch between parking and navigation apps. Some drivers have more than one app to meet various parking needs.
•    Consider street parking first, then off-street parking
       In many cases, drivers consider street parking first because of its low price. They will change to look for off-street parking when they think there is a small chance for street parking.​​​​​​​
•    Consider different factors in different situations
       Drivers need to consider different factors for street parking and off-street parking. We summarized six major factors and sort them by importance.
From insights to design
Money  v.s. Time
We took the insights from research and ideation as the design foundation. Then we developed two personas to help us to design more specifically and efficiently .
Persona 1 - Saving Money

Persona 2 - Saving Time

Drivers' Limited Attention
Before jumping into design, we did some research about drivers' attention while driving as well. For drivers, attention is a limited resource and mobile devices should not be used while driving. Therefore the app needs to appropriate to use while waiting for red lights or short stay at curbs.
Design Goals
Based on the insights from user interviews and the primary scenarios, we came up with three design goals:
User Flow
We iterated the user flow three times from the design phase to user testing phase. We tried to make the user flow as simple as possible.
Wireframes

Early Sketches

Early Wireframes

Prototype, test & iterate
Usability Testing
Users will use the product both during day time and night time, so the product will automatically change the color theme when you use according to the local time. I tested a clickable prototype of the night mode with three people because the dark theme has more limitation of colors. Here are the three main takeaways.
Iteration 1: Switching two maps
The most parking apps on the market are either for street parking or off-street parking. But we found users often consider both options when they drive and sometimes they have to open more than one parking apps to find a good space.
Therefore providing information about both street and off-street parking is an essential feature of the product. Here are some exploration about how users can switch between these two types of maps.

Solution Exploration

Solution 1 required users to decide the parking type before seeing the live map. Solution 2 was able to let users easily switch between two maps without being back to the home page. However, none of the users noticed the tab bar at first glance in the tests.
I iterated the design as the solution 3 because of the three reasons:
​​​​​​​•   The floating action button for switching to off-street parking map is more noticeable.
•   Users did not check the two maps back and forth. They often see street parking first, then look for off-street parking. Solution 3 works better with the user flow.
•   Primary action button is within the thumb zone.
Iteration 2: Street parking map
Because the street parking has much more uncertainty of the occupancy. All the users said they will check the street parking when they are there. So I zoomed in the map view and simplified the information. Green for OK to park and red for no-parking.
Two users said they sometimes will adapt their parking duration to the rule of the street parking. So for the iterated version, I added the parking duration button for users quickly changing the time to see if they can park here from now.
Iteration 3: Suggestions & Navigation
One of the users did not know to swipe the cards. So I iterated the interaction of selecting the different suggestions. Putting the "Best Price" and "Closest" cards on the same screen is more intuitive and simpler.
All of the users taped the card for the details. But they said they would like to directly navigate to the parking garage sometimes.
Design Principles
What I Learned
The biggest struggle we had was to balance the drivers' limited attention and the variety of parking options. In the beginning, we designed for every choice user may have. But by conducting the user testing and iterating, I have learned how to simplify the product to just provide what users most need at that moment.

You may also like

Back to Top