The Gap Between Vibe Coded And Production Ready #programming

26 Feb 2026 · 0 min

Watch on YouTube

0:21

In this brief conversation, the speakers discuss a growing trend where clients hand over quickly built, "vibe-coded" applications that lack formal specifications. While such prototypes can be easily rebuilt, capturing the undocumented nuances embedded by the original developers proves challenging. They illustrate this problem with a recent project: a legacy React Native CLI app was migrated to Expo using Claude Code, an AI code generation tool. Although the "one-shot" prompting approach is often overused, in this case it was effective enough to facilitate the migration, highlighting both the potential and limits of AI assistance in moving prototype code to production‑ready status.

We're seeing more and more clients kind of bring a Vibe-coded app to us for us to take to the next level. And it's interesting because on the one hand, you can almost throw it away because it's so easy to recreate. But on the other hand, trying to understand all of the nuance that they prompted into it is trickier because they don't have good specs or requirements.
It's just, hey, I built this thing. The app that you recently helped build a native version of was initially web, or did they just have a React Native and you helped migrate to Expo?
Yeah, it was React Native from the CLI, sort of the old style React Native build. And we converted it to Expo through the help of Claude Code. And I know like one-shot gets way overused, but it wasn't far off.
It's sort of like that. Like it was pretty close, but I think part of that is because like his knowledge of both web and native platforms. Helps make the AI one-shot promise kind of work, right?