Apps #
I build small apps and games, mostly by myself, mostly for the reason that I wanted them to exist. These are the build write-ups: what the thing is, how it works, what I got wrong, and screenshots of the real product rather than mockups. Every app, with a link to each one, is listed on the home page.
The builds #
Building an Offline AI Chat App
A language model running entirely on your own phone. No server, no subscription, no data leaving the device. It works on a plane.
Building a Private Speech-to-Text App
Whisper on-device, so your audio never gets uploaded anywhere.
Building Capybara Crossing, an Arcade Game
A small arcade game, start to finish, including the parts that did not go well.
Raw GPS speed is noise. Most of the work was turning it into a number you can trust at a glance while driving.
Building a Credit Card Tracker Without a Server
Which card to pull out, and a warning before an annual fee posts. No bank connection, on purpose.
Building a Retirement Planner That Does Not Lie to You
Why a single projected number is misleading, and what to show instead when the curve stays flat for eight years.
What they have in common #
Every one of them runs entirely on the user’s device. No backend, no account, no subscription, nothing uploaded. That started as a constraint, because one person cannot operate infrastructure, and turned into the most interesting thing about the work. A privacy property enforced by architecture is worth more than one asserted in a policy, and no servers means no costs to recover, which is why they are free.
The general form of that argument is in on-device AI explained and what happens to your data when you use AI. The hosting side of the same idea is in the free tiers I ship everything else on, and the model economics are in the cheap AI models I use.