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?






