Public simulation. The journey below is fabricated, not a live queue. Private operational Studio records owner decisions only; connected agents, usage tracking and automated weekly notes are future possibilities.
BuildsStudio: a system for building systems
Studio isn't another family app. It's a reusable layer for governing how software evolves, designed to live inside each app I build. This public page remains a specification and simulation. A separate private MVP now records intake, evidence, owner decisions and manual rollout approvals; the connected capabilities below are proposed, not running.
Two principles: reduce chaos, and never add work.
Follow one piece of feedback
A simulation with made-up data. Nothing here touches a real app.
Step 1 of 8
Feedback
Someone using a (pretend) recipe app taps the feedback button.
Feedback · confusion
“I can't find where my saved recipes went after the update.”
Captured: Saved tab · phone · v0.4
Six capabilities, as specified today
01
Feedback
People report a bug, a moment of confusion, or an idea, with an optional screenshot and context captured automatically.
02
Ticket queue
New → Next up → Building → Done / Won't do. Every change needs a ticket, bugs go first, the owner approves the work, and only one build is active at a time.
03
Usage insights
Lightweight daily tracking: a 14-day usage view, the core actions, and recent feedback.
04
Staged rollout
Introduce one core action first, unlock the next stage based on real usage, and keep manual release and rollback controls.
05
Build log
A chronological record of every change, which becomes the source for documentation.
06
Weekly notes
AI-assisted release notes drafted from actual changes and feedback, then reviewed and explicitly published by the owner.
How it fits together
Studio sits inside each app rather than above them. Each app keeps its own Studio data, separate from every other app. The proposed backend uses Supabase; the flow is prototype in Claude, deploy through Lovable.
People using the app
Use it, report what's broken or confusing, receive reviewed notes.
Studio inside the app
Feedback → tickets → one build → staged release → build log → draft notes.
The owner
Approves work, controls release and rollback, reviews and publishes notes.
Studio governs how the software evolves. Anton coordinates household experiences. They're distinct systems.
Possible future, not built
Opportunities I'm thinking about. None of these exist today.
- A portfolio-level Studio control center across apps
- Reusable lessons shared from one app to the next
- A publishing workflow that drafts notes from approved build history
Related notes
The build story is still being written.