Recreato
A system for kids' play centers that started as a client quote and became a product: desktop app, licensing platform, website and help center, built solo with AI
Recreato started as a sale and became a product.
The kids' play center my daughter goes to needed to replace its system, because the one they used was far too old. Since I was already a regular, I was first in line for the quote, and I decided to use that good relationship to propose a deal: I deliver the Windows app at half price, with a lifetime license, but all the rights stay with me.
For someone who wanted to pay little for something that worked, it was fair. For me too: if I can't sell it to anyone else, the loss is mine. That's when the development saga began: the system stopped being built for a single client and had to serve an entire market.
I committed to delivering it ready in 30 calendar days.
What is Recreato?
At the front desk, Recreato tracks each child's check-in and check-out with a timer that warns when time is running out and suggests charging for the extra time. It sells products with stock control, organizes parties and guest lists. It shows daily, weekly and monthly reports, plus birthdays and customers who stopped coming.
Doing this for one client is a project, but doing it for any kids' play center in the country is another: it needs licensing, payments, automatic updates, a trustworthy installer, a website, a help center, and a lot of willpower.
And 30 days to do all of it.
What was built
- Desktop app for Windows (direct download or Microsoft Store) and Ubuntu/Debian. Built with Electron, React, TypeScript and SQLite, it works offline and can back up automatically to any folder.
- Platform that issues licenses, takes payments and serves the updates.
- Customer portal to manage account, access and payments.
- Website live with a help center (nearly 40 pages), built entirely in Astro.
- Capture system that drives the app and takes the screenshots used on the website, in the help center and in the store. Every screenshot was made with it. When the app changes, the screenshots already show the new interface.
- Video generator for automatic videos, generated from code.
5 repositories in total.
AI, Claude Code and ADRs
Wait, you used AI?
Yes, a lot.
Even though I reviewed a lot of it, I didn't write the code itself. In fact, I didn't even write the help texts. The code works, the texts are correct, the screenshots are right and the help actually helps: all of it was done by subagents commanded by an agent that was commanded by me.
After understanding the client's pains and what the project needs to get off the ground comes the foundation of everything: the project's architecture. Preparing the system design, what you need, what you don't want, what you want to use, the repos required... All of this must be done before opening the terminal and typing claude.
When the work of writing code really starts, the groundwork is done, the main ADRs (Architecture Decision Records) are loaded automatically, and the main agent starts dispatching the subagents. In a nutshell: they implement the tasks in parallel waves, another isolated agent reviews the work, the main agent runs the mutations, and I verify and approve (or not).
The result
32 decision records, over 1,900 automated tests, version 1.3 live.
Today Recreato is running in production, updating itself, with the help center helping whoever needs it and great feedback.