The phone work from this month is on the live site. A phone with WebGPU, which means Chrome on Android 12 or later or Safari on iOS 26, opens straight into the place, in the same engine a desktop gets.
For most of the month that was not true, and this log said so, entry after entry marked in testing. Those marks have come off the phone entries, because they now describe what a phone actually gets.
Every way of moving has controls of its own, drawn on screen the whole time and sized for a thumb. The car and the bicycle steer on an arc that knows how far you slid, not just which way. Walking has a stick, and a lock for the long way round. The drone flies on game sticks with the camera on the right. Pause is a round button at the top, and every load has a way back out.
Most of the month went on the parts nobody sees until they fail: a gesture the browser takes away mid-drag without saying so, a stick that jumps when the page goes full screen under a held thumb, a slow connection that looks like a dead one. The stolen gesture has a post of its own further down; the rest are in the changelog.
Two things are not finished. Some phones have a browser that can run this and hardware that cannot: the town comes out wrong, the phone gets hot, and the tab gives up. A check that tells those phones so before anything loads is built and in testing. And frame rates on older phones are still being measured, one handset at a time.
If it runs badly on yours, please say so through the contact page. The phone that decides whether this works is not the newest one.