Car rental

A self-initiated 2-day UI project exploring how visual clarity, structure, and modular systems can improve trust and usability — even without changing core business logic.

Role

UI designer

Role

UI designer

Role

UI designer

Duration

2 days (January 2025)

Duration

2 days (January 2025)

Duration

2 days (January 2025)

Team

Solo

Team

Solo

Team

Solo

Motivation

Study

Motivation

Study

Motivation

Study

UX Design

UX Design

UX Design

UI Design

UI Design

UI Design

Webdesign

Webdesign

Webdesign

#hero —

#nav-trigger-1 —

Why redesign this?

I found this site while casually browsing Google Ads. It felt outdated, visually messy, and awkward on mobile — not ideal when you're deciding who to trust with a rental car.

The booking form was crowded, button states were inconsistent, and layout logic was missing. I decided to reimagine it, starting with flow and hierarchy.

#context —

Three types of users, one shared need

availability

Locals focus on price and availability

efficiency

Business travelers want speed and efficiency

mobile-first

Tourists need a simple, mobile-first booking experience

The new design had to work equally well for all of them — without overcomplicating things.

#users —

Structure before styling

Wireframes that prioritize logic
I started with lo-fi sketches for desktop and mobile, applying familiar reading patterns:
  • Z-pattern on the homepage to guide attention
  • F-pattern in the form layout for clarity
This helped define hierarchy before diving into visuals.

#structure —

Clean, reusable UI system

Clean, reusable UI system

Designing components that scale
Designing components that scale
I rebuilt the interface using a visual system with:
  • A 12-column grid for desktop and 4-column for mobile
  • Scalable spacing and radius logic
  • Accessible contrast and clear type scale
  • Modular components: buttons, chips, cards, input groups
This made the layout easier to extend and maintain.

#system —

#form —

The form. From overwhelming to intuitive

The original form was dense and hard to scan. I grouped related fields, aligned inputs properly, and made CTA buttons visible at all times. A toggle for “drop-off at a different location” was added with clear visual logic. On mobile, it’s all thumb-friendly and gesture-supported.
Each card shows just what’s needed — nothing more, nothing less:
vehicle type, fuel, transmission, seats, and price.
Popular cars are visually marked.
Actions appear on hover (desktop) or are visible from the start (mobile) to keep things clean but accessible.

Screens

Screens

Designed for all screens — and for attention
From homepage to cards to booking flow — each element was designed to adapt across breakpoints and support microinteractions.

The result: a consistent experience that feels natural both on desktop and mobile.

What I learned

And what I'll definetely change next time.
This project reminded me how much structure shapes perception.
I didn’t redesign the brand, rewrite the content, or add new features — but just by cleaning layout logic and rethinking how components behave, the product felt more confident. And more human.
Even without access to analytics or user interviews, small design decisions added up: clearer form logic, cleaner cards, responsive behaviors that don't distract. It became easier to trust the interface — not because of gradients or microcopy, but because everything was where it should be.
That said — I wouldn’t do it the same way again.
I’d test more assumptions: see how people move through the flow, how fast they book, where they hesitate. I’d validate if visual clarity actually helped reduce friction or just felt better to me as a designer.

Visual trust is not a style
its a decision

Also, the cards could be more flexible. In hindsight, I’d make them easier to scale with things like promos, loyalty offers, or upsells. I focused on clarity — but didn’t test complexity.
Still, for a 2-day self-initiated project with no brief and no metrics, it did what I needed:
It challenged my assumptions.
And it made me rethink how much value lives in simple structure.

#context —

#reflections —

Previous project

Previous project

Previous project

Next project

Next project

Next project

What will we build?

© Ekaterina Pykhova, 2025

#footer —

#contact —

What will we build?

© Ekaterina Pykhova, 2025

#footer —

#contact —

What will we build?

© Ekaterina Pykhova, 2025

#footer —

#contact —

What will we build?

© Ekaterina Pykhova, 2025

#footer —

#contact —