Koby, built under the new rules

Worked between pool sessions at a family finca, entry 73-1’s extraction script grew overnight into something else: “esta sí la pienso como un producto… pasar de esto a un producto que la gente lo pueda utilizar, pues no es tan difícil” ▸ 2:17. Name: Koby, Julia’s twist on Kobo. The dashboard already shows reading time per book, annotation counts, a donut of highlights by color, a timeline with bars marking finished books, and filterable quote cards underneath ▸ 2:36.

The vision has a shape borrowed from two products: Goodreads for the content, and, Julia’s analogy, Strava for the soul ▸ 7:07, public reader profiles where your highlights live at their own URL, indexed by Google, so a stranger searching a phrase can land on your annotated bookshelf ▸ 5:00.

la disciplina nueva: la lista de lo que NO va →

But the entry’s real subject is what happens for the first time: the 73-2 methodology applied at birth. Watch the features get refused. Likes, comments, sharing? “Ahorita no lo va a tener”, v0 is profiles and search, period ▸ 7:28. Kindle support? “La aplicación está hecha para esta cosa; ya después si la gente dice ‘quiero Kindle’, ahí miro” ▸ 3:22. Julia’s book-community idea runs into the edition problem, every printing and pirate copy titled differently, and instead of the heroic centralization project, the answer is “eso se vuelve una locura”, skip it ▸ 6:09.

Divo spent half its build on trimmings for users who never came. Koby, one day old, already has a dashboard, a vision, a name, and, more valuable than any of them, a list of things it refuses to be yet…