Preview build — apps, screenshots and Play Store figures are real; role / problem / outcome write-ups and timelines are still placeholder.
All work
Built

Partsapp

A three-app marketplace for spare auto parts — buyers, sellers and delivery partners, with maps, chat and ratings.

Client · Partsapp (Gadi Repair) Domain · Marketplace Timeline · 2024sample
Partsapp
Screenshot coming soon

Draft copy — the role, problem and outcome below are placeholder text pending review. Feature list and tech stack are accurate.

My role

Sole Flutter developer for all three apps, built from a shared models / API layer.

The problem

Three audiences (buyer, seller, rider) needed three apps that stay consistent as the platform evolves — without maintaining three separate codebases.

What I built

  • Customer: catalogue, search, cart, checkout, live order tracking on Google Maps, ratings
  • In-app buyer / seller chat: text, images, voice notes, emoji, file attachments
  • Google Places address picker, geolocation, reverse geocoding
  • Vendor and delivery apps sharing the customer app’s models and networking
  • Push + local notifications, multi-select filters, PDF and photo viewers

Stack

FlutterProviderhttpFirebase Core/MessagingGoogle Maps + Placesrecord / audioplayersflutter_rating_stars

3 apps · 41,690 lines of Dart · 81 screens

Outcome

Full three-app suite delivered; ~81 screens.