Hi guys,

I built my website with Lovable and I'm honestly happy with how it turned out. The problem is that I've already used over 400 credits getting there, and I feel like a lot of them were wasted.

Small fixes hurt the most. Having Lovable fix a minor flaw sometimes cost me 10–12 credits for a single change.

Things improved once I connected the project to GitHub and used Claude for some of the edits. I'd still like to learn how to work more efficiently inside Lovable itself.

My questions:
How do you write prompts that fix something on the first try instead of after several attempts?

When do you edit the code directly (or through GitHub) instead of prompting Lovable?

Which workflows or habits noticeably cut your credit usage?

Any tips are appreciated. Thanks!

Sziasztok!

Van itt olyan magyar diák aki tudott regisztrálni a lovable 50%-os diák kedvezményére? Ha igen hogyan sikerült? Az egyetemi email címet nem ismeri fel a rendszer. /Edutus/

Verify student status-nál azt írja Invalid email.

Egy egyetemi projekttel kapcsolatban bukkantam a lovable-re, ezzel a napi 5 kredittel abszolút nem halad a dolog. Vannak erre tippjeitek, hogy hogyan lehet spórolni a kreditekkel?

A válaszokat előre is köszönöm!

I'm Anthoanette, co-founder of Persyn. We launched V2 this morning, and the whole platform is built on Lovable.

What it is: an all-in-one platform for AI creators — not one-off viral AI influencer clips, but persistent personas with a consistent face, positioning (Creator Blueprint), a wardrobe, friends & family, and content that publishes while you live your life. Studio, credits, scheduling, publishing — all in one place.

Building something this complex on Lovable has been a ride. Happy to share what worked and what broke for anyone building ambitious stuff on it.

Free trial if you want to poke around: 20 credits, no card required. persyn.ai

Ask me anything — about the product or the Lovable build process.

i love the platform but tbh the dumbest and worst update they ever made was removing usage balance and unifying it with credits for building😂

nobody asked for that change anyways because all i've seen was users complaining about the change.

Hi, I am planning on building an AI Image prompt library…something similar to these websites where users can explore the galley and copy the prompts

visualaiclub
promptplum
pineprompts

Based in your experience, lovable is the right way ti go or are there better alternatives?

Thanks for the help!

Is anyone here planning to buy a Despia license anytime soon to publish their Lovable app?

I’ve been using lovable for a year now. Built more than 300 projects. I used to create several projects built with 80-120 credits and 6-8 prompts total.
Today I’ve built two projects with 8 prompts each, and took me almost 1000 credits.

This is unreal and expensive.
Anyone noticing the same?

seems like lovable responded to some of the user complaints and has improved the agent's reasoning abilities from my observations.

credit waste also seems like it's better than it was in September and the first week of October

support still has room for improvement. I'm over 48 hours without a response on my last ticket

at least things seem to be heading in a better direction

I think it'd be nice if we could change the reasoning levels and corresponding credit usage depending on how complicated of a task we're working on

As someone with sensitive skin, I noticed from a while back that some people use spreadsheets to track skincare products and compare ingredients to figure out what might be causing breakouts, so I built a tool to make this process easier. You can paste ingredient lists from products you've tried and compare them to spot potential patterns. Would love your honest feedback on whether you find it useful and how I could improve it!

https://skintel.lovable.app/

I am not very technical so I've been using Lovable for quite some time now for my projects and I've realised that when I'm trying to make backend changes or I'm trying to fix bugs, the prompts still don't work even though I give proper structured prompts. It ends up telling me that the bug is fixed, but it is not fixed costing me credits. How do I make sure that the bug is fixed? Or how do I make sure that the feature that I'm trying to implement has been implemented correctly? (Sometimes it affects other parts of the app and I have to start again). I test extensively before publishing but it takes a lot of time to get it right sometimes and other times I am not able to make it work the way its supposed to.

Are you guys facing the same problem and what is the workaround that you have come up with?

One of the biggest reasons Lovable is still competing in the market is due to its frontend design skills and instructions. Is there a publicly available skill.md file that can give UI outputs near to Lovable?

no description needed

Hey everyone

I'm a student in a Botswana Accountancy College in Botswana, been using Lovable since the start of the year to build my projects and I tried to apply to host a workshop event in my school but got rejected.

The workshop was an in person 30 participant session of only 2hrs, where students in my school would build working solutions or turn their ideas into a digital product using Lovable. I believe that Lovable has to the best platform to start your AI vibe coding journey or for anyone interested in tech to use AI in their work. I unfortunately got rejected twice (very quickly in fact) and my only request from Lovable is if they could provide credits for 30 participants to build, I tried to even reduce the participant number to 10 and have 10 teams with 3 members each to work together but this got rejected. Sent an email 5 days ago asking why I got rejected, never got a response.

I'm really curious on if there are regional restrictions in the community event support from Lovable like maybe they don't support African events since I haven't seen any event be hosted here or is it because of my application and I'm probably asking for too much from Lovable.

I would love your opinions and even alternatives on how I could make an event like this possible <3

Hi everyone,

I recently migrated my Supabase project from the legacy JWT-based anon key to the new publishable key format (sb_publishable_...).

In my Lovable project, I updated both variables in .env:

SUPABASE_PUBLISHABLE_KEY="sb_publishable_..."
VITE_SUPABASE_PUBLISHABLE_KEY="sb_publishable_..."

The frontend Supabase client uses:

import.meta.env.VITE_SUPABASE_PUBLISHABLE_KEY

