Past 7 days · Coding & app building

Lovable

Turn ideas into apps and interactive prototypes

Experience score37.6/10038 comments
Source All

What people think

Across 38 comments in the past 7 days, the overall experience leans negative. Criticism concentrates on price & limits (12 of 24 negative excerpts). Praise concentrates on workflow & integrations (5 of 12 positive excerpts). One user combined Lovable, Codex, ChatGPT and Codemagic and has published two apps from Lovable so far. One user found Lovable's inefficient Supabase auth queries made their few-hundred-row database perform like querying hundreds of thousands of rows.

Daily experience trend

3040506040.609-2509-2709-2809-3010-01By comment date · UTC · at least 5 comments per day

User feedback

50 review excerpts

PositiveWorkflow & integrations

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

PositiveWorkflow & integrations

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.

MixedEase of use

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.

NegativeResults & quality

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.

NegativePrice & limits

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.

Comment context
From the same comment ↗

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.

NegativeReliability

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.

Comment context
From the same comment ↗

Also Lovable loves writing very inefficient supabase queries to do with Auth stuff.

NegativePrice & limits

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).

NegativePrice & limits

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

PositivePrice & limits

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.

PositiveSecurity & permissions

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

PositiveEase of use

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.

Comment context
Comment being replied to ↗

Vercel has a free tier and does everything lovable does as a host, plus much more. There is simply no reason to pay for a lovable if all you want is a host, especially if you're already syncing to GitHub and developing outside of lovable. You're paying for something you could get for free.

PositivePrice & limits

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

NegativeWorkflow & integrationsReliability

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.

NegativePrice & limits

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

PositiveReliability

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?

NegativeSecurity & permissions

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.

NegativePrice & limits

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

Comment context
Original post ↗

I also setup stripe for payments so I plan to have an upfront cost of $799 with a $99 monthly fee for "running" the website along with free iterations.

PositiveEase of use

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

NegativeReliability

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.

PositiveWorkflow & integrations

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

Comment context
Comment being replied to ↗

Claude does not handle hosting, domains, database, auth, email delivery, cron jobs etc with one prompt. Or am I missing something?

PositiveWorkflow & integrations

This is something lovable is better at.

Comment context
From the same comment ↗

Codex gets really weighted down quickly though in large projects. Have to write continuous "hand off" documents and start a new chat.

NegativePrice & limits

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

PositivePrice & limits

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.

PositiveEase of use

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

NegativeWorkflow & integrations

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.

NegativeEditing & control

zero control

Comment context
From the same comment ↗

As a matter of fact, I have stopped considering Lovable or any Lovable like tools for development because they are effectively re-selling tokens at a very high markup. Claude code/Codex can do just anything so why pay for Lovable to get something done through the same models at a very high prices and zero control?

NegativePrice & limits

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

Comment context
From the same comment ↗

As a matter of fact, I have stopped considering Lovable or any Lovable like tools for development because they are effectively re-selling tokens at a very high markup.

MixedEase of use

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

NegativeReliability

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.

NegativeReliability

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.

NegativePrice & limits

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

NegativePrice & limits

lovable is just giving you access to cheaper models for a higher price and providing alot less value to you as a consumer

NegativeResults & quality

What shit, stop using lovable, damn it Claude code is now equal and better via web via desktop or via cli and with superior abilities

Machine translated
Show original

Que merda parem de usar lovable , porra o Claude code agora está igual e melhor via web via desktop ou via cli e com habilidades superiores

NegativeReliability

Every time a user goes through the site, it's this problem or that problem. Almost like for every bug or problem that is fixed, another one is created.

NegativeResults & quality

it's good for small scale projects, but you shouldn't use it for large scale projects.

NegativePrice & limits

Yup, it now seems to have gone X 3 credits. I'm bowing out over next few months, it's been fun.

Comment context
Original post ↗

Previously, if you asked Lovable to delete a normal text, it'd spend maximum 0.6 credits to do that. Now, it costs minimum 2.10 credits to delete a normal text.

MixedWorkflow & integrations

no hate for lovable, its just that i dont like to depend on single application for complete development

NegativeEase of use

Never understood the need for something like lovable when I can just use Claude code or antigravity to build what I need and host it on vercel or something similar.

NegativeEase of use

I first started Travi, I did it on Lovable, quickly hit a wall in terms of functionality

NegativeWorkflow & integrations

both are an hour to fix, and both are invisible from inside the lovable editor.

Comment context
From the same comment ↗

the one nobody lists but should: no privacy policy.

From the same comment ↗

the scary technical one is supabase tables readable with the public anon key, found 6 of those across the same batch.

NegativeSecurity & permissions

the scary technical one is supabase tables readable with the public anon key, found 6 of those across the same batch. both are an hour to fix, and both are invisible from inside the lovable editor.

MixedEditing & control

The important thing is your hosting platform for the website ahead of time so it's not hosted on lovable if you ever want to move off of it

MixedPrice & limits

you can stop paying for lovable and use the 5 free credits for small daily changes

PositiveWorkflow & integrations

I think using these intensively has really helped with my confidence level re the basic stack I'm using.

Comment context
From the same comment ↗

For now, I'm relying on my test users. I use 2 of my apps really intensively - one records all my matches over a season, the other is a captains app so I record the performance of my team.

MixedPrice & limits

I know there is a lovable feature that can monitor your apps but there is a cost and I need to get some more paying customers first.

MixedResults & quality

Now I think Lovable is only decent for people who really know NOTHING about IT, I think there's still a market, just less.

NegativeReliabilityPrice & limits

sometimes it uses all daily tokens just to even read file … before even making any changes

NegativeSecurity & permissions

Getting another customer's response is a very very serious security issue from my point of view