I still choose no-code over vibe-code

Last Friday, I challenged myself to build two side tools for Odyseek using both Lovable and Bubble.

Here’s how it went:

Lovable:
I’ll be honest, I use Lovable when I’m feeling too lazy to design from scratch or just need some inspiration for UI/UX. Usually, I throw a prompt at it, explain what I want, and it quickly gives me a decent starting point for layouts or features.

This time, I tried building an entire side tool for Odyseek. Seemed simple enough. My first 5-10 prompts went smoothly, and I had a pretty solid app structure. But then… I hit a bug.
One bug.
It took 46 more prompts (yes, forty-six!) to try to fix that single issue, and even then, it still wasn’t fully fixed.

I swapped out libraries, dug through web forums, refactored code, went back and forth in the chat, until eventually I just gave up and shipped a half-baked version because I ran out of patience (and time). Oh, and then Lovable hit me with a “Please upgrade your plan!” message. Really? I’m supposed to pay more for a tool that can’t even help me finish what I started? That’s when I was officially over it.

Bubble:
Next, I turned to Bubble, my old friend. Here, I was in full control. I knew exactly what I wanted, how to build it, and in five hours flat I had a bug-free, ready-to-ship tool. Sure, it sounds easy because I have 7 years of Bubble experience, but the difference was night and day.

Maybe I need 7 years of vibe-coding to do the same using Lovable 👀

Links from the tools 👇
Lovable: https://vision.odyseek.com
Bubble: https://app.odyseek.com/bingo