Hi everyone,
This has been on my mind for a few weeks, so I wanted to share it and hear what others think.
In my experience, AI in WeWeb hasn’t been helpful—it’s been unreliable. And to be fair, I don’t think this is just a WeWeb issue. I think “vibe coding” in general tends to create fragile, unpredictable results. I’ve seen people try to build apps this way and end up with something that looks good on the surface but isn’t stable enough to support real users.
I’ve personally tried to use WeWeb AI for small tasks. For example, I recently asked it to add a minimum character requirement to a password input. Instead of helping, it broke the logic—the button stopped working entirely, and I had to delete everything and rebuild it from scratch. I imagine others have run into similar issues.
My concern is focus. WeWeb is already a powerful no-code platform, and I think its biggest strength is giving users control and clarity over what they’re building. I’d much rather see continued investment in making the core no-code experience more robust, predictable, and refined—rather than putting energy into AI features that, at least today, feel unstable.
For context, I’m not a traditional developer. I’ve been learning by building—using WeWeb and Xano—and avoiding AI has actually forced me to understand how things work. That’s been valuable. It’s slower, but much more solid.
Even in cases where AI does produce something usable, there’s a deeper issue: if you don’t understand what’s happening under the hood, it’s very hard to sell, maintain, or troubleshoot what you’ve built. And problems will come up. If you don’t truly own the logic, you can’t confidently support it.
To be clear—I really like WeWeb. That’s exactly why I’m sharing this. I just think the platform’s strength is in empowering builders, not abstracting things away too aggressively with AI (at least not yet).
Curious to hear if others have had similar experiences or different ones.