top of page
Traveler in Motion

Wheelsy

Wheelsy is a car rental app designed to modernize and streamline the process of booking rental cars. The goal was to replace the outdated, cluttered experience of traditional rental sites with an intuitive, engaging, and transparent interface.

​​​

Project Overview

Project length: 4-5 days

Tools used:  Figma, Google Forms, Balsamiq, Maze

 

​​My Role

This my first project as a UX/UI design student and I managed the full redesign process—from research to usability testing—ensuring design consistency and business alignment.

  • User research and analysis

  • Information architecture and flow redesign

  • Creating the design system and UI kit

  • Prototyping and usability testing​​

Discover

The Problem

​The Problem at hand is that the current rental car websites needs to be revamped to increase conversion rate and booking. The goal is to make the website more engaging and at the same time also design an app for easy to navigation.

Screenshot 2024-08-19 at 8.24.45 PM.png

As it may be evident that the information on ABC landing page is very redundant and not very well organized. The font and the color theme is not readable and is not consistent through out the page. CTA (Call to Action) buttons are not very intuitive. It is hard to figure out the next steps.

​

Research

The research phase focused on understanding why users abandon car rental bookings and what helps them feel confident when making high-intent, transactional decisions.

​

User Research

​Research was conducted in the form of  informal interviews to begin with and then an online short survey  with frequent and occasional car renters to learn about their past experiences.

Users consistently mentioned frustration with hidden fees, long booking forms, and unclear rental policies. Many shared that they often compared multiple sites but abandoned bookings due to lack of trust or information overload.

​

Method

​An online survey was shared with participants who had previously used car rental websites or apps. This lightweight approach allowed me to collect qualitative feedback efficiently while identifying common patterns and frustrations.

​

Survey Details

  • Participants: 18 respondents

  • Method: Online Google Forms survey

  • Audience: Users who had booked a rental car online within the past 2 years

  • Platforms Used: Desktop and mobile rental websites

Screenshot 2025-12-23 at 1.53.25 PM.png

Here's an example of the survey questions and results 

​Key Findings

  • 72% of respondents said unclear or hidden fees were their biggest frustration

  • 61% abandoned a booking at least once due to long or confusing checkout flows

  • 67% felt that most rental websites were visually overwhelming

  • 58% preferred booking on mobile but felt the experience was harder than desktop

​

Insights Applied to Design

  • Pricing breakdowns were surfaced earlier in the flow

  • Booking steps were reduced and grouped logically

  • Visual clutter was minimized to improve focus and confidence

  • Mobile-first layouts were prioritized to support on-the-go users

​

​​​​Competitive Analysis

​I reviewed existing car rental platforms to identify common usability patterns and pain points. While most platforms offered similar features, many struggled with:

  • Overwhelming layouts

  • Poor mobile optimization

  • Inconsistent pricing presentation
    This analysis helped highlight opportunities for simplification and differentiation.

Screenshot 2025-12-25 at 10.49.20 PM.png

While competitors excel in scale or personalization, Wheelsy focuses on reducing friction through clarity, transparency, and a simplified booking experience.

Define

User Persona

 

The user persona was developed from survey insights to represent common behaviors, motivations, and pain points of people booking rental cars online. It served as a reference point for evaluating design decisions and prioritizing user needs.

Screenshot 2025-12-26 at 1.26.47 PM.png

Rita, 65 - Not very comfortable with technology, loves to take trips with her grandchildren. 

This information further helps us determine the user base for Wheelsy. 

Affinity Map

Survey responses were clustered using affinity mapping to identify recurring pain points and prioritize high-impact design improvements for Wheelsy.

Screenshot 2026-01-10 at 5.35.25 PM.png

Clustering survey responses revealed that user frustration does not come from a single issue, but from the combined effect of pricing uncertainty, cognitive overload, and booking friction—especially in the moments leading up to checkout.

While users initially approach rental platforms with confidence, that confidence quickly declines as they encounter:

  • Changing prices and hidden fees

  • Long, repetitive booking flows

  • Too many similar vehicle options with little guidance

These pain points reinforce one another, causing hesitation and ultimately abandonment right before payment.The affinity map highlighted that trust is the critical breaking point in the rental experience. When pricing lacks transparency or the interface feels overwhelming, users lose confidence in both the cost and the platform itself.

 

