[user43928]

I've also been having a wonderful time with the other approach, churning out reams of code for a mobile app.

It is taxing, the context switching is not easy. It takes effort to keep up with 3-5 conversations, remember what you deployed to the device, what is to be tested, and what feedback needs to be provided.

At the end of the day I am proud of the results, and I feel like I achieved something.

Contrary to popular belief it is still often hard work to vibecode.

Lots of QA work, UX decisions, debugging and steering efforts, as well as weighing architectural concerns and what should or should not be refactored.

While the code basically writes itself, the app still does not create itself on its own. Not to mention business and market research, as well as App Store Optimization.