The rise of vibe coding: copycats and winners

The vibe coding market is shifting from “quick prototypes” toward fully featured, end-to-end app building—because early leaders are getting users to trust AI enough to finish real products. That change matters for anyone betting on this space: companies that position themselves as only partially capable (or only good for early drafts) risk being boxed out as users increasingly demand working workflows, not just demos.

Canva’s reported entry into the “lovable bolt world” highlights the tension. Canva is emphasizing a narrow use case—prototyping—framing the tool as a design-first experience. Rumors suggest Figma may be moving in a similar direction. The underlying claim from these late entrants is that the best value is limited to early-stage experimentation, not building complete applications. But the market signal coming from the head of the pack points elsewhere: users are flocking to products that promise more than sketches, and they’re pushing for completion.

Lovable and Replit are presented as examples of that early-leader momentum. Lovable’s roadmap is described as expanding beyond prototyping—adding capabilities like database integration and announcing “Lovable 2,” with features such as bringing in teams and security scanning. The direction implies a broader goal: making it feasible to build web apps inside the product, not merely mock them. Replit’s improvement is tied to a specific workflow upgrade—its building agent now handles planning more effectively. Instead of rushing, the agent reportedly takes time to think through the whole workflow and then sets expectations with a notification that the build may take around 10 minutes, encouraging users to wait.

That planning-and-timing detail is treated as a practical turning point. The transcript describes a firsthand moment where a child saw the “10 minutes” warning and adjusted expectations, suggesting the system is becoming better at managing the user experience around longer build cycles. It also contrasts today’s progress with earlier failure modes: previously, builds could produce non-working functionality and fall into error-fixing loops. While endless error loops still happen—messages from users complaining about them appear frequently—the overall competency curve is said to be rising quickly.

The market’s deeper dynamic is framed through an analogy: imagine a city that previously only had restaurants, then suddenly invents affordable kitchens. Not everyone will cook at home, and restaurants still matter—but the existence of kitchens creates an entirely new industry. In the same way, vibe coding is not replacing professional engineering or traditional development; it’s creating a new path for building “light web apps” for little money, quickly enough to attract sustained demand.

Against that backdrop, the transcript argues that companies emphasizing “half-featured” outcomes will struggle long term. Users aren’t just curious—they’re frustrated when builds don’t work, and that frustration is interpreted as evidence of real appetite for a home-kitchen experience: fully featured apps that can actually ship, not just start as prototypes.