How these apps were built, why they were designed this way, and what we deliberately left out. No content calendar, no newsjacking — posts happen when there is something to say.
2026-11-22 · WenYaJi
A monitor's display is seven-segment, so reading it with the camera needs no large model: stroke by stroke, digit by digit. Voice entry runs on the device only, and says so when it cannot hear you. The grades are six neutral words — diagnosis is the doctor's job, and the app's job is to have the numbers ready.
2026-11-22 · Yimaji
A weighted median for the cycle length, MAD for the spread, a window of ±1.28σ, never narrower than 2 days and never wider than 10 — the uncertainty in a prediction is drawn rather than hidden. And confidence does not mean “accurate”, it means “enough to compute on”.
2026-11-22 · Pure Pace
Every fix is a point plus an error circle. Five gates (stale, accuracy, time, teleport, jitter) and one stationary re-anchor remove the starting drift and the jumps across the river from the route, the distance and the pace together.
2026-11-22 · mkok
No speech recognition and no manual beat-tapping: the lyrics consume the notes of a lead-sheet MIDI in order, and a character stays lit for as many notes as it owns. Also, why alpha export goes wrong with premultiplied alpha.
2026-11-20 · DanceDouble
A song is cut into beats and sections; 36 movement clips (18 captured, 18 procedural); a beam search of width 16 with a set of cost terms you can explain one by one picks the arrangement. No neural network, no generative model — which is also why the wording matters where it is filed.