One larger prompt costed me 10.20 credits, $2.5 for it to tell me it cannot finish the prompt and need me to tell it to continue. Wish they had a toggle for different models opus 4.7 is insanely expensive and thats probably what is passed along to the customers and their massive system prompt and .md is eating context like crazy.

A year ago the same change would be 2-3 credits for not much worse quality

Just launched a SaaS built entirely on Lovable. No ads. No Product Hunt. No email list.

Here’s what actually worked for distribution:

1. Post a genuine question, not a pitch
   “How are you solving [problem]?” not “check out my tool.” The question invited experts to share. The product came up naturally later.

2. Reply to every comment with value
   Every person who commented got a thoughtful reply. Kept the thread active for 48 hours and signaled to Reddit’s algorithm that the post had real engagement.

3. Let competitors mention themselves
   Six different competing tools showed up in my thread organically. That validated the category better than anything I could have said.

4. The product did the closing
   When someone asked “what tools exist for this?” that’s when I mentioned my product. Not before.

What Lovable made possible: I could focus entirely on distribution because the product was already built. No debugging, no deployment issues, no dev bottleneck.

The build is the easy part now. Distribution is the skill.

What’s your biggest distribution challenge after shipping on Lovable?

I’ve seen posts recently about it eating up credits, but it’s also making simple mistakes for me that have been really frustrating. For example, I spent a few credits perfecting how I wanted my pricing cards to look and I was finally happy with it. Moved on to some other feature then when I scrolled the preview page the pricing cards not only reverted all my changes but it looked worse than before!

If you’ve been on Twitter or tracking the vibe-coding space lately, you’ve probably seen people claiming that the combination of Anthropic’s Claude Design and Claude Code has completely made platforms like Lovable obsolete. The narrative is simple: design the frontend visually in Claude Design, then use Claude Code in your terminal to hook up the backend. Done.

But if you actually test this workflow on a real, production-ready app, you quickly realize why Lovable is still a necessary tool for most people.

Here is the honest breakdown of why the Claude tag-team doesn't replace a true app builder:

1. The "DevOps and Infrastructure" Tax

• Claude Code + Design: Claude Design gives you a gorgeous, stateless frontend prototype (HTML/CSS). Claude Code helps you write programmatic terminal logic. But you are still the systems administrator. You have to figure out where to host the database, how to provision the server, manage environment variables, and configure a live deployment pipeline.
• Lovable: It assumes you don't want to handle infrastructure. The second you prompt an app, Lovable provisions a live URL, hooks up a structured Supabase database, configures secure user authentication (including 2FA), and builds out real-time backend state management. It manages the "plumbing" automatically.

2. The Hardcore Developer vs. Everyday Creator Divide

• Claude Code + Design: This combo is an absolute weapon for the top 1% of developers. But Claude Code operates right inside your local IDE, terminal, and git repositories. If you don't know how to navigate a terminal, debug a local environment crash, or fix a broken node modules dependency, the terminal loop will get you stuck immediately.
• Lovable: It’s built from a visual, canvas-first perspective. It translates human descriptions directly into production-ready software architecture without forcing you to look at a command line. It's built for the other 99% of people who want to ship an MVP on a Sunday afternoon without installing a developer toolkit.

3. Model Hallucinations and the "Guardrail" Problem

• Claude Code + Design: When you use raw AI agents, you are dealing with a "black box." One day Claude writes perfect code; the next day a new prompt causes it to hallucinate, conflict with an existing file, or break your layout rules. You need to be technical enough to catch its mistakes.
• Lovable: Because it acts as a structured software engine, it wraps the AI inside rigid architectural guardrails. It forces the underlying model to output predictable, clean, and scalable backend patterns so your application doesn't slowly devolve into a house of cards as it grows.

The Verdict?

They aren't actually competing tools—they are different workflows entirely.

• If you are a developer who wants absolute, microscopic control over your local repo and code architecture: Use Claude Code.
• If you just want a functional, database-backed web app live on the internet in 3 hours without touching a terminal: Lovable is still the king.

Last night I was sleepy and I wrongly pressed project to delete . I was cleaning folders and later I realized I did shxt , the project that I have to make live soon is deleted instead

How to recover from.lovable

If you’ve been building any kind of data-heavy app or SaaS prototype on Lovable, you already know the platform is incredible at spinning up the core engine. It handles your frontend and your Supabase database beautifully. But the second you try to make your app interact with the outside world—like sending a WhatsApp alert, updating a Google Sheet, or triggering a Quickbooks invoice—you hit a wall.

Right now, to connect Lovable to external services, you either have to write custom webhooks or rely on standard integrations. It’s a massive bottleneck.

Here is why a native Make.com connector would completely change the game for everyone in this sub:

1. It bridges the gap between Vibe Coding and No-Code

Lovable is perfect for building the core application state (the database and user authentication). Make.com is the absolute king of workflow automation. Instead of trying to force Lovable's AI to write complex API integration code for 50 different third-party apps—and risking prompt looping or hallucination—you could just have Lovable pass a webhook payload straight to a Make scenario. It lets the AI focus on building the app, while Make handles the messy plumbing.

2. It bypasses the "Zapier Tax"

A lot of AI tools default to Zapier because it has name recognition. But for anyone running a lean startup or building a side project, Zapier’s pricing is brutal. Make.com gives you infinitely more advanced routing, loops, and data formatting on their free and budget tiers than Zapier ever will. Giving Lovable users a native, one-click way to map data directly into Make modules would save everyone a ton of money on monthly operational costs.

3. Instant access to thousands of APIs

