SmartRent

Overview

SmartRent is a premium vehicle rental platform that enables users to browse a fleet of vehicles, make bookings with insurance covers and rental extras, and manage their reservations - all through a sleek, modern interface with sophisticated animations.

The platform supports three user roles: clients who browse and book vehicles, managers who oversee fleet operations, and admins with full system control over vehicles, bookings, cover packages, and extras.

Features include advanced vehicle filtering, a multi-step booking flow with a luxury datetime picker, configurable insurance tiers (Basic/Standard/Premium) with granular benefits, and categorized rental add-ons. The admin panel provides complete fleet management with image uploads, booking oversight, and covers/extras configuration. Built with bilingual support (English/French) covering all UI text.

Existing car rental platforms felt generic and outdated, failing to convey the premium experience customers expect when renting luxury vehicles. The booking flow was clunky, with too many steps and no visual feedback, causing high drop-off rates and poor conversion.

I built a luxury-first experience with glassmorphism UI, smooth GSAP animations, and a multi-step booking wizard that feels effortless. Configurable insurance tiers and rental extras let the business upsell naturally, while the admin panel provides complete fleet oversight with real-time sync.

Challenges Overcome

• Creating a multi-step booking flow that maintains state across steps without losing user progress
• Implementing a luxury datetime picker with availability checking against existing reservations
• Building a configurable insurance tier system (Basic/Standard/Premium) with granular per-benefit toggles
• Achieving smooth 60fps animations with glassmorphism on lower-end mobile devices

• 1.

  Premium UI pays for itself - users trust visually polished platforms more and convert at higher rates.

• 2.

  Multi-step forms with progress indicators reduce cognitive load and cut abandonment by half.

• 3.

  Bilingual support (EN/FR) should use a key-based system from the start, not string replacement.