How codebymarvel/fundix works
Fundix appears to be a vehicle-service marketplace backend: customers create service requests, fund escrow, and track job completion; mechanics apply, accept funded jobs, and perform work; administrators manage participants, zones, requests, and escrow. The visible implementation is an Express/Supabase backend, alongside Flutter platform wrapper files; no Flutter feature source is present in the supplied tree. The README describes only a starter Flutter project, so marketplace capabilities come from the sampled backend. Some subsystems are represented by directory paths because their implementation files were not excerpted.
Main entry points: index.js Backend entry · firebaseConfig.js Supabase data store · authMiddleware.js Token middleware · requestService.js Request and inspection logic
Components 28
API and identity
- Backend entry
backend/index.js - Auth routes
backend/routes/authRoutes.js - Auth controller
backend/controllers/authController.js - Login and signup
backend/auth - Token middleware
backend/middleware/authMiddleware.js - Token verifier
backend/auth/tokenService.js
Service jobs
- Request routes
backend/routes/requestRoutes.js - Request controller
backend/controllers/requestController.js - Request and inspection logic
backend/services/requestService.js - Diagnosis API
backend/controllers/diagnosisController.js - AI diagnosis support
backend/llm - Mechanic routes
backend/routes/mechanicRoutes.js - Mechanic controller
backend/controllers/mechanicController.js - Mechanic operations
backend/services/mechanicService.js - Customer API
backend/controllers/customerController.js
Payments and escrow
- Payment routes
backend/routes/paymentRoutes.js - Payment controller
backend/controllers/paymentController.js - M-Pesa integration
backend/services/mpesaService.js - Escrow release
backend/services/escrowReleaseService.js
Marketplace operations
- Service zones
backend/services/zoneService.js - Admin routes
backend/routes/adminRoutes.js - Admin controller
backend/controllers/adminController.js - Admin operations
backend/services/adminService.js - Supabase data store
backend/firebase/firebaseConfig.js
Other components
- Customer
- Mechanic
- Administrator
- Safaricom M-Pesa
Connections 39
- Backend entry → Auth routes: mounts
backend/index.js - Backend entry → Request routes: mounts
backend/index.js - Backend entry → Payment routes: mounts
backend/index.js - Backend entry → Mechanic routes: mounts
backend/index.js - Backend entry → Admin routes: mounts
backend/index.js - Auth routes → Auth controller: routes to
backend/routes/authRoutes.js - Auth controller → Login and signup: delegates to
backend/controllers/authController.js - Request routes → Request controller: routes to
backend/routes/requestRoutes.js - Request routes → Token middleware: verifies
backend/routes/requestRoutes.js - Token middleware → Token verifier: verifies token
backend/middleware/authMiddleware.js - Token verifier → Supabase data store: reads profile
backend/auth/tokenService.js - Request controller → Request and inspection logic: creates and fetches
backend/controllers/requestController.js - Request and inspection logic → Supabase data store: reads and writes
backend/services/requestService.js - Request and inspection logic → AI diagnosis support: uses diagnosis support
backend/services/requestService.js - Request and inspection logic → Service zones: uses zone logic
backend/services/requestService.js - Request controller → Escrow release: gets release buffer
backend/controllers/requestController.js - Backend entry → Diagnosis API: mounts diagnosis routes
backend/index.js - Diagnosis API → Token middleware: uses
backend/routes/diagnosisRoutes.js - Mechanic routes → Mechanic controller: routes to
backend/routes/mechanicRoutes.js - Mechanic routes → Token middleware: verifies
backend/routes/mechanicRoutes.js - Mechanic controller → Mechanic operations: delegates to
backend/controllers/mechanicController.js - Mechanic operations → Supabase data store: reads and writes
backend/services/mechanicService.js - Customer → Request routes: submits requests
backend/routes/requestRoutes.js - Mechanic → Mechanic routes: manages availability and jobs
backend/routes/mechanicRoutes.js - Customer → Payment routes: initiates payment
- Payment routes → Payment controller: routes to
backend/routes/paymentRoutes.js - Payment controller → M-Pesa integration: initiates payments
backend/controllers/paymentController.js - Payment controller → Supabase data store: initializes and funds escrow
backend/controllers/paymentController.js - M-Pesa integration → Safaricom M-Pesa: calls payment API
backend/services/mpesaService.js - Safaricom M-Pesa → Payment controller: posts callbacks
- Backend entry → Escrow release: loads release service
backend/index.js - Administrator → Admin routes: manages marketplace
backend/routes/adminRoutes.js - Admin routes → Admin controller: routes to
backend/routes/adminRoutes.js - Admin routes → Token middleware: verifies token
backend/routes/adminRoutes.js - Admin controller → Admin operations: delegates to
backend/controllers/adminController.js - Admin operations → Supabase data store: manages marketplace data
backend/services/adminService.js - Admin operations → M-Pesa integration: uses payout functions
backend/services/adminService.js - Customer → Customer API: uses customer functions
- Escrow release → Supabase data store: processes escrow releases
backend/services/escrowReleaseService.js