Keep v0 fitness-app revisions traceable before deploying
At a glance
Adrian Noel used v0 to ship The HIIT PIT, adding change-reporting rules after prompts rewrote unrelated code. This workflow is listed under app-development, change-tracking, deployment-validation, vibe-coding.
He supplied a Figma moodboard and iterated in v0's browser. He asked it to leave unrelated files alone, bump package.json after code changes, and list each changed file with a reason. His workflow tested a Vercel URL, downloaded the ZIP, updated Git and pushed live.
How it went
He reported a functional app and 14 users after three days, and more than 110 revisions in another reply.
Worth knowing
He later reported missing files and a Vercel deployment still showing package version 0.1.0 while his app was at 2.0.6.
Save ideas in this browser. Upvotes count across the board.
A creator replaced Dots/Muse with a Grok Bot lattice—Whop for payments, Vercel+GitHub for the site, Gmail inbox bots that only draft, Notion CRM, and a morning chief-of-staff audit.
A thread claims a whole online business runs on 16 Grok Bots plus Opus for ~$165/mo with Whop, Vercel, Notion, Sheets, and Cursor wired in—founder's job is approving each consequential step.