Plan the database and backend before building
Front-end went fine, then the backend broke and the project stalled · Reddit r/vibecoding · u/Ok_Key_8113 · Mar 2026
A non-developer made progress on a front end with Copilot about 10 months earlier, then got stuck on the database and backend, and is now rebuilding from scratch.
The honest numbers
- Says about 10 months since the first attempt
- Says about 600 Lovable credits on hand
As stated by the source. Not independently verified.
Lesson
Sketch your data model and auth flow on paper before picking a tool. The backend is where non-developers most often get stuck.
Fix prompt
Copy this into your own AI tool (Cursor, Lovable, Claude Code, Bolt…). It's general guidance written by us. Review what the AI suggests before applying it.
I built my app with GitHub Copilot and want to make sure I'm not locked in. 1) Explain where each part of my app lives: code, database, file storage, auth, serverless functions and secrets, and which of them I can export. 2) Tell me how to get the code into my own GitHub repo and keep it in sync. 3) List what would need rebuilding if I moved hosting or backend, and roughly how hard each part is for a beginner. 4) Give me a step-by-step exit plan that keeps the current app live until the new one is tested. Don't change anything until I've approved your plan. Never ask me to paste API keys, passwords or .env contents; tell me where to check them myself.
Source: Reddit r/vibecoding ↗