SPRINT15 - Mobile App

ZenPark

A mobile application that incorporates both commute and parking time estimates for reaching your destination in addition to providing exact locations for available parking spots, so your journey is as accurate and stress free as it can be.

Problem Statement

How can we make navigating to and parking in a crowded city accurate and stress-free?

Problem Background  

Most drivers use traditional navigation applications to help them plan out and estimate their route and time to their destination. In fact, according to Insider Intelligence, it was estimated that in 2021, around 67.6% of smartphone users would be using navigation applications (4).  However, most don’t think about parking once they have arrived. So that additional time to find a suitable parking location is not factored into the original plan, contributing to a potential delay in reaching a destination and resulting in stress and frustration. A study by INRIX also found that the average American driver spends an estimated 107 hours per year frustrated looking for a parking spot. On top of that, the estimated costs from wasted time, gas, and emissions is about $2,243. (3)

In addition, with growing populations in urban areas (1), the demand for parking locations both in garages and on the street continues to grow, especially in dense locations, where “drivers are often left frustrated and spend too much time searching for a spot, due to lack of immediate awareness of where spaces are open.”(2)

User Pain Points

Conducted a survey to obtain initial user data with regards to parking. To address this problem effectively the questions were focused on parking experience alone.

In the research, it was found that about 72% of drivers arrive late to their destination because they were not able to find a parking location on time. It was also found that arriving late was not a pleasant experience for most. Of this group, most reported feeling “frustrated”, “annoyed”, “very anxious”, and “ticked off”. 

These findings confirmed that arriving late definitely has a negative impact on most drivers.

Feedback

In addition, the research also confirmed that about 81% of drivers do have a sense of where they will park, however, only if they have already been to that area beforehand or done previous independent research prior to going on their commute. Therefore, it is still an additional task that most users need to do aside from planning their overall commute. And even if they know where to park, there is no sense of availability unless they reserve a spot in advance. 

Landing on the Solution

Based on the pain points of our potential users it was identified that the main pain point for most users was arriving late to their destination. 

This confirmed the idea that overall time of the journey was equally as important as knowing where to park in order to arrive at a location on time. This helped shape the solution to be both a mobile navigation application and parking facilitator.  

Explanation of the Solution

ZenPark makes planning out your entire trip more convenient and hassle-free by providing both the route to the commute and facilitating your experience when it comes to finding a parking location based on your preferences, so that you know exactly where to park and still arrive at your destination on time. 

ZenPark will provide all the details for parking by combining inputs from parking data provided by INRIX, which includes off-street/on-street parking data. parking analytics, and predictive occupancy. In addition ZenPark will collect crowd-sourced user inputs to display the most up to date parking regions and their availability. 

All of this information will be displayed to the user in a format that is familiar and standard with most mobile navigation applications. This allows for any user to readily use ZenPark as a navigation app with the added benefit of including the parking time estimate and finding the exact spot to park once they reach their destination. 

Future Steps

I plan to take my experience and lessons learned with this project to develop a new product with a team of designers and engineers. If in the future I am at a point where I have the time and resources to fully execute this, this is definitely a product I would enjoy developing and bringing to life. 

References 

  1. https://ourworldindata.org/urbanization#what-share-of-people-will-live-in-urban-areas-in-the-future 
  2. https://meetingoftheminds.org/why-parking-issues-should-matter-to-cities-29897
  3. https://parkinglogix.com/search-for-parking-roads-congested/
  4. https://www.insiderintelligence.com/content/people-continue-to-rely-on-maps-and-navigational-apps-emarketer-forecasts-show
  5. https://inrix.com/blog/inrix-parking-data-quality/

Learnings

Product Manager Learnings:

Gabby Larios

As a product manager it is important to focus on defining a problem space that is focused on one problem. And though the solution space should be explored with your team, it is also important to have a focused approach of how the solution will be executed. 

I also learned that developing personas is crucial to envisioning how your product will be used. 

I also learned that defining quantitative metrics and milestones are crucial for developing a MVP. With quantitative metrics, it is easier to prove and monitor how your product is making a realistic impact in the world and with its users. These metrics tied back to both user and market research are what ultimately help define the product’s success and guide its potential growth.

Designer Learnings:

Designer Learnings:

Jo Sturdivant

  1. Adapting to an Established Team: Joining the team in week 6 of 8 was challenging, as I had to quickly adapt to existing workflows, dynamics, and goals. This mirrors real-world situations where you often integrate into teams mid-project, and flexibility is essential.
  2. Work-Blocking for Efficiency: With only two weeks to complete the project, I learned the importance of a structured work-blocking system. This approach allowed me to manage my time effectively and meet deadlines under pressure.
  3. Making Data-Driven Design Decisions: Unlike my past projects, I had to rely on research conducted by others. This was a valuable experience in using pre-existing data to guide design decisions, helping me focus on the core insights without starting from scratch.

Developer Learnings:

Developer Learnings:

Vanady Beard

&

As the back-end developer, I learned how important it is to create efficient and reliable systems that support the entire application. This experience also taught me the importance of optimising the database and ensuring the backend is scalable and easy to maintain.

Developer Learnings:

Stephen Asiedu

&

As a back-end developer, I've come to understand the importance of being familiar with various database systems and modules. This knowledge enables me to build diverse applications and maintain versatility in my work. I've also learned that the responsibility for making the right choices rests on my shoulders, guided by my best judgement.

Developer Learnings:

&

Developer Learnings:

Maurquise Williams

&

  1. Process of Creating an MVP: Developing a Minimum Viable Product (MVP) taught me how to focus on delivering core functionalities balancing between essential features and avoiding scope creep.
  2. Collaboration in a Real-World Tech Setting: This experience taught me how to collaborate efficiently in a fast-paced tech environment, keeping the team aligned and productive, even while working remotely across time zones.
  3. Sharpening Critical Thinking and Problem-Solving Skills: This experience honed my ability to think critically and solve problems efficiently. By tackling challenges and finding quick solutions, I sharpened my decision-making and troubleshooting skills in a dynamic, real-world setting.

Developer Learnings:

Jeremiah Williams

&

All in all this experience was very awesome I learned that in coding with others being transparent is key

Developers Learnings:

Justin Farley

&

I learned how important communication is when working with a team. Communication provides understanding, advice, ideas, and much more. While working with the product team, I’ve found that communication keeps everything flowing smoothly. Working with a team also showed me that every member brings something different to the table and we all have to work together in order to align and meet our end goal.

Full Team Learning