The player has a new name. My son picked it.

We’re back from two weeks in China. No work got done, which was the point, and the player came home with a name: Robi.

The name problem is old. The first prototype was named after our son, and that name ended up all through the code and the early site. It never sat quite right to name a product after one kid, and that got clearer after our second boy was born. It was no longer a device for our firstborn. It was a device for both our boys, and for all kids. For a few months the working name was Pip.

Then, on the trip, our son’s grandmother bought him a small maglev train set. Two trains in the box. He named them himself: one was Dot, the other was Robi. Robi sounds like a robot, a friendly one, the kind a kid would name and claim. Robi stuck. So the product isn’t named after our son. He named it.

What the trip cost: the app beta was due on May 14th, four days after we flew out. It didn’t happen. The fixes for the first-run bugs sat waiting for my review the whole two weeks, and so did the privacy policy the invites can’t go out without. The new date is June 1st, starting with a handful of families we know.

The trip gave one more thing besides the name: a small MUJI speaker, bought because the speaker inside is almost exactly the size of Robi’s. It’s going on the bench to come apart.

Before we left, I also paused the AI agents I set up in April. They don’t really work without babysitting, which defeats the point. I’ll come back to how I changed the setup in a later note.

Two earlier shells: the clear print from March and the white one with the red handle from April.

Next, in order: the privacy policy live, the waiting fixes merged, then the invites. Then the old name comes out of the code and the site.