.![]()

Spotwatch
Spotwatch
Objective
Understand the emotions, concerns, and motives intrinsic to the process of parking. Distill the complex relationships of parking-related data between multiple users in a quickly evolving database. Bridge data between users to create an informed and streamlined process of finding available public parking.
Understand the emotions, concerns, and motives intrinsic to the process of parking. Distill the complex relationships of parking-related data between multiple users in a quickly evolving database. Bridge data between users to create an informed and streamlined process of finding available public parking.
Application
A mobile app identifying relevant parking spots in cities before leaving for your destination to eliminate the stress of finding parking while driving. Streamlines the parking reservation process for both ahead-of-time reservation as well as in person payment.
Flow 1: Searching destination

Flow 2: Finding the right spot

Flow 3: Confirming reservation

The problem
![]()

After understanding the problem at its basic level, I wanted to break down the flow of user’s needs and emotions to first understand the gaps in the experience as it is now, and then bridge these to potential data connection opportunities. By understanding User 1 and what resources they lack without a connected ecosystem, I was able to understand how their errors can guide User 2.


Next, I filtered this information into user journey maps organized in two different use cases:
1. Planning out a parking spot ahead of time
2. Using the app only at the checkout in person
1. Planning out a parking spot ahead of time
2. Using the app only at the checkout in person
︎Click to alternate


After breaking down this transfer of data, I determined the three main focuses of the ecosystem.

Information architecture
![]()

Core flows
![]()

Wireframes
︎Click to alternate
︎Click to alternate



Style
![]()

Final screens
︎Click to alternate
︎Click to alternate


