What WASDAai says is entirely fair (though caveat: a shockingly large number of production apps have really mediocre implementations from the war stories I've h

What WASDAai says is entirely fair (though caveat: a shockingly large number of production apps have really mediocre implementations from the war stories I've heard). But: This description sounds less like "I am making a CRUD app" and more like "I am making a generic CRUD app framework/dev tool". Which is fine, and yes LLMs are not yet good enough to vibe their way at that scale, but it's not the same thing as any specific, concrete, CRUD app that such a tool may or many not also produce. Actually, it gets worse: > - Choosing the best UI framework for the requirements of the app. I actually had to write a custom react-like library for this. Danger, Will Robinson, danger! UI frameworks sure are fun to write. Done it loads of times myself. But one of those times was before jQuery existed, and was because it was before jQuery existed. Another was before Cocos2d existed, and because it was before Cocos2d existed. If this was a fun side project then sure, have at it, but as a startup? I've seen people want to reinvent every part of their stack, as you are doing, and it took them 14 years to ship as Early Access. Unless you're literally one of the FAANG companies, then devs — including ones you may need to hire, even if I'm reading the wrong thing between the lines and this isn't a CRUD-maker, you'll probably need to hire people at some point — aren't going to want to learn yet another UI framework to customise the output of your product.