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

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

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.

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.

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.

MixedWorkflow & integrations

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

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.

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.