Plan the risk first
Before building, I write down what could stop the project. For Hangar 64 that was data, not code.
Founder & builder, Hangar 64
I'm building Hangar 64, an iPhone app that identifies a Hot Wheels car from the code on its package and tracks a collection like a Pokédex. I took it from an idea to a working beta on my own: the product plan, the design, the data pipeline, the app, the backend and the releases.
This site is part product page, part portfolio. The build log is the honest version of how it's made, including what went wrong.
Hangar 64 touches every part of shipping a product. These are the areas I owned, and the tools I used for each.
Wrote the plan, feature phases and risk list, chose what to cut, and ran a friends-and-family beta with weekly builds.
Roadmap · GitHub Projects · TestFlightDesigned every screen through mockups and phone tests, and set the app's visual rules, like what each color means.
Canva · Figma · HTML mockupsBuilt the iPhone app: camera scanner, garages, Dex, series sets, profiles and accessibility.
TypeScript · React Native · ExpoDesigned the database with row-level security, edge functions, scan limits and an app-wide cost cap.
Supabase · Postgres · DenoWrote import scripts that turn fan-made wiki tables into a clean catalog of 7,900+ cars, with photos and series.
Python · MediaWiki APIBuilt the card reader on Claude with a cheap-first, retry-if-needed design, plus crash reporting and builds.
Claude API · Sentry · EAS · CloudflareBefore building, I write down what could stop the project. For Hangar 64 that was data, not code.
Two or three options for every screen, using real content, before anything gets built.
Every feature is tested on my own phone, with real cards, before it's committed.
Small TestFlight builds with one clear theme each, and notes on what changed and why.