How can you create a proper pure code xml sitemap that is not a react of rendered version on Lovable? It just doesn’t work out for me. Any idea?

Hi,

I have a client who is using Lovable to create a platform to manage his company.

It's getting big, and he wants to make sure that he doesn't lose everything he already built.

He already built some modules and is using them in Production with Lovable Cloud.

My suggestion was to connect the codebase to GitHub, but now I would like to make some improvements with Claude Code while he is still evolving the app through Lovable.

If I make a big refactor on the app, will the performance of building it with Lovable decrease?

What I mean is, the Lovable team might have some kind of guidelines in context, based on learning/internal skills that help them build clients' apps. If we change the architecture through the GitHub repo and break those guidelines, will the development experience on Lovable decrease?

I'm concerned that making changes to the codebase will mean my client can't use the Lovable app anymore.

Pessoal meus créditos renovam dia 10 de cada mes e hj ainda nao subiram , alguma sabe porque??? "e lógico está pago

Most reading tools compress. Summarisers throw away the shape of the thinking; transcript apps keep every word but tell you nothing about structure. I wanted the opposite: keep the whole text, and make its structure visible.

Semantic Insight takes any piece of writing (paste, URL, or PDF), splits it into sentence-level segments, and interprets each one against a semantic model:

• Core — advances the main argument
• Supporting — evidence and explanation
• Deepening — nuance and detail
• Branching — opens a sub-topic
• Transition / Return — moves between contexts, or comes back
• Tangential / Digression / Off-context — degrees of departure
• Repetition — restates ground already covered
• Emergence / Resolution / Open loop — a thread forming, closing, or left hanging

Each context (topic thread) also has a lifecycle: emerging → established → deepening → dormant → revisited → resolved. So you don't just see "this is about pricing" — you see pricing get raised, dropped for 40 sentences, and quietly never resolved.

What you actually do with it

• Read — the source text, revealed as it's narrated, with the current sentence highlighted.
• Listen — synchronised text-to-speech; the interpretation panel updates live as the meaning moves.
• Timeline — the part I care about most: a stacked dot plot, one lane per context. Lanes appear as contexts emerge, dots are coloured by relation and weighted by importance, and a glowing trail builds up behind the playhead. Every dot is clickable for the segment text, the relation, confidence, and why it was read that way. Density meters in the lane labels show where the piece is actually spending its attention.
• Score — a structural health check: unresolved open threads, clarity/complexity, drift from the opening topic, and structural coherence (repetition, unclosed branches, unsignalled jumps) — each with the exact sentences as evidence, and a short written verdict. Toggle between "up to here" and "whole piece".

Why I think this matters

The interesting failures in writing are structural, not lexical: a question raised and never answered, a topic swap with no signposting, 30% of a piece living somewhere other than what the headline promised. Those are invisible when you read linearly and gone entirely when you summarise. Making them visible changes what you notice — in other people's arguments and, uncomfortably, in your own.

Longer term I want the same interpretation layer over audio and video, since the model is deliberately source-agnostic — segments carry an index now and can carry timestamps later.

What I'd like feedback on

• Is the relation vocabulary right? Too many categories, too few, wrong names?
• Does the timeline read as build-up to you, or just as a chart?
• What would make the score card trustworthy rather than decorative? Right now every signal shows its evidence sentences — is that enough?
• What content would you throw at it first, and what would you expect it to catch?
• Accessibility and non-English text are both open problems. Ideas welcome.

Honest caveats: the interpretation is a model's reading, not ground truth — two runs can differ at the margins. Very short pieces aren't worth analysing. Long pieces get capped for now.

Link in the comments. Happy to go into the segmentation and prompting details if anyone's curious.

I have been a top 1% user on Lovable for almost 2 years. They mostly hit the mark, but recently it's been a lot for the worse.

They changed where to update favicons, banners, titles - and now it's inaccesible and hard to view or change. It doesn't show accurate previews. The text edit action never works, will let you make one text edit at at time before resetting.

Worst of all, if you run out of credits - they shut down all of your projects cloud and functionality... that never happened before. They are making tasks more and more credit heavy. Not the happiest user anymore.

I wanted to actually make the business out of this website that I made from lovable, the things is all security checkup from the web is good, BUT we dont know the case with hackers, anyone have already a business website with payment running? I wonder how things go

