Parc
Valet made easy.
A cross platform mobile app.
WHY
Valets make life easier. No debate.
But holding on to a physical ticket? A headache. Giving your number to receive a text message? Boring, but somewhat effective. Waiting for the valet to bring your car? Annoying. Waiting in line because there are multiple people requesting their car? Even more annoying. Getting scammed on pricing? You can’t even argue with the valet. They only accept cash? Come on, you have cash on you?
Parc makes sure none of this happens. Because it can all be done directly in the app.
Valets aren’t going anywhere. I mean they might disappear with self-driving and self-parking cars, but for now, let’s stay in the present. They must adapt to modern, technological times.
However, it must remain as simple as exchanging your keys for a slip.
Browse available locations.
Request your car.
Show the valet your QR.
Pay and leave a tip.
How it works.
Parc’s features revolve around efficiency. If it takes too long or too many steps, it’s scratched.
Customers are able to input their car details into the app, including their car model and a picture. Even multiple cars. They’re also able to input their payment details. When a user arrives at a partner location, they show their QR code to the valet, who starts a session and grabs the keys. During the parking session, users can check the current cost as well as contact the valet in case of any problems. Then users are able to request their cars and will receive a confirmation when their car is ready. Finally, customers can complete the payment within the app and tip their valet accordingly.
Development first-timer.
Parc became to be my first project where I developed the application after designing it. It was a semester long ordeal in my Mobile Computing class at the University of Miami. The design phase had to be completed promptly as the development phase was definitely going to require extensive work.
I used Flutter to build the cross-platform app and implemented Firebase Authentication and Firestore, and Google Maps API.
It was a challenging project as building the UI as well as connecting the back-end got a little chaotic to do them simultaneously.
ROLE
UI/UX DESIGN
DURATION
TEN DAY SPRINT
TOOLS
FIGMA - MIRO - TRELLO - CANVA
Discover.
Discover the problem, conduct research, create surveys, interview people, and do some business analysis.
Define.
Synthesize information gathered and make sense of it. What are the pains and gains of the users? How will they get value?
Develop.
Start ideating. Think of features that bring value to users. Define an MVP. Develop a user flow chart and information architecture.
Deliver.
Prototyping. Many iterations of LO-FI and MID-FI designs. Conduct usability tests. Start adding color. Make it look good. Finalize prototype.
