Peer-to-peer car rental platform (confidential)
Peer-to-Peer Car Rental Platform
End-to-end product design for a peer-to-peer car rental platform: booking flows, host and renter dashboards and an internal admin panel.
- Role
- UI & Web Designer
- Timeline
- November 2025 to September 2026
- Tools
- Figma, React, Vite, Supabase, Tailwind CSS, Lovable
- Type
- Employer
Client details are confidential. Names, logos and data are removed, and some screens are recreated or redacted.
The problem
The platform needed a complete peer-to-peer rental experience: host onboarding, renter booking, deposit handling and an internal operations panel, with no design system in place. Rankings were also suffering from technical SEO issues.
My role and constraints
As UI & Web Designer I owned the end-to-end product design: booking flows, host and renter dashboards and the internal admin panel. I also ran QA and usability testing with the developers.
Process
Research covered the private and peer-to-peer rental market, rules and regulations, and a competitor review of Turo and other P2P platforms. Existing platforms showed common friction: unclear booking states, opaque pricing and weak host trust signals.
I mapped 14 booking lifecycle states before wireframing, then designed 14 screens in Figma covering the full rental lifecycle.
Research
Scope
Private and peer-to-peer rental market
How the market works for hosts and renters.
Scope
Rules and regulations
What a peer-to-peer rental platform has to account for.
Scope
Competitor review
Turo and other peer-to-peer platforms.
Finding
Unclear booking states
Renters and hosts could not always tell where a booking stood.
Finding
Opaque pricing
Costs were hard to read before committing.
Finding
Weak host trust signals
Little to reassure a renter about the host and vehicle.
Platform structure
Stage 1
- Renter booking flow
- Host dashboard
- Internal admin panel
Stage 2
- Supabase back end. 14 booking lifecycle states
Stage 3
- Payment gateway. Security deposit pre-authorization
The solution
- Booking flows, host and renter dashboards and an internal admin panel.
- Security deposit pre-authorization live through the payment gateway on a Supabase back end.
- Diagnosed a www and non-www split and a client-side rendering problem that were hurting rankings.
The QA loop
Audit
Reviewed 300+ files across the platform.
Log
139 UX issues, each with a screenshot, URL, device and browser, and expected vs actual.
Track
Worked through the log with the developers.
Confirm
Every issue followed through to a confirmed live release.
SEO diagnosis
Found
www and non-www split
Two versions of the site were splitting ranking signals.
Found
Client-side rendering
Pages rendered in the browser, which was hurting rankings.
Outcome
Every logged issue was tracked with the developers through to a confirmed live release.
- Files audited
- 300+
- UX issues logged
- 139
- Booking states mapped
- 14
What I learned
I would invest earlier in a documented design system. Many component inconsistencies surfaced mid-build that a token library from the first sprint would have prevented.