I am a backend dev, and building a mobile app for the first time, It is a toy sized project right now and it works, would have indeed taken me 5x the time to get to that point on my own.

I know from experience that to make it a non-toy project I am probably going to need to spend some, if not most of that saved time cleaning up in the future due to technical debt.

For backend, it is mildly useful at best, helpful with boilerplate and when I know exactly what needs to be built. I have not yet firsthand experienced these 10x, 100x productivity gains.

Frontend, forms,tables and generic dashboards is pretty good, I am sure one could get it done faster and better over the long term with proper technique and methods, but I just hate css

AI is an extremely powerful weapon against a blank page.

It's much easier to take "well now I have an app, which after using for a bit I find it sucks in <quantifiable list of ways>" and then fix them, than it is to start from absolutely nothing.

Thats a big sometimes for me. I am unfamiliar with the app development process. For backend,I would rather design the whole thing from scratch rather than try to fix a broken architecture. For frontend, maybe that is true, but I haven't had the chance to build anything complex, just forms and tables.

its a great solve for the cold start problem +1

Honestly it sucks at Web apps of any meaningful complexity too. On my huge complex app at work, nothing can coax it to do an even average quality job in one pass. It hates following my project conventions even after spelling it out in MDs