Key takeaway from analyzing the affinity map is that users are willing to rent a car—but only when they feel informed, in control, and confident. When clarity is lost, so is conversion.Insights from the affinity map highlighted trust as the key driver of booking abandonment. Wheelsy’s value proposition was built to directly address this by prioritizing transparent pricing, reduced friction, and guided decision-making throughout the rental experience.

Screenshot 2026-01-10 at 7.19.47 PM.png

Wheelsy enables users to book rental cars faster and with confidence by eliminating hidden fees, reducing friction, and simplifying decision-making.

​The Value Proposition Canvas translated user pain points into clear product strategies, ensuring Wheelsy’s design decisions directly addressed user needs.

​

​With a clear understanding of user behaviors, pain points, and Wheelsy’s value proposition, the next step was to visualize how these insights play out across the end-to-end rental experience. The user journey map brings together the persona, affinity map findings, and value proposition to highlight key moments where trust is gained or lost. By mapping user actions, emotions, and friction points across each stage, this exercise helped identify critical opportunities to simplify the flow, reinforce pricing transparency, and design interactions that support confident decision-making throughout the booking process.

​Journey Mapping

​

I mapped the end-to-end booking journey to identify moments of friction — particularly during car selection, price comparison, and checkout. These steps were where users felt most uncertain or overwhelmed.

Screenshot 2025-12-25 at 11.24.46 PM.png

Problem Statement

People who rent cars online often abandon bookings because current rental platforms make it difficult to trust pricing and complete reservations confidently. Through survey insights, affinity mapping, and journey analysis, it became clear that unclear fees, long and fragmented booking flows, and overwhelming choices create friction at critical decision points—especially right before checkout.

As a result, users feel uncertain and disengaged, leading to dropped conversions and a frustrating overall experience. Wheelsy addresses this problem by reimagining the rental journey with transparency, simplicity, and guided decision-making at its core.

​

 Goals

  • Simplify the rental car booking experience

  • Reduce friction and unnecessary steps in the booking flow

  • Improve pricing transparency to build user trust

  • Help users compare options and make confident decisions

  • Increase completed bookings across web and mobile

Develop

Building on the research insights, design explorations, and usability findings, the next phase of Wheelsy focuses on translating the concept into a scalable and testable product. The following steps outline how the experience would evolve from design to implementation.

 

​Ideation & Strategy

The next step would involve collaborative ideation sessions to refine Wheelsy’s core features and prioritize high-impact improvements. Using insights from the affinity map and journey map, design efforts would focus on moments where users feel the most friction—particularly during vehicle selection and checkout.

Key activities would include:

  • Defining success metrics aligned with business goals (conversion, drop-off rate, time to book)

  • Exploring alternative interaction patterns for pricing transparency and decision guidance

  • Prioritizing features based on user value, effort, and technical feasibility

This phase ensures design decisions remain user-centered while supporting long-term product strategy.

​

Minimum Viable Product (MVP)

​The MVP would focus on delivering Wheelsy’s core value: a fast, transparent, and confidence-building booking experience. Rather than launching with a full feature set, the MVP would prioritize essential functionality that directly addresses user pain points.

MVP features would include:

  • Simplified search and vehicle selection

  • Upfront pricing with a clear cost breakdown

  • Streamlined checkout with fewer steps

  • Booking confirmation with clear next steps

This approach allows the product to launch quickly while gathering real-world user feedback for iteration. Here's a comparison between MVP vs Non-MVP with reasoning behind it.

Screenshot 2026-01-11 at 5.31.48 PM.png
Screenshot 2026-01-11 at 5.31.59 PM.png

User Flows & Information Architecture

With the MVP defined, detailed user flows is created to ensure a smooth and logical progression through the booking journey. These flows focus on reducing cognitive load and minimizing decision fatigue.

Key considerations:

  • Designing linear, distraction-free booking paths

  • Reducing form inputs and grouping related steps

  • Supporting easy edits without restarting the flow

  • Ensuring consistency across web and mobile platforms

Clear information architecture at this stage helps prevent usability issues during development.

Screenshot 2026-01-11 at 6.37.57 PM.png

Step-by-Step Breakdown of the User Flow

1. Search Location & Dates

  • User enters pickup location and rental dates

  • Sets context for availability and pricing

Design Focus: Speed and simplicity

​

