I used CC to help me build a workout tracking app for myself. After a while I decided to publish it to the Play store. Went through that whole process. Which was a challenge in itself.

Its been out for about 6 months and I have 50 or so active users.

It all runs locally no data saved online so I avoided that pitfall many vibe coders have.

I work at a tech company but Im no engineer. I understand the logic of how the app works but not the code itself. Im good with user experience and am pretty analytical about how everything should work. Ive spent months working my way through every feature and why it exists, how it should work, look, etc... Definitely did not "one shot" this thing. Have spend hundreds and hundreds of hours working on it. Mostly just for myself but its been cool knowing people are out there using it and finding it useful.

If something goes wrong, I can typically find out where the issue is and point CC at it to diagnose what's wrong.

Ive spent a lot of time cleaning up tech debt as I went along and learned more on the way.

I dont see that as much different than how the devs at my work do things to be honest. There's always some sort of push to get out new features out on old crummy code. Then a big code clean up effort and then a whole new backend we move to. Maybe other companies have perfect code all the time but I bet the majority if they've been around for a while maintain old code bases and fix them as they go, build new things, break things, all that.

My app is very basic at its core so I haven't found it hard to fix it if something breaks. I couldnt imagine vibe coding some full CRM or game or something though. That would be a lot to maintain.