Remix.run Logo
▲ stefanfisk 3 hours ago

I'm a developer who consults for a company who don't have their own devs but whom have started experimenting with building misc little apps in Lovable to solve business needs. I have spent a fair amount of time trying to get them into Claude Code instead so that they can prototype in our main codebase rather than vibe coding separate little apps for everything, but it really is an uphill battle and at this point I'm not even sure that it would be the right call.

Lovable is just waaay easier to use for a novice, because the workflow is stricter and a lot more directed. There's a chat and a preview side by side by default, and the interface is entirely modeled around directly building something simple for the web.

Claude can do everything Lovable can and much much more, but you have to know what to ask for and it's quite easy to go off the rails if you don't. Without any experience with branching, what would you even ask for? I've seen examples of Claude just starting to modify the main branch and without committing while working because a prompt was worded a bit wrong. But vague or confusing prompts are to be expected when the person prompting has never had to learn even the most basic common language around developer workflows.

▲theturtletalks 3 hours ago | parent [-]

Lovable is actually really good at frontend so letting your PMs and designers use it is no issue. Generally you want a skill ready for them to give Lovable so Lovable uses an external app that a real developer is building. That way you can make sure the backend code is outside Lovable.

It’s actually how a lot of people are building external storefronts for our SaaS.