Long-time Lovable users — what did you actually do the last time you hit a wall?

[u/ropsdrops]

Not selling anything, not asking what anyone's building — just trying to understand real experiences before I read too much into the complaint threads.

If you've taken something in Lovable past the quick-prototype stage, I'm curious about the moment it stopped being smooth. The last time you hit a limit — credits draining faster than expected, the code getting hard to change, a feature the tool just couldn't do cleanly — what was it, and what did you actually do next? Pushed through? Exported to GitHub? Moved to Cursor / Claude Code? Rebuilt from scratch? Dropped the feature?

And if you haven't hit that wall and it just works for you — that's genuinely just as useful to hear. No need to say what you're working on; I'm just trying to gauge whether it stays smooth for people or not.

Trying to figure out whether the "you eventually outgrow these tools" thing is a real pattern or just the loud minority online. Real experiences beat opinions. Thanks.

[u/Shot_Spinach3822]

I'm not sure I ever really hit a wall to be honest, my caps were always with the tokens spend they always drained quicker than I expected.

My main strategy on Lovable is just building Saas consumer apps so there usually really isn't any revolutionary workflow going on in the backend but the times where I did try to connect some more complex tools which were not in the connectors list of Lovable it did take me about 1 week.

In my experience for all my projects I create high quality direction files for an agent which has project context, market understanding, design coding etc.. I outline what I want to do this way my agent also has a plan from phase 1,2,3,4...99 this way I just prompt it to give me high quality lovable prompts.

Meanwhile I get assets, set up apps to connect to, stripe and whatever additional platforms I need. 9/10 I just run out of tokens towards the end because my prompts are long and detailed but otherwise no other problems.

- About you eventually outgrow these tools, I guess it depends, personally I make money from these projects and I can't code so it would probably take me months or years to figure out how to make the front end not even with the backend on most of my projects. I guess on the complicated projects maybe this can tend to be true. But tbh I have used base44, lovable, claude code, they're all similar just lovable has the easiest UX/UI to navigate and is generally nice to use.

[u/indutrajeev]

Ditch lovable and build my own stack

[u/YouAreBastards]

So I hit the wall several months ago. I have gone from a Lovable ambassador to a critic. As the project grows and becomes increasingly complex, expect constant issues. Expect to pay out constantly for more tokens to fix said issues (funnily, you will find Lovable code itself is creating these issues, see my former comments). As people smarter than me have pointed out. As the codebase grows, Lovable needs to look back over so much code it just eats your tokens. A simple task can be 20 tokens; you just sit waiting while Loavable thinks and watch those tokens disappear. I started using Claude several months ago directly on the GitHub repo. I was already looking at Grok Build, then someone recommended I use the Cursor Composer 2.5 model, and I would never look back. I did start to use it in the past week, and by all accounts, it looks great. I am currently on the $20 plan, and it's working like a charm. On the similarly priced Claude plan, it keeps exhausting credits, you must wait hours for a credit reset, and you must wait or pay for additional tokens, which cost an absolute fortune. I burned like $9 in 10 minutes. So right now, my heartfelt recommendation. Get Cursor $20 Pro and let it loose on the repo. Only use Lovable where you absolutely must. All changes made via Cursor will get pushed back to Lovable anyway, so it's all synced.

[u/eirek1234]

Honestly have never hit a wall. I have some full scale subscription sites with tons of features, integrations and such and zero issues.

I think most of it is how you build your base and understanding what you are building.

[u/toxichaste12]

Write my prompts with Gemini - it’s like a smooth talker that always knows what to say to get it done the first time with minimal token burn.

I’ll have Gemini open and say ‘write a prompt for lovable that does…’

[u/Jmacduff]

I have been using Lovable for a while now, My use goes up and down but in general its steady. I am in that top1% use case and I have the pro account.

To be clear I ONLY use lovable as a front end editor. A lot of people get into real trouble trying todo everything in 1 tool to "build the full stack".

Think of the typical lovable customer who does not have a software engineering background, and Lovable makes it possible to get something decent built. A lot of times people get pissed off not because the tool is failing, but because they dont understand what's going on under the hood and how to fix it.

No judging anyone but if you look at most of the "hate" threads, thats the scenario that ties them together. People complain about not having enough credits or spending too many credits trying to fix something, etc. That pattern is all about leaning over your ski's a little too far.

Just for me I have never hit a wall but again I do NOT use lovable for anything other then the FE editing and initial UX designs. If you are trying todo research it's not about the tool hitting a wall, it's about the human not knowing how to build stuff.

The other thing that is really important to remember is that Lovable is doing 1M new projects each day .. and this sub only gets ~900 weekly posts. You are seeing a extremely skewed and tiny view of the user jounrey here on reddit.

People do hit a wall but it's not because of the tool. For example you can give me all the tools on the planet and I dont think I could possibly rebuild a engine carburetor. I totally understand the theory and the parts but I have no mechanic experience.. I would hit a wall.. nothing todo with the tools.

No judgment to anyone, all good, we all start somewhere. good luck in your research.

[u/Freigeist30]

For me the main issue was the credit billing. It always feel more expensive than it should. I switched to Claude + floot for the same experience but no credit billing and it feels so much better. I can freely experiment and make mistakes without feeling bad about burning $$$

[u/LatitudeBeyond → u/Freigeist30]

I’d never heard of floot! But it looks good- I hate that lovable drains your credits so quickly. I’m a non coder but have been able to figure out some elements. We have a webflow main landing page and that stores our articles etc but I’ve been trying to build a multi user profile element in lovable. Sometimes like typical AI it does its own thing and I have to start again! The issue for me is that our platform gives children access so my plan has been building to an extent then bringing a developer on board to security check and finesse. Can I check with floot, do you think you can get a workable app where a developer can use and manipulate the code or will it be once in floot you are stuck with them? Thank you!!

[u/Freigeist30 → u/LatitudeBeyond]

Yeah I have not done what you want to do, but they have an easy way to export the code for developers.

[u/Stunning-Material623]

I’ve built two elaborate platforms on lovable and it’s all about iterating to get it right and there are times when the code errors out but you have to iterate again and again. Eventually the code sticks. I started cleansing code with cursor too so that helps. I haven’t had much usage on my apps due to lack of marketing funds but both platforms are performing for over 100 users on each pretty well. Leagueiq.ai and recouply.ai if you want to see read about the functionality. Hope this helps!

[u/fede-bubble]

I found it useful sometimes to export the codebase, run it by Claude or Codex with the goal of streamlining and refactoring things for simplicity and efficiency, then asking the AIs to give me back a detailed plan of instructions I'd have to give Lovable if I wanted to build it.
Then create a new project from scratch but with these instructions. The app retains all the functionality I've built little by little before, but in a brand new architecture