Useful, usable, unfinished
Shipaton deadline tomorrow: three hours lost to a blinking card, a Gemini outage that exposes the missing retry path, SHA-1 keys he doesn't fully understand, and a $25 Play Store fee he has to borrow, and the decision holds: ship it in its current state.
// trace: where this idea came from
- ↳ video diary @ 5:57 (la decisión de publicarlo así)
- ↳ video diary @ 9:12 (el mensaje que nunca llega)
- ↳ video diary @ 14:37 (el fee de $25)
- ↳ Entry 114-4: Three days short (el conteo regresivo que anticipó esto)
The day before the Shipaton deadline opens with a bug that costs three hours: send a message, Severo answers, and a millisecond later the card blinks ▸ 4:38. He doesn’t fix it. What he fixes instead is the decision the countdown entry left hanging: “tengo que sacarlo en el estado actual, no está perfecto, está útil, usable” ▸ 5:57. The whole objective was to deliver for this competition; a polished thing that misses the window delivers nothing.
The remaining list is instructive because none of it is features. RevenueCat, “como un Stripe, pero para servicios móviles” ▸ 7:03, is the host’s required SDK. Google login needs a thing called SHA-1 he admits on camera he doesn’t fully understand ▸ 12:27, with a test key and a production key and a warning not to lose the second one ▸ 13:50. The Play Store wants a one-time $25 developer fee, “en estos momentos sí es mucho para mí” ▸ 14:37, borrowed from Julia against five jars of Nutella ▸ 15:16.
útil y usable le gana a perfecto e inédito →
The best lesson arrives by outage: the Gemini API goes down for an hour and a half ▸ 8:32, and because Severo is cards, one message per card, a response that never arrives kills the thread forever, there’s no retry button yet ▸ 9:12. A dependency failure just wrote his backlog for him. And the advice distilled from a month of this, still untested on a real emulator ▸ 10:37: if it’s your first app, go web MVP first, mobile has its own tax ▸ 11:43…