Loading
How Lovable is similar to a slot machine
The psychological loops that drive habit and retention
How to time paywalls to be more effective
The Covid pandemic helped turn the company Zoom into a verb. It was the standout success of that time, accelerated by the tailwind of everyone being stuck at home.
There's a chance that Lovable reaches similar category-defining heights with their take on "vibe coding"—essentially helping non-developers build products by prompting AI models.
But when I recorded exactly what I did during a realistic 100-minute build, nearly 60% of my messages were simply pointing out bugs. That sounds like product hell.
So how have Lovable created an experience that is so enjoyable to use, it's actually addictive to fix bugs?
And more importantly, how have they used this to upsell their premium service so effectively, that they've grown to $100m ARR in just 8 months?
Welcome to the product design casino.
As you use vibe-coding apps like Lovable, one thing becomes clear: you'll spend the vast majority of your time doing nothing.
You're not incentivised to think about problems. Instead, you just ask the AI to "do it again, but better", and wait. Maybe this is what being a Roman emperor felt like.
Consider the following:
⏰
1. The wait time is unpredictable
It might be 5 seconds, or 3 minutes.
🤫
2. You can't send multiple prompts
So you need to wait for your original request to finish before adding another one.
🔥
3. Your request might break everything
So why bother planning your next move in great detail?
This is just an observation of my own behaviour, but because of those three factors, I quickly settled into my role as a lazy dictator and did nothing.
And although I was often sat for 5+ minutes, doing nothing, I wasn't thinking—there wasn't a strong enough incentive to do that.
Even worse, you might start multi-tasking, by watching Netflix or aimlessly scrolling Twitter. That kind of 🗯 Context Switching can be really damaging to both creativity and productivity, even if it feels efficient at the time.
Which begs the question: how creative is this process?
What worries me is that this periodic downtime, combined with delegating key product decisions to AI, may gravitate designs towards mediocrity.
So, what can these vibe coding apps do to incubate creativity while their AI is working? Surely there's a better and more productive way to use the right-hand side of the screen?
But maybe it's designed perfectly for what it is...
Yes, Lovable has many characteristics of a casino game—but most of those are just byproducts of the fact that they use AI.
So what's the takeaway here? Be a casino? (No).
Instead, think about my 100 minutes as a new Lovable user.
The more I used it, the more time I spent fixing bugs.
What Lovable have done so effectively with their free plan, is:
🏓
1. Encourage a specific type of usage
e.g., hiding credits and hiding "plan" mode from the homepage
💸
2. Use daily credits to encourage a habit
e.g., to repeat this "fun" behaviour
🔓
3. Know when to show the paywall
e.g., at peak "fun", before it gets too stressful
This may sound obvious, but it would have been so easy to just encourage users to plan more, to use their credits sparingly, and to start building something really ambitious.
But then the user would burn through their free credits without having fun, and they'd be less likely to upgrade.
In fact, if you designed Lovable with the assumption that everyone was building a scalable product, this is probably what you'd do.
Instead, they're controlling what happens in those first 5 minutes.
And that's the takeaway here: those first few minutes don't actually need to represent the stresses of the full experience—you want to showcase the best thing it can do.
Lovable aren't building their own AI models, they're building the experience layer around them.
As the underlying AI improves, some of the current issues will fade away—particularly around response times and error rates.
But right now, what is Lovable?
It's marketed as a tool that can build "real" products, suitable for real businesses.
Whilst I'm sure that's technically feasible, the actual experience right now has characteristics and psychology that lean more towards prototyping—and it works really well for that.
But consider the dilemma of what you actually want from a rapid prototyping tool, compared to one that builds scalable products:
⚡️ A great prototype
🚢 A scalable product
Prioritise speed and simplicity by delegating unnecessary decisions to AI
You want ownership over decisions and to know when they're being made
A magical backend that "just works", without caring about database structure
Planning a database structure is crucial to scaling, efficiency and future ideas
An uncluttered interface where you mainly use natural language
You'll want to use wireframes and flow charts to express yourself
Bugs are an annoyance, but not critical enough to need a QA process
Bugs can cause immediate and lasting damage to your brand
It's not that Lovable is designed poorly—it's actually excellent at what it does. I'd argue that it's best-in-class.
The point is that it's so addictive, enjoyable, and successful because it makes building ideas simple. Every aspect of the experience has been fine-tuned to make you think less.
But has great UX ever been created by thinking less?
We're all familiar with (if not bored to death by) the confetti blast celebration. This is how to design a motivational slingshot that actually works.
Learn which milestones to celebrate, and why
The common mistake when building celebrations
Techniques for upselling more effectively
Companies are building unique features, but then failing to show anyone how to actually use them.
How to structure onboarding for creative input (like AI)
Identifying when simply "pointing" isn't enough
How to make these features more memorable
Substack is optimised for writers, not readers. They use deceptive design and psychological exploits to drive growth.
How Substack uses deceptive design to boost sign-ups
How they exploit uncertainty to drive upgrades
The risks of careless A/B testing
The best retention strategy? Design a product that helps users feel like they’re making progress—right from the moment they set a goal.
How to create goals that stick
Framing benefits better to upsell more
Reducing churn by leaning into goals
There are more than 40,000 designers, developers and product teams who trust BFM to explain why things work. Join them.