2. View Available Cars

  • List of vehicles with key details (price, type, seats)

  • Clear, consistent layout across listings

Design Focus: Reduce cognitive load

​

3. Compare & Select Vehicle

  • User reviews options and selects a car

  • “Best Value” or “Recommended” indicators guide decisions

Design Focus: Reduce decision fatigue

​

4. Review Pricing Breakdown

  • Full price visible (base + taxes + fees)

  • Optional add-ons clearly labeled

Design Focus: Build trust before commitment

​

5. Enter Details

  • Minimal form fields

  • Autofill where possible

Design Focus: Reduce friction

​

6. Confirm Booking

  • Final review of rental details

  • Clear primary CTA

Design Focus: Confidence and clarity

​

7. Booking Confirmation

  • Summary of booking

  • Pickup details and next steps

Design Focus: Reassurance and closure

Deliver

Low-Fidelity Prototype

The low-fidelity prototype was created to quickly explore layout, structure, and user flow without getting distracted by visual details. Using simple wireframes, I focused on validating the booking journey, ensuring that pricing transparency appeared early, and reducing unnecessary steps in the checkout process.

At this stage, the goal was to answer key questions:

  • Can users easily find and compare rental options?

  • Does the booking flow feel fast and intuitive?

  • Is pricing clear before users commit to checkout?

Screenshot 2026-01-17 at 5.05.36 PM.png
Screenshot 2026-01-17 at 5.05.50 PM.png

Mid-Fidelity Prototype

The mid-fidelity prototype bridges the gap between early wireframes and the final visual design. At this stage, the focus was on refining layout, hierarchy, and interaction patterns while keeping visual styling minimal. Using grayscale wireframes with real content, I validated the structure of the booking flow and ensured key moments of trust — such as pricing transparency and checkout — were clear and easy to understand.

This prototype helped answer important questions:

  • Is the booking flow logical and easy to follow?

  • Can users quickly compare vehicles without feeling overwhelmed?

  • Does pricing feel transparent before checkout?

Wireframe created for website homepage 

Screenshot 2026-01-17 at 11.11.12 AM.png

Wireframe created for the App 

Screenshot 2026-01-17 at 11.28.50 AM.png
Screenshot 2026-01-17 at 11.29.14 AM.png

Prototyping enabled rapid iteration and ensured Wheelsy’s design decisions were validated before moving into development.

High-Fidelity Prototype

The high-fidelity prototype translated research insights and wireframes into a fully branded, interactive experience that reflects Wheelsy’s design system. This version focused on visual clarity, accessibility, and trust-building details, ensuring users feel confident at every step of the booking process.

Key areas of focus included:

  • A clean, modern interface with strong visual hierarchy

  • Transparent pricing modules with clear breakdowns

  • Streamlined checkout with minimal form inputs

  • Reassuring confirmation and feedback states

This prototype was used for usability testing and stakeholder review, allowing design decisions to be validated and refined before development.

These are some main points to focus on as the user interacts with the prototype

Search & Results:
Final branded design with strong visual hierarchy and clear calls to action.

Vehicle Details:
Transparent pricing and consistent card layout guide confident decisions.

Checkout:
Minimal, distraction-free experience with early pricing clarity.

Confirmation:
Reassuring confirmation screen that reinforces trust and clarity.

​Usability Testing

 

​To validate the high-fidelity prototype, I conducted usability testing with users who regularly book rental cars online. The goal was to evaluate whether the redesigned experience improved clarity, reduced friction, and increased user confidence.

Testing Overview

  • Participants: 8 users

  • Method: Remote moderated usability testing

  • Device: Mobile & desktop

  • Tasks Tested:

    • Find a rental car for a weekend trip

    • Compare options and select a vehicle

    • Complete a booking

 

 

Key Results

Screenshot 2026-01-17 at 2.37.42 PM.png

Insights & Improvements

  • Users immediately noticed pricing transparency and said it reduced anxiety before checkout.

  • Reduced steps improved confidence — users described the flow as “fast” and “stress-free.”

  • Minor refinements were made to microcopy and button labels to improve clarity after testing.

 

Key Takeaway

The high-fidelity prototype successfully validated Wheelsy’s value proposition: a faster, clearer, and more trustworthy booking experience.

 

​Design System

