r/VibeCodeDevs • u/appsanic • 1h ago
ShowoffZone - Flexing my latest project Appsanic began as an AI that builds mobile apps. We ended up building an editor.
A year ago the plan for Appsanic was simple. You describe a mobile app, an AI writes it, done.
Getting a first version out of a model wasnât the hard bit. What we didnât see coming was how much work sits behind âok, now just move that buttonâ. Most of our time went there. A few things we learned, in case theyâre useful to anyone else building something where an AI edits existing work.
The prompt is the wrong place to keep a change small. âOnly touch the headerâ works until it doesnât. We check the change itself: if it touches anything outside the part that was selected, the whole thing is rejected before it lands.
Same goes for âdid it workâ. A model will say done either way. The pass or fail people see comes from the compiler and our own validation, never from the modelâs reply.
The AI gets no special door. Its edits go through the same path as a drag in the visual editor or a save in the code view: one transaction, all or nothing, one undo step. A lot falls out of that. Itâs why someone can keep editing while the AI is mid-run, and the two sets of changes get three-way merged at the end, like branches in git.
Data is the other line we drew. Apps talk to the userâs own Supabase project, and the model only ever sees table and column names.
Last one: build something that shouldnât fit. Ours was a 3D arena game. 19 TypeScript files, around 8,300 lines, no engine, written with a lot of help from coding agents. We made its rules deterministic so matches can be replayed in tests.
What did you think would be easy that wasnât?






