Andy Halliday

Don't worry, they're not going to fall.

Oh, yeah, yeah.

Oh, no, no, yeah.

So being a lovable user at the moment, I can say that there are some niceties to working with lovable that you don't get with cloud code.

And principally you have, because I'm using cloud code in the cloud desktop environment,

And in terminal, I don't have as someone who's doing that inside cursor, I don't have an integrated view of what the emerging work space is.

If you're building an application, I don't get a view of that.

Whereas in lovable,

you have a preview pane that's there right by your side.

So as you're working in conversation with lovable and giving it tasks to proceed with based on your extensive early preparation, I insist on a good PRD, then, you know, you're seeing it and you can play with it right there as it's delivered.

And then ultimately, it's all set up with their lovable cloud system to click one button and deploy it to the web.

Now, there's a bunch of steps that you have to go through to make that work that simply in cloud code.

And eventually Claude Code will catch up with those niceties.

The other thing I'll point out is that on the downside, Loveable still exhibits an oversimplification of its execution with sort of an inclination towards doing something that's just demo-like rather than the full production happen.

And so what I've found in my most recent sessions with both Claude

watching and advising about what Lovable is doing is it was really disappointing that Claude would say, oh, I've completed all these features.

But when Claude looks at the code underneath it, it's like it didn't really do it.

It just it puts something up that, you know, would make it kind of superficially present in your UI, but it doesn't have connection to all these other things.

And then we have to instruct Lovable to do that.

I wish it weren't that