If the team at Lovable builds a native Make connector, they don’t have to waste time building individual integrations for Salesforce, Slack, Hubspot, or Notion. One single, robust Make connector instantly unlocks thousands of apps for Lovable builders. You could suddenly build a CRM in Lovable that seamlessly syncs with a client's existing business toolkit with zero manual code deployment.

The Verdict

Lovable is unmatched for creating the "brain" and the "face" of an app. But a native Make.com connector would give it "hands." It would turn simple MVPs into incredibly powerful, production-ready enterprise tools overnight.

Have any of you managed to set up a clean, custom webhook loop between Lovable and Make manually, or are you waiting for a cleaner, native integration to drop? Let's discuss below—hopefully the devs are lurking!

Hello,

Just my perspective it seems like the community is getting a lot of posts around "this got too expensive" or "it's using too many credits for the prompt" recently. It feels like every other post is "This is too expensive!!" and they never ever share details.

My experience is very different with Lovable and I wanted to share actual concrete data.

Generally speaking these posts loosely describe "I asked for X and it cost Y and that's bad" scenario without sharing real information. I have not seen a single post actually share the prompts and outcome in terms of costs.

Below are 4 real prompts I did this morning as a test of costs.

Context: I have a existing Dashboard app (~140 pages) and I am adding a new Product so just doing some basic clean up on the new pages. Below are 4 real prompts + costs done today.

Scenario 1:

I asked it to disable a button and it cost me 1 credit.

https://preview.redd.it/4k38p27brb2h1.png?width=522&format=png&auto=webp&s=489fcc6f822eed5cbec2501efb27cd03e43e9cf3

Scenario 2:

On one of the pages there was a existing json parsing bug, I asked it to fix it and it cost me 0 credits

https://preview.redd.it/b6dc04firb2h1.png?width=433&format=png&auto=webp&s=f398ce1441f9f5566f7fe7f25eb88349e070bf8e

Scenario 3:

Update 2 big dashboard pages and add test to all the sections explaining the data. This is a big grey prompt since I am expecting it too add detailed text. it cost me 6 credits

https://preview.redd.it/oj8pmbmprb2h1.png?width=556&format=png&auto=webp&s=1131dbf1a61e505a6e872dc84b3c0aa19821b540

Scenario 4:

Add a Debug Json button so I can see the raw json, on 6 pages gated by a admin only flag. This cost 6 credits.

https://preview.redd.it/bofk449fsb2h1.png?width=563&format=png&auto=webp&s=ea888b49fa22f1aaeab2e4ea497791b60e9d652a

Outcome: All of the changes were completed exactly like I asked with zero fixes needed by me. The text on the Dashboard pages looks good and is technically correct. Small Example with some of the text it added:

https://preview.redd.it/3v168zb2ub2h1.png?width=1276&format=png&auto=webp&s=2ebe090bd7f921d9bd3e3f68b6f422ff75c42e28

My Perspective: These Credit costs seem very reasonable to me personally. It's made edits on multiple pages, it's calling and parsing the JSON, and it's checking Auth for the bug component. It generated contextual user level text for the analytic views with no input from me.

I am curious what others think? Everything seems fine to me?

What prompts are you doing that go nuts? I am not seeing that on my side. Friendly questions.

edit: fixed some formatting

Hey folks,

I have seen my lovable cloud usage grow in the last couple of weeks. Is there a way for me to spend less on lovable cloud and possibly move storage out of lovable cloud? Please advise.

I am in the middle of building out something that I think is going to be awesome. I’m not ready to solicit feedback just yet from this (or other communities on reddit but I currently have a beta in the hands of a few friends).

My question to you folks is once I’m ready, what is your best suggestion on how to get a usable product from here to an app to be launched on the App Store/google play store?

I’m getting close but need some help figuring this last part out.

In the last few days, I noticed that each prompt seems to be consuming significantly more credits. Most of the edits cost about 5 - 6 credits now compared to maybe 3 - 4 credits in the past. Do other people notice this too?

Ok complete newbie here, I have a background in video production and editing etc, anyways I had an idea and during lunch break tried a few development apps out, just to see if it could come close, and boy did it, in particular lovable did exactly what I had imagined in just one prompt.

Now however I need to figure out how to continue. Its a mobile app concept, but from what I hear lovable cant really do that, its just generating a ui design. So whats my next move? Do I make as many corrections as possible then proceed by exporting it and importing it into another ai like bolt?

Its a social media app, so there's algorithms, server hosting logistics, etc to think about, and I figure its probably the most demanding task to give ai. Will definitely hire devs if It actually starts looking feasable, for the time being I want to get to a working preview and a better understanding as to how/if I could get it running by myself. Like ideally running on something like xcode for ios.

Has anyone had experience making an app using code from lovable? What were the general steps you had to follow anw what services did you go with?

I’ve run out of credits and need more to continue, anyone willing to buy me credits?

Do i stay on lovable so fixing bugs and future updates are easier with prompts and hosting is quite cheap, or do i move to a diff hosting website?

I run an agency which builds software with lovable. The goal is to become a certified partner - and today is the first time I’ve had to seriously consider alternatives and maybe rethink the strategy.

Technical prompts are burning 8-12 credits at a time and I still have to go back and prompt again to finally get the initial request, so you’re talking 20-30 credits per run.

my usage has tripled this month - by month end I’ll have used over 5000 credits

I have a Claude pro max account and the error rate is so much lower and I’ve never hit the limit.

The credit-draining has reached a new level of creativity. I honestly cannot stay with Lovable anymore.

Before, at least when you asked for a specific change, it would attempt the change, get it wrong, and drag you into a loop that was annoying but eventually fixable.

Now? I ask for something simple, like making one product image match the size of the rest of the product images on my online store.

Lovable’s response?

“Here, we made the image transparent.”

I never asked for that. Not once. Not even close.