A questionnaire web app requires a solid online database. I started off with a combination of Vercel and Neon for frontend and backend, but one of them required GitHub to be involved. This kinda complicated things because to make it work, stuff had to be done in all three and that didn't't always work well. Changes here required more changes somewhere else and that dance continued until a partial reset became necessary. However, by then the whole thing had become such a mess that a complete reset was the only reasonable way out.
Now I have to admit that I was not saving every step on GitHub, but there was a good reason for that. There were so many different edge functions and functionalities required that even with GitHub it would have been hard to keep track, especially since GitHub itself was part of the mess. Instead of a reset I ended up switching to a combination of Netlify and Supabase and the problems we faced there were product design issues, not software functionality.
