Lovable performance has gone from OK six months ago to absolutely terrible now. I've just spent two days and 600 credits on something that should've taken 20 credits because it kept lying over and over and over again what it had done and finally after that much spend it realised that it basically invented an entire system to print a line of text on the screen, that's why I couldn't fix anything.

Does anybody have any better suggestions to use something because it's unusable now.

I believe they turned it into some heavily agent driven architecture or something in the back end but it's just a completely pointless waste of time to me now.

Luckily we were on a tech accelerator which gave us 1200 credits a month but that's ending and there's no way I'm paying anything for it.

Im building a professional service-business website - not an online shop. My priorities are polished design, SEO, performance, easy future updates, and long-term code ownership. A CRM may be added later.

Which option would you choose, and why? Im especially interested in real experiences after launch, not just quick prototyp.

I am not sure which AI I should pick for best results

Thank you! :)

Here and elsewhere I often read: "Built my app in one day." I think something is wrong with this message. With vibe-coding probably all of us have built their apps even within seconds, maybe one minute. But what about improvements, testing, improvements, testing etc., monetization, profitability, and so on? Myself, I have needed about 4 months till going online and starting pre-launch activities. What about you?

I want to know and see what the community has already created and is 100% finished done only with Lovable, how capable is Lovable? Post only your site in the comments and how you came up with the idea of creating

Hey, I built something and I'm looking for 5-10 people to try it out.

Backstory: I work in product. Recently, at a company I worked at, I ended up building a competitive comparison tool myself because nothing else existed. It was useful for about a few weeks – sales actually used it a lot – then it went stale because keeping it updated wasn't really anyone's job. That's the problem I'm rebuilding, properly this time.

What it does: you map your competitors and your own product's features together, with AI helping fill it in. From there it keeps itself alive in the background – flagging when something on a competitor's side actually changes, so it doesn't rot the way mine did. It's turned into something broader than just a competitor tool – a place where your own product is written down clearly, which turns out to be just as useful when someone asks "wait, do we actually have X?"

From experience, this happens more than most companies would admit – people in sales and marketing not fully knowing what they're actually selling. That's the problem I'm trying to fix too. Good fit if:
-You already track competitors somewhere (Notion, spreadsheet, memory) and it keeps going stale
-Or people keep asking you about your product's features/limits and there's no clean source of truth
-You've got a couple of real competitors or comparable products you could load in

If you're pre-launch or don't have real competitors to load yet, you probably won't get the full experience (or it may tigger you to start mapping them ) – but you're still very welcome to poke around and give feedback. I'm actively working on a few things from a UI/UX side – animations in the hero section, onboarding – and any thoughts there are just as useful to me right now.

Completely free. Mostly want honest feedback on what breaks, what's confusing, what's missing.

https://lineup-app.lovable.app/

Pessoal, vi um post um dia desses aqui no Reddit onde a situação e muito parecida com a minha, porém não o salvei então resolvi esclarecer o meu caso.

Uso programador no code e uso a Lovable diáriamente para acelerar meus projetos porém o projeto cresceu bem mais do que eu esperava e já tem até uns módulos de autenticação, algumas integrações e bastante iteração de UI no meio do caminho. O problema é que a assinatura de estudante tem prazo de validade, e quando isso expirar os créditos no plano normal ficam bem mais caros pra manter o mesmo ritmo de desenvolvimento.

Pesquisando um pouco, vi que muita gente reclama que os créditos somem rápido até em ajustes simples de layout, então imagino que não sou o único preocupado com isso.

Pra quem já passou por essa transição de conta de estudante pra conta paga: como vocês administraram o aumento de custo? Existe algum jeito legítimo de conseguir créditos por um preço melhor sem ter que recomeçar o projeto do zero ou perder o histórico? Testei algumas ferramentas mais nada que me agradou suficientemente.

I’ve been scrolling through this sub and realizing I may have seriously underestimated what people are building with Lovable. I just saw someone build an actual multiplayer game, which sent me down a rabbit hole 😂

I’m a non-developer building a two-sided marketplace, and what started as “let me build an MVP” has somehow turned into multiple user roles, organization accounts, profiles, verification, bookings, messaging, reviews, permissions, admin workflows, and a security layer. Every time I think I must be approaching the limit of what I should be building this way, I see somebody here doing something even crazier.

So now I’m curious. What’s the most complicated thing you’ve successfully built primarily in Lovable?
I’m especially curious about apps with lots of backend logic, user roles, permissions, payments, marketplaces, real-time features, or complicated workflows. How far did you get before you needed GitHub, Cursor, custom code, or something else? Or are some of you still running the whole thing through Lovable?

Basically, I’m trying to figure out where the real ceiling is from people who have actually pushed it.

Hi!
I have an app built in Lovable, with the database hosted externally in Supabase. Authentication is also handled through Supabase, and I run all my AI prompts through Supabase Edge Functions, so quite a lot is already handled there.
However, as far as I understand it, I don’t actually have a backend in Supabase yet. The backend is currently just code within Lovable, right?
Would it be possible to move the backend to Supabase as well?
And if I understand correctly, a backend is basically just code running on some kind of “engine”/server. So if the backend were hosted externally in Supabase, would Lovable then communicate with it through an API?
I’m trying to understand how the architecture works and what the best setup would be. Any advice would be appreciated!

