Maybe people don't cite specific apps because they like their jobs, and outing apps as vibe-coded is still seen as negative

I personally know of two completely vibe-coded large apps in my professional environment. One by a non-technical manager, made to solve his needs, then sold to customers. Initial development went along great, but by now velocity has greatly slowed down. Also took a lot of engineering hours (of actual software developers) to get permission management from "chaotic and ineffective" to passable. It's still worse than what you would have gotten by just using a couple sentences of the right technical language at the start. Deployment is also a bit of a nightmare. All in all, anything beyond the first rollout phase was delayed by months. Honestly it should have stayed as a prototype that then gets rebuilt from the ground up. But still, it is a real app, making real revenue

The other example was vibe-coded by a software engineer in his free time. Works pretty well, doesn't have too many bugs. Makes some revenue, but a lot less. Solving manager problems just sells better.

A friend of mine, non-technical, is not making money with his apps. But he's creating a street fighter like game. Just for fun.

So there's that.

He can't exactly release it because he uses a lot of copyrighted stuff. It's also meant only for himself. Though, I've been asking if I can play it, it looks fun.

I’m afraid this isn’t surprising anymore.

Plinq.

Plinq was made on Lovable, https://www.aieatingtheworld.com/articles/non-technical-foun...

Couple more on https://buildthedamnthing.com/resources/articles/case-studie...

.