Back to work

Product Design Case Study / Concept case study

Vehicle Rental Website -
Rental Website UIUX
shaped into a story.

A rental website interface focused on vehicle discovery, booking clarity, and trust.

Product UX, UI design, booking-flow QA
Responsive rental website
Vehicle discovery, comparison, booking confidence
A rental website interface focused on vehicle discovery, booking clarity, and trust.

Project Overview

The work starts before the polished shot.

I treated Vehicle Rental Website as a product problem first. The Dribbble image is the final visual layer, but the useful story sits underneath it: who the screen is for, where a user might pause, and what needs to be checked before the interface can feel ready.

RoleProduct UX, UI design, booking-flow QA
TimelineConcept case study
PlatformResponsive rental website
ProjectRental Website UIUX

Problem Discovery

The real risk was hesitation.

Rental options needed to be easy to scan, compare, and act on. I focused on the moment before the click: does the page explain itself quickly, does the next step feel natural, and does the visual hierarchy support that decision?

01Primary user path

Vehicle discovery, comparison, booking confidence

03Research signals

Journey notes, content priorities, and expected user behavior.

03Design decisions

Interface choices tied back to user hesitation and action clarity.

A good-looking screen is only useful when the user knows what to do next.
01

User Journey

Mapped the rental decision flow from vehicle browsing to booking confirmation.

02

Content Logic

Prioritized comparison attributes: vehicle type, price, feature set, availability, and trust signals.

03

Decision Risk

Reviewed common failure points in rental flows, including hidden fees, weak availability states, and unclear CTAs.

Design Process

From first intent to a clearer product flow.

I moved from intent to structure before pushing the visual style too hard. That kept the work grounded: every section needed a job, every action needed a reason, and every polished screen needed a quality check behind it.

01

Discover

02

Map

03

Frame

04

Prototype

05

QA

06

Refine

01 / Discover

Problem and user intent

Mapped the rental decision flow from vehicle browsing to booking confirmation.

02 / Structure

Journey and content hierarchy

Prioritized comparison attributes: vehicle type, price, feature set, availability, and trust signals.

03 / Design

Comparison-first cards

Vehicle cards place core decision data in a repeatable layout so users can compare options without opening every detail page.

04 / QA

Booking path audit

Checked the flow for missing states around selected vehicle, pickup details, availability, and final action.

05 / Outcome

Handoff and next steps

Prototype filters and date selection.

Dribbble Screen Gallery

All project visuals now live inside the case study.

The real images from the Dribbble detail page are pulled into this case study, so the reader can review the actual UI screens without leaving the portfolio. No repeated crop placeholders here.

UX Decisions

Why the screens were shaped this way.

01

Comparison-first cards

Vehicle cards place core decision data in a repeatable layout so users can compare options without opening every detail page.

02

Action hierarchy

Primary booking actions are visually stronger than secondary exploration actions to prevent decision drift.

03

Trust before booking

Support, policy, and reliability cues are positioned near booking moments where hesitation usually appears.

QA Lens

I looked for the places the flow could break.

01

Booking path audit

Checked the flow for missing states around selected vehicle, pickup details, availability, and final action.

02

Edge-case checklist

Defined QA scenarios for unavailable vehicles, missing price data, invalid dates, and repeated booking attempts.

03

Mobile tap review

Reviewed card density, CTA spacing, and filter interactions for thumb-friendly mobile use.

Outcome

What the concept proves, and what it still needs.

A rental website interface focused on vehicle discovery, booking clarity, and trust.

This is still a portfolio case study, so I am careful not to fake product metrics. The value is in the clearer flow, the visible UI system, and the checks that would guide the next iteration.

01

A faster scan path for rental decisions.

02

A clearer booking hierarchy with fewer competing actions.

03

A QA checklist that connects UI states to real booking risks.

Next

Step 1

Prototype filters and date selection.

Next

Step 2

Run task testing for vehicle comparison.

Next

Step 3

Add error-state screens for the full booking path.

Visual Source

Want to review the original shot?

This page documents the UX and QA thinking. The original visual presentation is still available as supporting work evidence.