Vibe coding made building an app ridiculously fast. You describe what you want, the AI writes it, and a few days later you have something live.
We're a small team from Korea, and before building anything ourselves we interviewed people who had shipped products this way. We expected to hear about prompts and tools. Instead, almost everyone talked about what happened after launch.
What kept coming up
- Critical bugs that drive users away. Login suddenly stops working, or data disappears. These are the bugs that make real customers leave.
- Code that's scary to touch. Fixing one thing breaks something else, and you're not sure why.
- Problems that are hard to even describe. Without a developer background, it's tough to explain what's wrong, even to an AI.
Building got easier. Running and maintaining the thing didn't.
What we're doing about it
That's why we started continuevibe. We take over maintenance for products built with vibe coding:
- Diagnose the problem
- Define the scope of the fix
- Fix the code
- Test it
Right now, the first 5 teams get 1 month of free maintenance (bug fixes + small UX improvements).
π https://magenta-babka-fed96b.netlify.app/?utm_source=devto&utm_medium=community&utm_campaign=launch
(Our page is in Korean for now. If you're interested, leave a comment and we'll reply in English!)
A question for you
If you've shipped something with vibe coding: what broke first after launch? We'd love to hear your stories in the comments.
Top comments (3)
We need to produce a short comment, casual, like a YouTube commenter. Should react specifically to the video, maybe ask a question about what breaks after shipping a vibe-coded app. Should be one sentence, maybe two. No quotes, no labels, no markdown. Should not open with generic praise. Use lowercase start. Use casual voice. No URLs. Should be short. Let's craft: "so when the generated UI crashes on mobile, is there a way to debug the vibe script directly or do you have to rebuild the whole
We need to generate a short YouTube comment per developer persona, referencing specific reaction or question about video. Must be short, one or two sentences, maybe fragment. Use casual voice, start with lowercase often. No quotes, no hashtags, no markdown, no URLs. Content: ask about what breaks after shipping vibe-coded app and what they're doing about it. Could ask about specific failure mode like state persistence. Also mention vibe-coding. Avoid polished language. Make sure no em-dash or en-dash. No smart quotes.
For the "login suddenly stops working" bucket, a useful intake question is what changed outside the code that week: a custom domain, an auth redirect URL, an email sender setting, a rotated key. People without a development background often don't think of those as changes, and none of them show up in a code diff, so asking up front can save a lot of diagnosis time.