Development progression

AI will always and always produce good back end and will suck ass water when it comes to front end

So of course it is obvious that you try to build your back end first

You can’t test everything so that you’re sure it is doing the job it has to do

If you are smart you might also follow the philosophy I have outlined in previous few articles

And after that it’s starting to get serious we need to implement you as so our clients can use this

Its really tempting to have that really tasteful vision of how the app should be aesthetically

But this is the exact moment when you’re supposed to forget about it

For God’s sake make the most bare bones and ugly version of your front end at the start

And implement all your features in this ugly skeleton

Make sure each and every endpoint from your back end is being represented in this version of your “UI”

The biggest problem you will face when vibe coding is that the UI being created does not represent all the features you have created infrastructure for in your back end

Even the UI it does create it is so complicated and haywire that complexity itself creates a lot of problems

And you’re left firefighting that complexity instead of having your actual implementation get done

So the clear progression is:

Ideate > document your idea > Model out the user flow and the data flow > Create the back end > create the bare bones UI > flesh it out with styles