I have been exploring the idea of vibe coding, meaning describing an application in natural language and receiving a working project in return. In practice, many existing tools generate impressive demos but struggle once you start iterating, especially when the project spans multiple files. They also tend to assume a desktop IDE as the primary environment.
I built a web-based vibe coding platform powered by Claude Opus 4.6 as the core reasoning model. The system runs entirely in the browser, and you can generate and refine applications directly from your phone. The intention was to remove the dependency on a local development setup and make prompt-to-app creation accessible from any device.
Instead of returning isolated snippets, the platform generates structured multi-file projects with a defined separation between frontend and backend. When you request modifications, it attempts to reason over the existing codebase and apply changes coherently, rather than regenerating everything from scratch. The goal is to make iteration feel closer to refactoring an evolving project than repeatedly producing disposable output.
It is still early, and I am particularly interested in how it performs under real-world use. If you have pushed other vibe coding tools to their limits, I would value your perspective. Where do they typically break for you? Does mobile-first generation make practical sense, or is desktop still essential for serious development?