The tools behind a one-person app

Expo, Supabase, Claude, the Hot Wheels wiki and a lot of small scripts: what Hangar 64 is built with, and why.

Hangar 64 is built by one person, so every tool had to earn its place by saving time. Here's the stack, and the reason behind each piece.

The app: Expo and React Native

The app is written in TypeScript with Expo and React Native, using Expo Router for screens. One codebase could later run on Android too, and Expo Go let me test every change on my own phone in seconds by scanning a QR code. Builds go out through EAS, Expo's build service, straight to Apple's TestFlight.

The backend: Supabase

Supabase holds the catalog, every user's garage, follows and scan counts. It's Postgres underneath, with row-level security so each person can only see and change their own cars. A small edge function handles card reading and enforces daily scan limits.

Reading the card: Claude

The scanner sends a cropped photo of the code to Claude. A fast, cheap model reads every card, and if it can't read the code clearly, the same photo is retried once with a stronger model. That keeps hard photos working without paying top price for easy ones. Each person gets 50 scans a day, and the whole app is capped at 1,000 a day so a busy launch can't spend the budget.

The catalog: the Hot Wheels wiki

There's no official Hot Wheels API. The catalog comes from the Hot Wheels Wiki (shared under CC-BY-SA), pulled through its public API by Python scripts I wrote for each line: mainline, Silver Series, Premium and RLC. Wiki tables are written by hundreds of fans, so the scripts have to handle merged cells, two cars in one pack, chase cars listed as "0/5", and pages that cover several years at once.

Everything else

  • Sentry for crash reports, without personal data.
  • Cloudflare for this website, the domain and email forwarding.
  • GitHub for code, a project board for the roadmap, and Actions for small automated jobs.
  • Canva and Figma for app icons and screen mockups.
  • Claude Code as a pair programmer: I describe a feature, review mockups, test on my phone and decide what ships.
What I learnedFree tiers are great for starting, but each one has a catch. Knowing where those limits are matters as much as knowing the tools. The next post is about one of them.