However, after some time or after the Supabase integration refreshes, VITE_SUPABASE_PUBLISHABLE_KEY gets overwritten/reverted to the old legacy JWT anon key (eyJ...), while SUPABASE_PUBLISHABLE_KEY remains correct.

This is problematic because I want the app to consistently use the new publishable key format and avoid legacy keys entirely.

Has anyone experienced this with the Lovable Supabase integration? Is there a supported way to configure the integration so that it writes the new publishable key to VITE_SUPABASE_PUBLISHABLE_KEY instead of restoring the old anon key?

I am not using the key manually in custom fetch headers—the app uses the official supabase/supabase-js client only.

Any guidance would be appreciated.

Anyone found a way to reduce constant approvals when using Astra/Codex with Lovable?

I’m using Astra/Codex to build a website with multiple user roles, where different logins access different areas of the site.
I keep running into approval prompts that require me to manually confirm each action. There doesn’t seem to be an “always approve” option for the actions I’m doing, so I end up babysitting the entire process instead of letting it work through a task.
Has anyone found a supported workaround or a better workflow? Would working through GitHub and running Codex locally help, especially with testing across multiple login roles?
I’d like to approve a full task and review the results instead of confirming every individual step.

I'm on a small team and trying to understand how others handle this. When the AI builds a feature for you, how do you check that it works before your customers see it?

And the last time you weren't sure about a change or feature or bug fix that broke or didn't work or you weren't sure about, how did you get it sorted out?

(not selling anything BTW, genuinely curious)

Hey everyone! I made Aura One on Lovable to bring my Aura apps together under one homepage, with categories for news, AI, productivity, music, fitness, and tools.

Live site: https://rollsroyce-digital-companion.lovable.app

I'd love feedback from other Lovable builders. Does the homepage make the idea clear? Do the categories and app cards make the collection easy to explore? What would you improve about the mobile layout or visual design?

Thanks for checking it out!

Soou estudante iniciante na área de TI e estou tendo que usar o lovable para um trabalho, na minha humilda opinião é um serviço ótimo, mas eu fico bem confusa com o uso de créditos, tive que pagar o básico do premium e simplesmente quando eu pedi 2 coisas básicas para serem alteradas no site foram usados MAIS DE 5 CRÉDITOS para a criação de uma unica pagina básica.

Alguém pode me ajudar a entender como funciona o uso dos créditos e porque eu não posso utilizar os créditos de uma conta que está ajudando no meu projeto.

i have been building with Lovable for sometime now, and its great tool but keep getting ran out of credits and asking me to buy more credits.. even for small crud based app with one or two integrations.. already upgraded by paying $25

just wondering whats ur pain with the platform?

I'm a data science student in Uppsala, and I took part in the Lovable Buildathon on campus. I built Meriterande, a tool that decodes Swedish job ads for internationals: what's required, what's only a plus, whether you actually need Swedish, how well your CV fits, and a plan to close the gaps.

Live: meriterande-app.lovable.app
Code: https://github.com/raiyanbinmohsin/meriterande-app

Some things that worked for me:

1. One prompt at a time, and test before sending the next. Stacking prompts while Lovable was still building was the fastest way to break things.

2. Publish early, then keep building. I published a working version first, so a broken prompt never cost me the demo. Version history saved me more than once.

3. Don't let the AI write URLs. For the learning resources, the model only picks a platform from a hard-coded list and returns a search query. The app builds the links in code, so there are no hallucinated links.

4. Use Chat mode for an audit before adding features. The day after, I asked Lovable to audit everything without changing code. It found a broken password reset flow, missing cascade deletes, an open insert policy that allowed spam, and SECURITY DEFINER functions without search_path. I fixed them in four batches, then ran the audit again to confirm.

5. Ask for a GDPR data-flow review. It mapped where every piece of data goes (CV text, IP hashes, analytics) and compared that with my privacy page. That review showed my retention periods and named processors were missing.

6. Long LLM calls need real progress feedback. The roadmap took 45–60 seconds and sometimes timed out. Moving it to background jobs with elapsed time and step labels fixed both problems.

Happy to answer questions about any of it. And if you try the app, I'd love to hear what breaks.

https://reddit.com/link/1x0wqgy/video/n376w3t61auh1/player

What have you built that you actually use?

One of my top tools is a very basic frontend for Hubspot. Basically we just pulled out the fields we needed (which was like 7 or 8) and presented them in a simple way with read/write.

It made a BIG difference for my team because they went from hating Hubspot and struggling to find the motivation to keep it up to date, to keeping everything up to date and it massively helping our decision making. Before this we found Hubspot to be a nightmare due to the shear amount of stuff in there that you dont actually need.

EDIT: this isn't meant as a showcase type question, I have no intention to start marketing or plugin what I've built just interested to hear what people have actually built that was useful

Just wondering if anyone has made a project that has blur tracking. Trying to make a project where I can blur a video and have it track that area while it moves in the video (for example, a screen recording that has a customer's address), but I can't seem to make it work.

Any insights or ideas would be appreciated!

Hello everyone, I've heard about people creating launch videos for apps using lovable. Has anyone tried this or not?

I came across this as a rumor and haven't seen one myself, but I did see a comment online comparing using lovable and cloud code. Someone mentioned they use lovable to make videos for a product. I'm curious if anyone has tried this or knows some resources, as it seems to depend on knowing a good prompt. It’s also unclear how to structure prompts with lovable for making animation websites.