To ensure consistency, scalability, and accessibility across the website and mobile app, I created a flexible design system that supports Wheelsy’s core principles: clarity, trust, and simplicity.

Color

The color palette balances warmth and clarity to guide attention without overwhelming the user.

  • Primary Accent (Orange): Drives action and highlights key CTAs

  • Dark Gray: Primary text and structure for readability

  • Light Gray: Backgrounds and dividers to reduce visual noise

  • White: Clean canvas for content focus

Screenshot 2026-01-17 at 2.59.11 PM.png

 High contrast improves accessibility and ensures important actions are easy to find, especially on mobile.

Typography​

A clear typographic hierarchy supports scannability and confidence.

  • Headings: Bold, modern Inter for strong visual hierarchy

  • Body Text: Highly readable, mobile-friendly font

  • Microcopy: Friendly, reassuring language to build trust

Screenshot 2026-01-17 at 3.09.48 PM.png

Users can quickly scan key information and understand pricing and policies without cognitive overload.

Components

Reusable components ensure speed, clarity, and consistency.

  • Buttons (Primary, Secondary, Tertiary)

  • Car listing cards

  • Pricing breakdown modules

  • Input fields and form elements

  • Confirmation and status banners

Screenshot 2026-01-17 at 3.25.50 PM.png

Components reduce development friction and ensure the experience scales across features.

Layout & Spacing

  • Grid-based layouts for predictable scanning

  • Generous spacing to reduce cognitive load

  • Mobile-first breakpoints

Why it matters:
Clear layout reinforces trust and makes complex information feel manageable.

 

Interaction Design

  • Subtle microinteractions for feedback (hover, loading, success states)

  • Motion used sparingly to guide attention

  • Error states designed with helpful guidance

Why it matters:
Feedback reassures users and prevents mistakes during high-stakes actions like payment.

 

Key Screens & Features

  • Search & Results: Fast, filterable, and easy to compare

  • Vehicle Details: Clear specs and pricing summary

  • Checkout: Minimal steps with early pricing transparency

  • Confirmation: Reassuring summary and next steps

​

Before and After Impact 

Screenshot 2026-01-17 at 3.36.56 PM.png
Screenshot 2025-03-30 at 4.46.07 PM.png

Before

Screenshot 2026-01-17 at 3.40.17 PM.png

After

Development Handoff & Iteration

​To ensure a smooth transition from design to development, a comprehensive handoff package needs to be prepared that aligns design intent with engineering requirements. The goal is  to reduce ambiguity, accelerate implementation, and preserve the user experience validated during usability testing.

Design Handoff

The handoff includes a complete set of production-ready assets and documentation:

  • Design System Library
    A shared component library with buttons, forms, cards, and pricing modules, including usage guidelines, spacing rules, and interaction states.

  • Annotated Screens & Specs
    High-fidelity screens with spacing, typography, and color specifications, along with interaction notes for hover, focus, error, and loading states.

  • Responsive Guidelines
    Breakpoints and layout behavior for mobile, tablet, and desktop to ensure consistency across devices.

  • User Flow & Edge Cases
    Documented flows for booking, editing selections, and confirmation, including error states and empty states.

  • Accessibility Notes
    Contrast ratios, text sizes, and keyboard navigation considerations to support WCAG compliance.

Collaboration with Engineering

Working closely with developers to walk through the booking flow and clarify design intent:

  • Design reviews to align on interaction patterns

  • Technical feasibility discussions for pricing logic and form behavior

  • Iterative feedback to refine components for performance and scalability

This collaboration ensured that the experience remained simple and transparent through implementation.

Iteration & Continuous Improvement

Post-handoff, iteration is driven by real user behavior and performance data rather than assumptions.

Iteration Strategy

  • Usability Feedback Loop
    Continued testing on implemented screens to validate that clarity and trust remained intact.

  • Conversion Optimization
    A/B testing pricing presentation and CTA placement to reduce drop-off.

  • Performance Improvements
    Refining load states and skeleton screens to reduce perceived wait times.

  • Design System Evolution
    Expanding the component library as new features were introduced, keeping consistency across the product.​

​

The handoff and iteration process ensures that Wheelsy’s redesign didn’t stop at design—it became a scalable, user-centered product ready for real-world use. By aligning research, design, and development, the experience continues to evolve while staying grounded in user needs and business goals.

Thank you for reading this casestudy

bottom of page