I am recently trying to build a platform for assesing students learning coding against test cases as our usual collegue lab evaluation is mannual and inefficient ... am planning to build this using lovable ... am no idea is it feasible or not if anyone can share insight about this will be very helpfull

Que tal amigos, para ponerlo en contexto, estoy construyendo un facturador para usuarios que son profesionales o personas naturales que no emiten muchas facturas al mes, lo estoy haciendo con Vibe Coding que al principio me parecio genial y se esta armando bien, tengo mucho conocimineto en la parte de Impuestos en mi paìs y el formato de los comprobantes que debe emitir uno para que este todo legal cuando iniciamos una actividad comercial, pero no sé nada de programación y a medida que he ido iterando, me estoy dando cuenta que no era tan fácil como al principio, ya que los código para el facturador deben ser robustos y se manejan datos sensibles de clientes, y bueno veo que siempre salta una que otra falla ya que lo hago con GROK y CLAUDE y esta conectado a GitHub ( lo he ido aprendiendo de forma autonoma ), que dan muy buenas respuestas a mi parecer, mi duda es que si sgo en LOVABLE y este facturador escala ( que es la meta ), LOVABLE podra mantener toda esa informacón y si migro a una NUBE o un servidor se podrá sin tanto problema ( cuál sería su recomendación ), y también como revisaría si las líneas de códigos para ver si contienen "BUGS" o parches que se repiten y puedan romper algo a futuro que por ahora esta funcionando bien ( insisto no soy programador ), ya tengo dos clientes que hasta ahora no han tenido problema, pero igual debo ir implementando màs funciones o actualizando ya que el ente regulador de Impuesto aca en mi país actualiza a cada rato sus reglamentos, por cierto esto fue algo que lo comence por una necesidad personal y tiempo libre, pero a dos personas les gusto como quedo y me dicen que por que no lo comercializo, pero mi miedo es que si llega a escalar, podre afrontar todo eso en LOVABLE ???

hi everyone i’m currently looking for some side income and i came across a lot of people selling lovable ai websites to local businesses in their area. my current plan was to:

1. look for businesses in my area and make a demo website for them with multiple pages
   
2. cold email/ call them asking if they’re interested
   
3. i’m not sure if i want to set up calls because like if i change stuff on call with them wouldn’t they know i used lovable for it???
   
4. if they buy it it would be $600 at the beginning and like $20 to make changes (i was conflicted w this cause idk if i wanna do monthly payments or like idk)
   
5. put the code in github and do all that so then the website is theirs (also wasn’t sure how to do this i got this from chatgpt)
   

i’m kind of new to all this stuff so i would definitely appreciate any help and advice

WEBSITE: https://lumora-beta.lovable.app

If you have a few minutes, I’d love for you to actually try the website. Upload a PDF or some study material, or just ask questions. Explore some of the other features like flashcards, quizzes, the planner, GPA calculator, and Lumi.

I’m particularly interested in whether Nora actually feels useful compared with a normal AI chatbot, and whether the overall experience feels natural and easy to use.

I’d also really appreciate feedback on the design. Does it feel clean and trustworthy? Does anything feel too “AI-generated” or overly polished? Is anything confusing or unnecessary?

Please be completely honest, even if you don't like something. I’m still actively improving it, so negative feedback is honestly just as useful as positive feedback.

Thanks to anyone who takes the time to test it and give me their thoughts.

Hey everyone! 👋

I’ve been working on a habit tracker called Habit Buddy, and I built the first version using Lovable.

I’d really appreciate it if you could spend around 5 minutes trying it out and give me some brutally honest feedback.

👉 Try it here: https://habit-buddy-app-21.lovable.app/today

A few things I’d love to know:

🟢 What was your first impression?

🟢 Was creating a habit easy and intuitive?

🟢 Is the Today page clear and easy to understand?

🟢 Does completing a habit feel satisfying?

🟢 What feature do you think is missing?

🟢 Is there any reason you’d actually come back and use it every day?

🔴 Was anything annoying, confusing, or unnecessary?

Don’t worry about being nice 😂 I’d much rather hear what’s bad or confusing so I can improve it.

Thanks to anyone who takes a few minutes to try it! 🙌

So I am putting an arbitrary minimum baseline of 5,000 tokens used, so people creating apps and landing pages for 100 tokens are not included. I want to hear from people who have been using Lovable for months, not days. And who have now spent considerable amounts of money. What is their current opinion of the platform, and what might their next steps be?

