Auto Cllan: A Multi-Sided Vehicle Marketplace

A normal marketplace has two sides: buyers and sellers. Auto Cllan has more — buyers, sellers, shop owners, and service workshops, each needing different tools inside one app. Leading that build meant designing for multiple roles without shipping multiple apps.

What is a multi-sided automotive marketplace app?

A multi-sided automotive marketplace app connects everyone in the vehicle lifecycle — buyers, sellers, shops, and repair workshops — inside one platform for buying, selling, and servicing cars and bikes. Built in Flutter, Auto Cllan lets users browse and search listings, sellers and shops manage their inventory, and workshops handle service requests, all from a single mobile app.

Leading this project, the hardest decision was structural: how do you serve several distinct user types without the codebase — and the UX — collapsing into spaghetti? The answer was role-scoped navigation and shared repositories, so each role gets a coherent app built on common foundations.

The brief

Auto Cllan simplifies buying, selling, and servicing cars and bikes by connecting users, shop owners, and workshops in one platform. I led the development, which meant delivering:

• A public marketplace for browsing and searching vehicle listings
• Seller and shop tools for creating and managing listings
• Workshop tools for receiving and handling service requests

TODO: confirm the team size I led, target platforms, and whether payments or in-app service booking were in scope.

Role-scoped architecture

Instead of branching logic all over the UI, the app resolved a user's home experience from their role, then reused the same data layer underneath:

Widget homeForRole(UserRole role) {
  switch (role) {
    case UserRole.buyer:
      return const MarketplaceHome();
    case UserRole.seller:
      return const SellerDashboard();
    case UserRole.workshop:
      return const WorkshopDashboard();
  }
}

Each dashboard consumed the same listing and service repositories, so a change to how listings are fetched or cached happened in one place instead of forking across three roles. That's what keeps a multi-sided app maintainable as it grows.

What leading the build actually involved

Beyond writing code, leading Auto Cllan meant making the architectural calls early — how roles are modelled, how listings and services are structured — so the rest of the work stayed unblocked, and keeping the marketplace, seller, and workshop flows consistent as features landed. TODO: add specifics on team, timeline, and my exact responsibilities.

Results

Auto Cllan brought buyers, sellers, shops, and workshops into a single Flutter app covering the full buy–sell–service loop. TODO: add real listing/user numbers and store links once available.

Building a marketplace with more than two sides?

Multi-role marketplaces are where a lot of app projects quietly go wrong. If you're planning one and want it to stay clean as you add roles and features, I've done exactly this and I'm happy to help you scope it right from the start — reach out, or find me on Fiverr and Upwork.