In Taiwan, drivers receive paper tickets as bills to pay for street parking. The government workers come to issue tickets and mark parking hours when the car is parked on the street. As a driver, I find myself losing the tickets or forgetting to pay often. Bothered by this issue for a long time, I started to think about the solutions to address this problem. In this project, I interviewed drivers to learn about the difficulties the met, utilized persona to understand the target group, and quickly get rounds of feedback in the process of mocking up.
To begin with, I listed out a few problems I have met on paper tickets.
As physical tickets are easy to be lost, I started to think about virtualizing the tickets, which tickets are stored on the phone and ready for drivers to pay and check.
To see how other similar products do on the market, I researched about the products on the market. I found that most products help users to pay the tickets, but managing the street parking tickets is not the primary service. Because of that, drivers have to go through many steps to get to the payment stage, and some designs are lacking to guide drivers to pay.
To begin with, I gauge the target user demographics to narrow down the scope.
Do other drivers feel the same? Will this service have potential? Are there related issues I can explore? I asked 6 drivers to learn about their experiences.
After the interviews, I discovered that most active drivers can be segmented into two groups. I looked through the interview notes and created the persona of these two typical groups.
With the goal set, I brainstormed the required features and quickly sketched some of the ideas.
As I completed brainstorming, I drew out user flows to examine whether the features accommodate the user journey.
As I making the design to be more polished, I constantly sought feedback from the drivers and explored the possible improvements with them.
How can we help drivers to recognize the rates? There were a few options that I explored, present all color stripes or with a filter. Considering the real use case, presenting all the rates is the most convenient way to the drivers.
Initially, the tickets are presented all together. From the drivers' feedback, categorizing information as they collecting tickets helps them to find the tickets. The ticket tab will also be highlighted when the driver receives a ticket or there is a ticket overdue.
How can we encourage drivers to pay (if they choose to pay manually)? I improved the design with a CTA "Pay All" button, which shows up when the user opens the ticket page. Drivers can also know the amount of the fee on the left side of the button.
How can we help the user to find long-term receipts? Except for the list, I designed another way – Calendar, which users can find the ticket through its issued date. Normally, a user receives less than four tickets a day. Under the circumstances, I used card design to help user quickly switch between different days and tickets.
In addition to changing the swipe direction to left and right, I also include a conversational text "remind me on __ at __" to make the customizing experience friendly.
As AutoPay is the main feature of Parkie, how can we introduce it to the user? Instead of the pop-up window (which sometimes seems abrupt) or placing it after the sign-up form (which makes it looks minor), I broke the sign-up process into two steps. The second step introduces AutoPay.
Though there are still many details that can be explored with Parkie, It was fun and exciting to design for the issue that I meet in life. I enjoyed the process of knowing other driver's issues and learned to improve the design by seeking quick feedback. As I constantly inspired by people and the environment around me, feel free to get in touch if you have any thoughts!