Making renting feel less like a gamble

Overview

Finding a rental is one of the highest-stakes consumer decisions people make on their phones, and one of the worst-designed. This project asked a simple question: what would a rental search look like if it were designed around the renter's biggest fear — being deceived — instead of around listing volume?

The problem

The rental search is fragmented across classifieds, social media groups, and word of mouth. Listings go stale without warning, photos oversell, prices hide fees, and outright scams are common enough that "never pay a deposit before viewing" is folk wisdom. The result: renters do enormous manual work — cross-referencing, screenshotting, messaging strangers — to establish the basic facts a product should guarantee.

Business context

For a rental marketplace, trust isn't a feature — it's the moat. Listing volume is easy to copy; verified, current, honestly-presented listings are not. The concept's business logic: a platform that reduces wasted viewings and eliminates fraud anxiety earns the two behaviours marketplaces live on — repeat usage and word-of-mouth referral. Every design decision below traces to that thesis.

Who I designed for

[EDIT: replace with your actual research — interviews, surveys, or secondary research you used. Even "I interviewed 4 recent renters" is stronger than vague claims.] The core persona was the time-pressed renter searching remotely — someone relocating for work or study who must shortlist and commit before they can be physically present. Their journey concentrated three pain peaks: not knowing what's real, not knowing what's current, and not being able to compare options on equal terms.

Key decisions

Trust made visible, not claimed. Listings carry explicit signals — verification status, last-updated date, and complete cost breakdown including recurring fees — presented as structured data, not marketing copy. A listing that hides information looks worse than one that shows a higher price honestly. The interface takes the renter's side.

Search that matches how people actually decide. Renters don't choose on price alone — they trade off commute, space, and cost against each other. Filters are built around those trade-offs, and a side-by-side compare view puts shortlisted homes on equal terms, replacing the screenshot folder every renter currently maintains.

Closing the loop: from listing to viewing. The journey doesn't end at "message the landlord." In-app viewing scheduling with confirmed time slots turns the vaguest, most drop-off-prone step of the journey into a committed appointment — good for renters, and the single most valuable conversion event for the business.

The system

A consistent component library — cards, filters, badges, forms, and state patterns — keeps the experience coherent from browse to booking, and made high-fidelity iteration fast. Empty, loading, and error states were designed deliberately: in a trust product, a blank screen with no explanation is a broken promise.

Accessibility

WCAG AA contrast throughout; verification and warning states carry icons and labels, never color alone; touch targets sized for one-handed use; type scale tested at larger system font sizes, since housing search skews heavily mobile.

Testing & iteration

[EDIT: replace with your real testing story.] Walkthroughs of the prototype surfaced hesitation around what "verified" actually meant — so the badge became tappable, opening a plain-language explanation of what was checked and when. Trust signals only work if the user can interrogate them.

Outcome

The published case study has drawn 6,800+ views and 425 appreciations on Behance — the strongest reception of my published work. The deeper outcome was methodological: this project is where I learned to design from the fear backwards — identify what the user is most afraid of, and make the interface the thing that disarms it.

What I'd do next

Validate the verification model against operational reality (who checks listings, and at what cost?), test willingness-to-pay for landlord-side tools, and run task-based usability tests on the compare view — the feature I believe in most and therefore trust least.

Reflection

Marketplaces succeed when both sides feel the platform is on their side. Designing this taught me to treat trust as an information architecture problem: it isn't a badge you add at the end — it's the order in which you reveal the truth.