SazCars — Car Auction App for the GCC

The Challenge

SazCars is a car-auction marketplace for the GCC. The product brings vehicle browsing, individual vehicle information and auction participation to mobile users in the UAE and Saudi Arabia, with Android and iOS versions.

A buyer needs enough information to decide which vehicle to follow before placing a bid. The interface brings together vehicle details, the current auction state and the available action. Those pieces need to remain understandable as information changes.

The mobile journey also includes moving between a list, a vehicle and the auctions the user is watching or participating in. A project like this needs the account, record and action responsibilities planned alongside the screens, including the paths where a request or connection is unsuccessful.

The Architecture

The product combines Flutter mobile clients, a .NET backend and Firebase. These layers support the application experience and the business records behind the auction. Their roles are related, while each has different interface and data responsibilities.

Flutter · Android & iOS

Flutter supports the mobile experience on both platforms. The app presents vehicle information, auction views and user actions, with platform-specific testing and release preparation alongside the shared application.

.NET backend

The backend is part of the product’s connected system. APIs and business records support what the mobile interface needs to read or change; the app and backend scope must agree about those operations.

Firebase

Firebase is part of the real-time application stack. Changing information needs an appropriate relationship with the business state and the way the client presents it to the user.

Vehicle information and auction state

The vehicle view brings its image, specifications and auction information together. Buyers can inspect the listing before following the bidding journey, with the supporting details close to the available action.

Auction lists and individual vehicle views serve different tasks. A list helps the user find or track an auction; a detail screen provides the information associated with one vehicle. The visual hierarchy should distinguish current status, supporting details and the action available to that user.

These flows also depend on accounts and connected data. Permissions, changing state, delayed responses and unsuccessful actions are important requirements to define for an auction product. They affect the interface and the backend contract together, rather than only the appearance of the bidding button.

Cross-Platform on iOS and Android

The Android and iOS versions use Flutter, giving the product a shared application implementation. Each platform still requires suitable integration checks, signing, device verification and store material. Shared code supports related behaviour without making the two release processes identical.

SazCars is available on Google Play and the Apple App Store. The vehicle and auction views connect discovery with participation across the Flutter application, .NET backend and Firebase stack.

Delivered scope

The project brings a vehicle-auction experience to Android and iOS through Flutter, connected with a .NET backend and Firebase. Its screens illustrate the relationship between discovery, vehicle information and participation. For a similar product, those user tasks and the records behind them are the starting point for scope and acceptance.