Case study
DriveShare
DriveShare is a concept for a peer-to-peer parking marketplace: homeowners rent out driveways and drivers reserve them. It was a four-person HCI course project. I was the front-end developer and built the project website.
- Next.js
- Tailwind
- Figma
- HCI
- prototype rounds: lo-fi, mid-fi and hi-fi
- 3
- participants in the think-aloud test
- 3
- Nielsen heuristics in the team's own review
- 10
- personas: two students and two driveway owners
- 4
This is a design project, not a working marketplace. The app exists as Figma prototypes and the website presents the research and design work. The website has no database, booking or payment code.
How the project ran
Interviews
The team ran semi-structured interviews with commuting students. Safety and reliability came out as important as price.
Themes and personas
Interview notes were grouped into four themes: safety, convenience, interaction and current issues. The team also wrote four personas (two students and two driveway owners), an empathy map and an experience map.
Lo-fi prototype
The first round was low-fidelity: an early paper prototype and a flow map in Figma. It mainly validated the concept and the task flow.
Mid-fi prototype
A medium-fidelity Figma prototype for mobile supported the renter side in full and the homeowner listing flow in part.
Think-aloud test
Three participants, two student commuters and one homeowner, used the prototype while thinking aloud. One change, showing driveway photos earlier in the flow, went straight into the prototype.
Hi-fi prototype
Before the final version the team reviewed the design against Nielsen's 10 usability heuristics and recorded one issue per heuristic with its fixes. The report says all ten were addressed in the high-fidelity Figma prototype, which has separate renter and homeowner flows.
The problem
Drivers waste time circling for parking while many homeowners have driveway space that sits unused. In the team's interviews, commuting students reported spending roughly 10 to 30 minutes looking for a spot before class.
The idea: homeowners list driveway space for set time windows and drivers reserve a slot. Time-boxed reservations are meant to reduce conflicts and overstays.
My part
I was the front-end developer on a four-person team. I built the project website with Next.js, React, TypeScript and Tailwind CSS, and contributed to the driver and host flow design and the HCI write-ups.
- A landing page that explains the idea, the three-step journey (search, reserve, park) and the safety approach.
- An analysis page with the interview themes, the four personas, the empathy map and the experience map.
- A features page with 12 captioned tiles, 6 for drivers and 6 for homeowners.
- A deliverables page that links six course documents, the FigJam board and two videos, and a team page with a profile for each member.
What testing changed
The think-aloud sessions produced one immediate change and a list of refinement goals: buffer and extension time after booking, in-app messaging, safety verification indicators, multiple photos per listing and pricing suggestions.
The high-fidelity prototype's README lists smart pricing suggestions and enhanced safety and verification among its additions. The prototype also gives homeowners a full flow: list a driveway, upload photos, add safety tags, set availability and pricing, and view a dashboard.
Limits
- This is a design project. Prototype functionality is not real: nothing is saved, booked or paid for.
- The landing and features pages describe the intended product, including in-app payment and host payouts. None of that is implemented, and the listings on the landing page are placeholder text.
- The feature images are generated concept images, not screenshots of an app.
- Usability testing was small and qualitative. The documented think-aloud round had three participants.
- The heuristic review was done by the team itself, not by outside evaluators.
Built with
- Website
- Next.js
- React
- TypeScript
- Tailwind CSS
- Biome
- Design and research
- Figma
- FigJam
- Paper prototyping
- Think-aloud testing
- Heuristic evaluation