I think there's still an underestimated burden to vibe-coding an app for a non-software engineer. I'm not recommending my parents vibe-code apps to solve problems, so I think the market is smaller.

But Roberto's use-case is definitely more sane than most.

I'm currently assisting three very non-programmer people in-house who did just this.

Their problem is solved, now it's up to me to update the internal guidelines and agent instructions so that the code is at least semi-decent.

None of these are going to "production", they all live on local company controlled laptops and only one of them might access an external API automatically later this spring.

But each of them takes hours of manual work and does it in minutes.

With the current tech, I agree this will still be pretty niche. I'm vibe-coding my own iOS apps, and it still needs a decent understanding of the tech and a willingness to put up with a lot of rough edges.

However, with a proper framework (e.g., a very opinionated design system, the ability to choose from some pre-designed structures/flows, etc.) I could very much see ad hoc creation of software becoming more widespread.