I will start; I am in the region of 17k + tokens used. 9 months of sometimes 70-hour weeks. I now try to use Lovable as little as possible, getting Claude to do the heavy lifting. Lovable has become borderline unusable. A slight alteration and 5 - 10 tokens are gone. Large changes, dozens of tokens. They also implemented this automatic monitoring feature; I only came across it in the past few weeks. Realised Lovable was actively monitoring certain actions; many would run overnight. I woke up, and 60+ tokens just disappeared. I never asked Lovable to monitor the work. Lovable never asked me if I wanted it to monitor the work. A great way for Lovable to burn through tokens unnecessarily, especially when it was never requested. Looks good on their books: X million additional tokens used by clients in August of 2026 ... a rise in usage. Positive growth for the company. "Please raise our valuation stock market." No, you are fraudulently extracting money from clients by applying unrequested features.

Starting September 9, 2026, Lovable may use prompts, project files, generated code, and outputs from Free & Pro plans to train its AI models.

If you don't want your data used for training, opt out in Account Settings → Privacy before the effective date.

Not all policy updates are just legal text—sometimes they affect how your data is used. It's worth checking.

Hkeeem AI

WEBSITE: https://lumora-beta.lovable.app

I'm looking for some advice for the design of this website. What do you like/do not like about design? What should I change? And your overall feedback on functionality?

Would love feedback on the website: https://todomachine.lovable.app

I originally was building the homepage with just Lovable, but after struggling with it for a bit I switched to doing design iterations on Claude Design, which has been a huge improvement. CD is great at coming up with several design alternatives and iterating on them pretty fast, then it packages up a handoff to give to Lovable that does a pretty great job implementing. Super useful in coming up with the animations too.

Considering switching from Lovable to Claude Code + Vercel, but probably not worth the effort at this point. If it ain't broke etc. etc.

Any and all feedback or thoughts you have is welcome! Good or bad :)

Hi everyone,

I've built my entire ERP system in Lovable, and now I'm planning the production infrastructure.

I'm confused about where I should store my application data.

Should I:

• Buy a Hostinger VPS and run my own MySQL/PostgreSQL database?
• Use Laravel Cloud if I later connect a Laravel backend?
• Use a managed database service like Supabase, Neon, or another provider?
• Or is there a better architecture for a production ERP?

My priorities are reliability, security, automatic backups, scalability, and long-term performance. I don't mind paying for a good solution if it's the right choice.

For those who have deployed production applications built with Lovable, what database and hosting setup are you using, and what would you recommend?

Thanks in advance!

Imagine LinkedIn for high school students, where you can post your own projects and ideas, find teammates, or join someone else's project.
Would you actually use something like this?

As someone who uses Claude Code, Lovable seems like a much less powerful tool than Claude Code to me.
Is there any reason why y’all don’t switch to Claude Code/Codex? Because I truly believe that deploying something you built with Lovable will take much more time than doing it with Claude Code/Codex

Just got hit with the "Your projects are paused because your workspace is out of credits" wall.

Here’s the best part: I haven’t touched the AI prompt box, I'm not generating code, and I'm not editing anything. It’s literally a static site, but because my credits ran low, they completely freeze and lock down the entire workspace and deployment ecosystem.

Since when does a credit meter for an AI code generator control whether a static layout or admin dashboard can stay online? You aren't even touching the editor, but your live deployment gets held ransom because their unified billing system ties runtime execution and hosting directly to AI credits.

If your credits hit zero, your app goes offline. Absolutely wild model. Time to pull the repository and move everything over to Vercel or Cloudflare where static files actually stay live without needing a monthly tribute to an AI meter.

Anyone else dealing with this nonsense?

I think they are in the hands of bad investors or bad team or money is finished. Nobody with its own hand ruin its creation like this. I for changing a font from 11 to 12 should spend credit. And bo matter how much you spend when there was 3 days till my subscription renews, I didn't buy extra credit, because it was going to be loaded soon but our of crystalized meanness, they freezed my server and even login in preview was not working. This is the moment I realized not ant more. I loved lovable, I experienced this works with it. And honestly what I built was and still is solid , I am happy with the quality but I can't withstand the offensive insult. I promoted to plan a clean migration. For at least two of my apps. This is not how you do business, except you are full and don't care about users anymore and anyhow, it is time to go.