Parkster - Active ticket
Seems like not everyone using the Parkster parking app remembers to manually end their tickets – some just let them run out on their own. How can we at Parkster make it super easy and user-friendly for folks to wrap up their parking hassle-free?
Course: User-Centered Design
Role: UX-Designer
Client: Parkster
Time frame: 6 weeks
Methodology: Heuristic evaluation · Observations · Survey · Interviews · Personas · How might we
Why don't users end their ticket when they leave their parking?
How can it be made clearer that they have an active ticket?
What can we do to encourage users to end their parking ticket when they leave the parking area?
Problem
To gain a better understanding of the app.
The flow creates unnecessary confusion.
Relevant information, but it could be presented more effectively.
Heuristic evaluation
Notis
Map view
Active ticket
The majority forgets to end their active ticket.
Notifications as reminders are an appreciated feature.
Being able to do more via the notification.
Users don't have trouble finding their ticket.
EasyPark's active ticket is considered smoother due to the interface.
What information an active ticket should include.
Insights from a survey.
"Parkster feels complicated. EasyPark is easier for me because it has a lot of colors, is clear, and it's big. These things make it simpler. The big circle indicates that it's active - Idiot-proof."
Quotes
"All information appears equally important, which makes it easy to overlook the essential."
"Miss the green 'parking in progress' banner at the top. I have tunnel vision. Want to see everything right in the center immediately. Don't like the tab choices, easy to make mistakes."
"They're the ones in the countryside, they're the ones you need to park out here."
"Show which information is valuable to display, and how can the interface entice users to fulfill their needs on Parkster? To cancel a ticket or extend parking."
Avoid creating stress or frustration for the user when they use parkster app and the notis?
"Expand notifications, to go directly to the ticket view."
HMW (how might we)
Design decisions (Low-fi)
"Good to have interactive buttons in the notification.
The end time is more important than the start time.
Change color based on remaining time (To avoid blending in and being overlooked)
The countdown might be a bit hard to perceive with the downward slider. Moves at different speeds depending on time.
'A parking session is ongoing' is a more accurate phrasing."
Design for notis
"End time of ticket is more important than remaining time of the parking.
Remaining time should be included, but not prioritized as much as the end time of the ticket.
It should be relatively clear where the car is parked.
An information button should be available to access specific information about the current parking, even after activating the ticket. (Should it be placed at the address?)"
Design for active ticket
"The next step is to conduct more tests with users, gather their input, and iterate on the low-fi prototype.
After creating a hi-fi prototype, it should be tested with real users to gather their input.
Finally, the process will move to development."