A peer-to-peer car rental platform has to make an agreement between two people precise. The renter needs a particular vehicle for particular dates. The owner needs to agree to that booking and understand the terms of handing over an expensive asset.
Juuh is a car sharing marketplace in Spain designed and built by Renewator. Its public catalogue includes vehicles in Estepona, with search by location and dates, host profiles and booking requests. Looking at that journey reveals several product decisions that matter well before a marketplace needs sophisticated recommendation systems.
Updated in October 2026 to reflect the public catalogue and booking pages. The earlier version described a planned September launch.
What should a car rental listing show?
The result card has limited space. A renter scanning a grid needs to compare the vehicle, price, location and a few practical attributes. Juuh’s cards show model and year, transmission, pickup city, a starting daily rate and the booking mode.
The booking mode deserves that position. “Request to book” means the renter is asking for approval, so choosing dates cannot be mistaken for a confirmed reservation. A platform that leaves this distinction until the end of checkout creates uncertainty at exactly the wrong moment.
The detail page then expands the agreement: photographs, seating, fuel type, equipment, pickup area, rental rules and the host. Someone travelling with a family can check seats and luggage needs; someone unfamiliar with the city can check where pickup happens.
A daily rate is only the beginning of the price
A starting price makes a catalogue comparable. A booking needs a quote for the selected dates, the applicable taxes and a clear explanation of any security deposit. These amounts serve different purposes and should have distinct labels.
Juuh’s inspected listing describes a card hold separately from the rental total. It also places the mileage allowance and cancellation policy within the vehicle page. Those details can change whether a car suits a trip even when the daily rate looks attractive.
When designing a similar product, check the transition from advertised rate to dated quote. Can the renter account for the difference? Can they see what is charged and what is held? A support agent should not have to reconstruct the price from a screenshot after the booking.
Host approval creates a real waiting state
Request-based booking adds a period between submission and confirmation. The inspected Juuh listing tells renters that the host confirms within 24 hours. A stated window gives the renter an expectation before they send a request.
For a marketplace team, that implies several separate states to design: requested, accepted, declined, expired and cancelled. Each needs an understandable next step for both parties. The interface also needs to be clear about when money is collected or released. These are requirements to settle during platform development, rather than text to add after checkout is built.
Keep pickup information useful and appropriately limited
Juuh shows the pickup city publicly and says the exact address is shared after confirmation. That supports discovery without exposing every owner’s precise pickup point to every visitor.
The handover still needs practical details: a time, a place and a way for the two parties to coordinate. Software can organise that agreement without pretending the physical exchange has disappeared. For a new marketplace, this distinction helps keep scope tied to the actual transaction.
Explain protection without implying coverage
The BMW 220i listing explicitly says Juuh does not add insurance cover of its own and directs renters to ask about the host’s policy before booking. That is a more specific statement than a general reassurance about safety.
Product teams should keep deposits, damage responsibilities and insurance explanations separate. The interface should link to the applicable terms and make the relevant information available before a request. Juuh provides dedicated pages for trust and safety and payments and cancellations.
Owners need their own introduction
A renter arrives looking for availability. An owner arrives asking whether listing a car is worthwhile. Juuh’s host page addresses pricing, approval and earnings before the listing process.
Map each side’s decision separately, then identify the information they must share. The result is a more concrete brief than a list of screens labelled “search,” “profile” and “checkout.”
See the Juuh case study for more screenshots. Our UI/UX design and software development work starts with these transaction rules: what each person agrees to, what they see and what happens next.