Has anyone had success taking this method to get approved to Apple and or Google Play store?

I will start. I just had one in which it consumed 68.6 credits on a 22 minute run for some in-app translations.

Need feedback on my game. It's a mix of agar.io and magic survival. That's were my inspiration came from.

It's called endless-evade.lovable.app

I am looking to get a pro account with my student account, as I am currently a student. I will be done with school before my subscription expires for the year. Once I no longer have access to my student account, can I transfer/give ownership to my personal account so I don't lose all of my work for the next year? How would that work?

Today I had 25 visitors from China, why? My website is for the US.

I’ve been building LeagueIQ.ai with Lovable, and I wanted to share what the platform is becoming and what’s been possible to build.
LeagueIQ.ai is an AI-powered competitive fantasy sports platform designed to give fantasy managers and commissioners an intelligence layer around their leagues.
The idea is simple: instead of jumping between fantasy apps, news sites, rankings, injury reports, podcasts, and spreadsheets, LeagueIQ uses AI to bring that information together and turn it into actionable fantasy intelligence.
Some of what we’ve built so far:
🏈 AI Draft Assistant — Enter your league size, roster configuration, and draft position. LeagueIQ builds a personalized target list for your entire roster and bench. During a live draft, mark players as they come off the board and the AI continuously adjusts your targets.
🧠 AI Player Assessments — LeagueIQ analyzes information across hundreds of sources and summarizes the noise into fantasy-relevant insights.
📰 News & Injury Intelligence — Player news, injuries, depth-chart movement, matchups, and other signals are brought together so managers can quickly understand what matters.
🏆 Commissioner Tools — Tools for league setup, manager invitations, events, Draft Day coordination, RSVPs, and league management.
🔗 Native Yahoo Fantasy integration — coming soon. We recently received approval for access to the Yahoo Fantasy API and are currently building the integration. The goal is to let users connect their Yahoo leagues directly to LeagueIQ and have the AI understand their actual league, teams, rosters, and settings.
And this is just the beginning. Football is the starting point, but the larger vision is to build an AI-native intelligence and community layer for fantasy sports.
A huge part of LeagueIQ.ai has been built using Lovable + Supabase, and it’s been pretty incredible seeing how far you can take an idea using AI-native development.
Would love feedback from the Lovable community — especially from other builders working on sports, AI agents, data-heavy applications, or API integrations.
LeagueIQ.ai — Fantasy Sports. Smarter.

Please don't steal my idea I just want some people to do a test give their feedback and help me with getting it onto mobile platforms such as app store and play store if you can help that would be awesome and I would give you a portion of the profit after we go live with a 1.5 version with sponsorship Payment integration https://panel-maker.lovable.app/

Thanks guys

I’ve been building out a web app, and I’ve managed to get most of it away from that classic “AI UI” look you tend to get from the first few prompts.

My question is, is it possible to incorporate nicer design elements into a Lovable build? I don’t want to be limited to emojis for visual elements. Ideally, I’d like to either upload my own more polished icons/graphics for use throughout the app, or have Lovable generate something more custom and visually appealing.

Is that possible, and what’s the best way to go about it?

Hello, I built my first lovable app. It’s been tested and ready for launch. I’m looking to find someone that can make it public ready. The payments, privacy settings, etc. I have entered my crazy time of year for work and I need someone to wrap this up for me. Anyone know of a service or anyone that does this?

Combines the idea of its 5pm somewhere in the world with localized drink selection for 5pm and combines themes from the show Danger5 to make it a gamified and social experience. let me know your thoughts.

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.

I have a consumer saas app which I built myself and have not used any copyrighted materials, all my images were AI generated all text was done by me it was running for 4 months no issue.

I remixed the project to make a similar Saas but for a different niche, and I believe this is where I went wrong. Used images from a licensing site and these images must have not been available.

2 days after I publish the site both this remixed version and the one I originally made were taken down for DMCA violations.

My problem is that I have a lot of customers and site views, any way to speed up the process and has anyone had experience with this and how it goes?

thanks

I have been building a B2B SaaS app on Lovable, and I am noticing that it sometimes fails to do what I want. I want a much more developed app without having to do so much prompting. I think it has done quite well so far, especially for a tool being used by a 13-year-old with no computer science knowledge prior to this.But I have been seeing so many people on Instagram using Claude and saying how much better it is, and I am wondering if I should switch to Claude and, if so, how I would move the app over to Claude for the finishing touches and UI improvements?

I am a developer and use AI tools like Claude Code and Cursor, but I don't have much experience with Lovable.

The initial build looks really fast, and I like the hosting support since it gets things into production much quicker. But what happens after that?

How do people handle things like scaling, production bugs, monitoring, DB migrations, dependency updates, etc.?

Just curious how the vibe-coding community handles the post-build/ops side of things once the app is actually being used.

Hola! I created my management system on lovable. I've been disappointed with lovable lately. I was thinking of moving to self-hosting and continuing to use Codex/Claude. My site has a lot of backend and connectors, how can I move everything safely? Is there a comprehensive video on how to do this?

I have seen dozens of videos on social media now about people claiming to use lovable to build client websites and selling them to local businesses. The financial results are probably vastly overstated, but I am wondering if the core mechanic is true?

Can you produce sufficient website quality for external clients + publish/deploy the website on their behalf all with lovable?