Katter Mobile
Kotlin on one side, TypeScript on the other, on hardware I run myself. The models those tools lean on live on a machine in my office — details are further down the page.
01What I build
Both get the same treatment: a budget written down before the first line, and profiling before polish.
Android
Native Kotlin and Jetpack Compose, offline first. State lives in Room and syncs when it can, so the app is useful in a tunnel and consistent later. Material 3 throughout, because fighting the platform on a phone is a fight you lose.
Games & web
TypeScript plus Canvas and WebGL, behind a frame budget I actually measure. When a scene misses that budget the scene changes, and the budget stays put. Sixteen milliseconds is the first thing written down, not the last thing checked.
02Local AI
It is a dedicated machine that serves open-weight models to my own tools over an OpenAI-compatible API. I patch the inference engine myself, watch tok/s while a job runs, and pick a quantization level instead of picking an invoice.
Running it here means a prompt never leaves the room and nothing gets rate-limited mid-debug. The failures are mine too: when something crawls I profile it and keep the patch, which is how the batching work on this engine happened at all.
03How I work
Design, code, and the machine it runs on are all mine. Nothing waits in a queue, so something decided in the morning is usually running by the afternoon.
If I say it is fast, there is a repeatable run behind that claim. When the numbers are not in yet, I say so rather than fill the gap with a comparison to nothing.
An app that works offline, a model that stays on my LAN, analytics that follow nobody. Convenience gets traded away quietly, and it is worth it more often than people expect.
04Support
No ads, no trackers, no paywall. If any of this is useful, Ko-fi is how it stays that way — contributions go toward time and hardware for the next thing.
Ko-fi handles the whole process on their platform, so this site never sees how anybody pays, and nothing here sits behind a paywall.
05Contact
Questions, bug reports, or a strong opinion about EXL3 batching: write to [email protected]. I read everything and I answer when I can.
Write an email