← all work

$ open ./work/gigmission

GigMission

My own product for production companies that rent out sound, light and video gear. It tracks warehouses down to every single unit, books equipment for events against what is really free, plans the vans and trucks, and keeps the crew talking. One Expo codebase runs on iPhone, iPad, Android and the web.

platforms

iPhone · iPad · Android · web

commits

700+

typescript

~140k

lines, app + API + contracts

live

app.gigmission.com
since Aug 2026

GigMission on iPad: an SM58 microphone line with 17 of 20 units free, a six-week availability chart and a grid of every unit with its state
One stock line on iPad: what is free now, the lowest point over the next six weeks, and every unit with its own state.

// what it's for

the job it does

A production company lives on three questions: what gear do we have, where is it, and who is taking it where. GigMission answers them in one place. Every microphone, speaker and LED panel is a unit with a serial and a state, so you always know which one is broken, which one is out with a client and when it comes back.

Planning an event books gear for its whole pack-to-unpack window, and the app refuses to promise what isn't there. The same numbers drive the stock list, the event wizard, the send-outs and the delivery run sheets.

// what it does

five tabs

Stock

  • Every unit tracked, with states from New to Needs repair
  • QR labels with random codes, and a scanner
  • All-or-nothing CSV import, low-stock alerts

Events

  • A four-step wizard: basics, schedule, equipment, review
  • Crew assigned from friends, each with a role to accept
  • Gear booked against real availability, with shortages shown inline

Fleet

  • Vehicles on a weekly board, double bookings flagged
  • Delivery run sheets with load weight against capacity
  • A load checklist ticked off as gear goes on board

Send-outs

  • Planned, out, overdue, returned or cancelled
  • A signed PDF slip with serials and a QR code back to it

People

  • Friends, chat with read receipts, and a mailbox for invitations
  • Pushes with Accept and Decline right on the banner

Sharing and sign-in

  • Share a warehouse, item, vehicle, event or company as Editor or Viewer
  • Google and Apple sign-in, and a second factor by email code or Face ID

// screens

demo data, not real people or companies

ipad

Events on iPad as a continuous month calendar, with multi-day events and their pack and unpack days
Events as one continuous calendar that zooms in and out. Multi-day events run across the weeks, with their pack and unpack days as dashed bars.
An event on iPad: dates, venue and notes on the left, the gear list with a shortage warning on the right
An event with ten lines of gear. One line is short for these dates, so the page says so before anyone loads a truck.
Fleet board on iPad: nine vehicles across a week with outbound and return runs
The fleet board: every vehicle's runs for the week, and which ones are free.

iphone

Stock on iPhone grouped by warehouse, with low stock and need attention filters
Stock across five warehouses, with what needs attention one tap away.
An event on iPhone with a shortage warning and its pack, run and unpack times
The same event on a phone.
A delivery run sheet on iPhone with load weight and a checklist of lines to load
The run sheet for a truck: weight against capacity, heaviest gear first.
A chat between the owner and a crew member on iPhone
Chat with the crew, with read receipts.

web

Stock on the web as a table with available units, SKU, location, warehouse and category
On a wide screen the tabs become a sidebar and stock becomes a table: 2,331 units across 190 lines.
A stock line on the web with free units, availability chart and unit grid
A stock line on the web, in two columns.
Send-outs on the web with overdue, out and planned rows
Every send-out, with the overdue ones on top.
People on the web: friend requests, recent chats and an open conversation
People and chat side by side.
The plan event wizard as a panel over the stock page
Creating opens as a panel over the page on the web, and as a sheet on phones.

// how it works

architecture
app   expo router · react native · one codebase
      ├─ iPhone / iPad / Android  native lists, sheets, haptics, camera, Face ID
      └─ web                      static export, installable as a PWA
      data: TanStack Query · forms: TanStack Form · styles: Unistyles
            │
            │  REST + one WebSocket (chat and live "changed" frames)
            ▼
contracts   zod schemas, permission keys and catalogs shared by both sides
            │
            ▼
api   fastify · prisma 8 · postgresql · JWT with rotating refresh tokens
      ├─ ledger    one answer to "is there enough", under the item's row lock
      ├─ pdfs      send-out slips drawn with pdfme
      └─ mail      verification codes, invitations, new-device alerts
            │
            ▼
google cloud   Cloud Run for the API and the site · Cloud SQL · Secret Manager · deployed by GitHub Actions and Cloud Build

// hard parts

what I'd talk about in an interview

Never promise gear twice

Every "is there enough" question goes through one ledger. An event holds its gear from pack to unpack, a send-out from leaving until it is back, an overdue one with no end, and a unit that needs repair is never counted. The check on save runs under the item's row lock, so two people booking the last units at once can't both win.

Units as derived rows

A stock line says "20 × SM58"; each of the twenty is a row with its own serial, state and history. Every change of quantity syncs the unit rows in the same transaction, and shrinking a line is refused if it would drop below what is already booked.

Live on every screen

Each write declares which kinds of data it changed. This device refreshes those queries, and every other device gets a "changed" frame over its socket and does the same. A send-out returned on one phone updates the stock count on another about a quarter of a second later.

Works offline, safely

A signed-in phone opens without a connection, from a saved copy of what it last saw. It doesn't queue writes: availability is decided on the server, so a send-out made offline couldn't know if the gear was still free.

One contract for both sides

Request and response schemas live in a shared package. The API parses through them, the app checks responses against them in development, and a snapshot test fails the build if a change would break an older app still in people's pockets.

// stack

tools
app
expo sdk 58, expo router, react native, tanstack query, tanstack form, unistyles, legend list, react-native-mmkv, keyboard controller
api
fastify, prisma 8, postgresql, zod, jose, argon2, websockets, pdfme
shared
a contracts package of zod schemas, permission keys and catalogs
platform
google cloud run, cloud sql, secret manager, github actions, cloud build, eas, expo updates
quality
vitest unit and integration suites (a database per worker), playwright end-to-end checks against fixtures

My own product. The screenshots use the demo data from the app's own seed script: invented people, companies, events and stock.