A car workshop, run from one live thread.
Indian car workshops coordinate over calls, paper job cards and a dozen WhatsApp groups. GarageFlow turns each job into one structured, real-time thread: the technician documents the work with photos and voice notes, parts land as priced line items, the manager approves the estimate from a push notification, and the owner sees the invoice, GST and collections without asking anyone.
I designed and built both halves — the Expo mobile app and the NestJS API — contract-first, so the app and the server never drift.
The reel follows a single Tata Nexon through the workshop — the same thread as the technician, the manager and the owner see it.
03Product
Every feature hangs off one idea: the job card is a conversation, and the conversation is the record.
Comments, photos, voice notes, parts and status changes stream into a per-job room. WhatsApp-style ticks go from sending to sent to read; optimistic sends reconcile with the server echo.
Parts and labour roll up into an estimate; the manager gets a push, reviews the lines and approves or declines — the decision lands back in the thread and releases the job.
Hold-to-record voice notes with lock and slide-to-cancel gestures, compressed photo uploads via presigned URLs, and before/after completion photos on delivery.
Invoices split CGST/SGST for intra-state sales, record cash / UPI / card payments, render a PDF receipt and open the customer’s WhatsApp with the message pre-filled.
Collections, receivables, expenses, GST reports and party ledgers are derived from invoices, payments and expenses — never stored as snapshots.
Technician, manager and admin each get their own app shell; the API enforces the same roles with global guards, so a tech simply can’t reach finance.
The app shipped with the default Expo icon, so I drew one: a garage-shaped chat bubble with typing dots — the workshop, mid-conversation. The wordmark is Satoshi Black, the same face as the app UI.
SatoshiUI + wordmark — Regular to Black
The mobile data model is the contract: types/api.ts defines every shape, and the backend’s serializers emit exactly that — money in paise in the database, rupees and Indian date strings on the wire. Hover a node to trace its connections.
Serializers are the only boundary between Prisma rows and the app contract.
Deployed on Render (Singapore): a Docker web service with managed Postgres and Redis.
0 commits (app + API, 26 Jun → 10 Jul 2026), 0 API endpoints (OpenAPI contract), 0 data models (Prisma · PostgreSQL), 0 screens (Expo Router), 0 components (feature-grouped) and 0 roles (tech · manager · admin).
Counted from git, openapi.json and the Prisma schema.
26 Jun
The whole mobile app was designed and built against in-memory fixtures — the fixtures became the contract.
27 Jun
NestJS + Prisma stood up to serve that exact contract, with RBAC, money in paise and Indian formatting in serializers.
Early Jul
Mock → typed fetch client + TanStack Query; every screen reads live data, optimistic updates included.
10 Jul
Socket.IO job rooms with the Redis adapter, Expo push for approvals and deliveries.
The classroom, in every student’s pocket — and every parent’s.