Software engineer in Phoenix. Five years at Amazon, now CTO at a strategy firm. Nights and weekends I run a one-person app studio. The tools below came out of taking two apps through App Store review, with two more behind them, and automating everything that hurt the second time.
It reads your App Store Connect state and tells you what is actually wrong: a version that looks submitted while nothing holds it (that one cost me eighteen days), products stuck in the wrong state, a missing analytics report. It is GET-only by construction, so it cannot change a listing even by accident.
The fastlane lanes I use for every release: signing that survives a certificate wipe, TestFlight pushes, submission with in-app purchases attached correctly, and analytics report requests you have to create before launch rather than after.
Everything above, plus the scripts, CLI and agent skills that take a project from a plan to a TestFlight build. You prompt Claude Code instead of learning fastlane, code signing and App Store Connect first.
Everything I am building right now, unfinished things included. Hover or tap one to inspect it.
A daily challenge app built on trading card mechanics. Five cards are dealt each day; you commit to the ones you will actually do. App Store · cardhabitapp.com
An idle tycoon game about running an AI startup. Train models on questionable data, ship them before they are ready, raise absurd rounds with a straight face. App Store · Jackrabbit Games
A video store tycoon set when renting a tape was the whole evening. Shipping this year.
Build a haunted attraction, then look at the photo of your guests on the way out.
A submission can read as queued while nothing holds it. A signing error usually names the wrong cause. Analytics undercount, and every rate you compute from them is wrong until you find out why.