Rare Cars

Web platform · Case study

Rare Cars is a marketplace for buying and selling rare and classic cars. I designed its account area for desktop and mobile: the seller's listings and the form to add a car, plus saved cars, saved searches, notifications and settings.

Rare Cars 'My Listings' page: a dark top bar with the RARECARS logo, an account menu on the left, status tabs and a grid of yellow 1975 Dodge Challenger listings, with the filter and card action menus open.

01Overview

One account for buyers and sellers

The same person can be shopping for a car and selling one. The account puts both sides behind one menu: My Listings for selling, Saved Products, Saved Searches and Browsing History for buying, then notifications and settings.

The seller side carries most of the weight. A listing goes through review before it is published, so every card shows its status and the tabs filter by it: Published, In Review, Declined, Archived.

02What I designed

Selling, saving and staying informed

  • My ListingsA grid of your cars, filtered by status

    Each card shows price and status; a menu marks it as sold or "in talks", or deletes it.

  • Add a carOne long form with photos alongside

    VIN, year, make, model, condition, transmission, drive train and colours on the left; photo upload with a chosen thumbnail on the right. Can be saved as a draft.

  • SavedSaved cars and saved searches

    Saved cars keep the listing card; a saved search stores the model and price range with a "Search again" button.

  • NotificationsListing updates and preferences on one page

    Toggles for news, reminders and email above a feed of requests, approvals and declines.

  • MobileThe same account in a dropdown

    On phones the side menu becomes a selector at the top, and a bottom bar adds Home, Buy, Sell, Profile and More.

03Screens

Desktop, then mobile

Car Description form: labelled rows for VIN, year, mileage, make, model, trim, body style, condition, fuel, transmission, drive train, colours, stock number, description, YouTube link and Carfax report, with a photo upload area and five thumbnails on the right
Add a carEvery spec in one form, with photos uploaded and a thumbnail picked on the side.
A modal confirming 'Listing details sent successfully' with a note that the user will be told once the listing is approved, a 'Don't show it again' checkbox and a Got it button
SubmittedThe listing goes to review, and the seller is told what happens next.
Saved Products page: a three-column grid of car cards with mileage, collection, model, dealer location and price, each with a remove button, and pagination below
Saved productsSaved cars keep the full listing card, with Clear All and Select for bulk removal.
Notifications page with three toggles for news, reminders and email, above a list of notifications: request received, listing approved and published, listing declined
NotificationsPreferences on top, the feed of listing updates below.
Mobile profile: a My Profile selector, a greeting, an account info card with contact details and a list of recently viewed cars, with a bottom tab bar
Mobile profileAccount info and browsing history on one scroll.
Mobile saved searches: a list of cards with the model name, price range, a Search again button and a delete button
Saved searchesRerun a search in one tap.
Mobile settings with collapsible sections for account details, payment cards, billing information and password change with a strength meter
SettingsAccount, payment, billing and password as collapsible sections.
  • Add client and year to the header line (currently "Web platform · Case study").
  • The board covers only the account area; there are no browse or car detail pages in this section, so the case study does not describe them.
  • Helper text under the form fields and notification descriptions are placeholder; the case study does not describe that copy.
  • Confirm your role and whether the platform shipped.