Twelve testers, fourteen days

The morning opens with mercy: he wakes to “su perfil ha sido aprobado en la Play Store” and thinks second chance ▸ 5:36, the organizers having stretched the deadline another fifteen hours. Then he reaches the page that actually gates production: run a closed test with at least twelve testers for at least fourteen days before applying for public release ▸ 6:09. “No tengo 14 días” ▸ 8:09. The Shipaton ends there, not with a bug but with a calendar.

The entry earns its keep in the framing around the wall. Contrast, first: the web has no store at all, you buy a domain and publish whatever you want, whenever ▸ 1:37. And the store’s customs exist for a reason he remembers firsthand: the early Play Store was malware bingo, apps that made your phone hot enough to suspect Bitcoin mining ▸ 2:45. The friction that killed his deadline is the same friction that made phones trustable; both things are true, which is why the lesson stays procedural, repeated from yesterday’s electricity bill: “el error mío, no haber cacharreado con esta cosa desde más temprano” ▸ 8:32.

la tienda no es un dominio; es una aduana, y la fila empieza semanas antes →

Meanwhile the work continues past the dead deadline: an hour lost to a build that keeps signing itself in debug mode when the upload demands release mode, Cline analyzing the code over and over and finding nothing ▸ 10:14, and the architecture lesson underneath: publishing a paid mobile app means choreographing “una danza sincronizada” between Play Console, RevenueCat, and Google’s console, each refusing to move until another has ▸ 12:07…