Lovable

Sometimes, even after explicitly telling it not to modify anything in a specific file, it still ends up making changes there.

That said, I’m glad I somehow managed to get the overall UI exactly the way I wanted via lovable.

Accurate updates, good additional suggestions and the chat saves me a ton of tokens.

I’ve had the opposite experience. For me it has massively improved. Accurate updates, good additional suggestions and the chat saves me a ton of tokens.

Once it reaches a certain size, Lovabel starts to lose track and spends tonnes of credits thinking about he next step, revisiting the code. The more code the more time, more tokens.

Once it reaches a certain size, Lovabel starts to lose track and spends tonnes of credits thinking about he next step, revisiting the code. The more code the more time, more tokens. Plus, it makes tonnes of mistakes, tonnes.

Lovable went downhill so bad.

Lovable was great in the beginning.

Lovable was great in the beginning. But now there is No use case.

The quality is terrible compared to claude code. And this is because they switched to GPT Sol 6 which is terrible. They started using fable 5.1 and the quality was great now its been worse and also a bunch of hiccups are happening on the platform where I have to re-iterate things.

The quality is terrible compared to claude code.

I have been quite impressed by it's ability to write clean code for React and to make sure of Reacts components structure even though I find myself specifically asking for that.

All of my challenges have been through my own prompt writing.

What I have done with the $480 plan saves thousands.

This isn't true at all the prompting has degraded from literally 2 weeks ago. They made a change recently that made everything worse.

You're not wrong about Claude Code but I would even still recommend to use lovable to spin up the site then take it into VS Code and use tools like Claude Code and Cursor to maintain.

Nowadays honestly if you spend the evening learning how to setup and use Claude code or codex you will go MUCH further compute credits wise and the harness is very strong. There is no more use case why you would want lovable over the direct interaction with a frontier model.

overconsumption of credits, lying about completed work, the whole nine yards

it's gone down the tank in the last month. overconsumption of credits, lying about completed work, the whole nine yards

It's a really great cost effective way to build.

I've used Lovable for months, at the start of my SaaS project. Burned through my 300 credit bonus for being a LinkedIn premium subscriber. Subscribe for two months for 200 more credits and them switch to Claude. I do so much more with Claude Code that I downgraded back my Lovable plan to Free.

Lovable Chat helps alot.

Lovable for quick mvp.

My first project to go live will be by Claude. More control there (I feel..)

I use Lovable for frontend and codex for backend. So I don’t burn Lovable credits on anything except UI

Lovable provides no benefit, absolutely none.

if you're actually using it, £11 is cheap enough to just keep it grandfathered in. once you cancel you'll probably never get that price back.

I used a combination of Lovsble, Codex, ChstGPT and codemagic and have published two apps from Lovable so far.

keep shopify as the backend and just hit their storefront api from lovable. trying to rebuild carts, checkout, and inventory tracking yourself is a massive headache when shopify's headless setup handles all of it out of the box.

So I always say Lovable for development/testing only. Code on Github. Selfhost on a vps for launch if you know how or Vercel/Supabase Cloud if you dont.

Therein lies the problem as Lovable has written an auth loop into my code before too. Also Lovable loves writing very inefficient supabase queries to do with Auth stuff. However, you won't know that unless you use Supabase cloud/selfhost - the Supabase advisor says how badly they perform but Lovable cloud doesn't have that feature.

Most people don't know about the usage/hosting charges as accounts have a certain amount free. I had a site with a few hundred rows in a db but it was performing like I was querying a couple of hundred thousand all because of those bad queries. Also the three days of test only traffic was eating 3 credits a day so anything after launch was going to be horrific.

I had a site with a few hundred rows in a db but it was performing like I was querying a couple of hundred thousand all because of those bad queries.

I'm just saying it so people don't consider Lovable as more than a development platform. Too many posts on here where they reach the find out phase (costs/migration pain/Lovable ToS/whatever).

Lovable hosting is not free and if you scale in any way it will wreck you in costs.

Also, Vercel free tier prohibits commercial use, which rarely is an issue as most projects have to pay the $20 subscription due to practical limits.

But you can't say Vercel has the same offering as Lovable compared to cyber security and ease of us.

But you can't say Vercel has the same offering as Lovable compared to cyber security and ease of us. Basically everything that a non technical person needs.

They should pay $500 on Lovable as its a small cost to what the opportunity cost would be developing a "scalable" solution 😆 Another exaggerated example sure

My advice is for non-technical people using lovable with the plan to sell apps or release paid services to immediately start gaining the knowledge of what lovable is doing and what they should do with the code to host it properly.

All the data I keep it in BigQuery and avoid using Lovable Cloud, because credits burn now after the changed it.

I don’t get why everyone hates on Lovable for hosting tbh. Granted, the apps I’ve built for businesses tend to max out at about 60 concurrent users each, so hardly load, but I’ve never really had an issue?

If you use Chrome extensions that abuse the Lovable credit system to bypass what you usually pay for, this is breaking the terms of service of Lovable. You risk your workspace being removed indefinitely, along with all the projects that were remixed in the workspace, and that originated in the workspace. Further, Chrome extensions like these usually track every message you send and try to fish for API keys, credentials, and personal information. If you utilize extensions, your account and workspaces will be compromised.

And no one with any sense would pay anyone $799 for a vibe-coded AI crap website.

Lovable is really convenient as a cloud service, especially when you have a lot of small or medium-sized projects

DON'T host it on lovable!!! This is where you need to start learning more about web development. Especially around properly hosting websites. Lovable will get you in some serious jams if there's high traffic or resources used. You can't afford for a paid site to go down. Best thing to do is host it on their current platform or find a proper web host or vps or cloud for them to host on and don't take on hosting responsibility.

It can deploy your code to Cloudflare (free) as well as to Supabase (free), while committing all of the code to Github.

This is something lovable is better at.

although there are better hosting platforms to use (Vercel for example) than Lovable since they are optimizing toward different customers

I spend 1500+ credits to explore it (about 400 euro for one month), so I satisfied, but I wanted to find cheaper way to develop instead.

the frontend export is usually easy since it's just standard react

but dealing with the supabase side is where it gets annoying. untangling generated rls policies and getting all the edge functions running cleanly in your own environment usually takes the most manual cleanup.

zero control

they are effectively re-selling tokens at a very high markup

Lovable like tools can be a good start for someone who has zero technical knowledge

But its not 100% working. If you do changes with chatgpt and then publish but after that if you changes with lovable it will break the design or code.

It's also really easy to start with an architecture that makes future changes really hard. When you look at the code there's duplicated logic everywhere so the longer you build the worse it gets.

It’s all a hidden credit sink as the transparency from them is gross