Personally, this shift towards AI vibe-coding was a bit discouraging for me at first. It felt like people were quickly abandoning Bubble’s well-defined infrastructure and years of ecosystem development for the latest AI trend.
I was curious why so many people preferred these new platforms, so I went ahead and tried most of them myself — v0, Replit, Lovable, and others. One thing I noticed immediately was that the AI-generated designs were nowhere close to what I was building in Bubble. Beyond that, the lack of visibility into where components lived, how things were structured, and what was happening under the hood was genuinely concerning.
During all this chaos — when Bubble jobs seemed to slow down and everyone was jumping on the AI hype train — I decided to learn the basics of coding. Not because I wanted to leave Bubble, but because I wanted to better understand the platforms I build on and not be completely dependent on any single tool.
I started with Flutter, which was very beginner-friendly, then Python, and later moved into DevOps fundamentals. Learning things like what a domain actually is, how data moves between servers and clients, how data centers, CDNs, CI/CD pipelines, GitHub pull requests, and deployment workflows operate gave me a much clearer picture of how the web works.
Ironically, that journey made me appreciate Bubble even more.
Bubble has been saving us from having to think about so much infrastructure complexity. A lot of the things developers spend time configuring manually are already handled for us. Meanwhile, someone fully relying on AI-generated code still needs to understand enough to instruct the AI correctly or troubleshoot when things inevitably break.
And let’s be honest — we’re starting to recognize AI-generated products. The familiar Tailwind styling, the purple gradients, the similar layouts and structures. Right now, AI is excellent for landing pages, waitlists, prototypes, and getting ideas off the ground quickly. At the same time, the advancements are real, and ignoring them would be a mistake.
What I always enjoyed most about Bubble was focusing on proper database design, reusable elements, performance optimization, and privacy rules. Once you understand those fundamentals, building becomes incredibly enjoyable.
That said, as apps scale, there is a valid concern around additional functionality. Plugin developers have contributed enormously to the ecosystem, but every new capability often comes with extra costs — plugins, storage, workload units, and so on. Sometimes you’re forced to either custom-build a solution or purchase one, which requires additional skills and investment.
My overall conclusion is that Bubble builders should invest time in learning coding fundamentals and web infrastructure concepts. Not necessarily to become full-time developers, but to provide more value, especially if you’re operating as a freelancer or agency. Understanding how the web works makes you a much stronger Bubble developer.
The reality is that there are fewer Bubble clients today than there were a few years ago, and we need to adapt to that reality rather than ignore it.
My current view is this:
If AI and no-code tools are becoming our new workforce, let’s be creative with them. Let’s use them to build products, solve problems, and create value — not just rely on them as a source of employment opportunities.
The builders who will thrive are the ones who combine AI, no-code, and technical understanding into something greater than any one tool alone.