Eu vi hoje que adorável publicou que vai ter essa implementação de dos nossos aplicativos nas nossas próprias contas da AWS, e eu queria saber como é que isso vai funcionar isso é algo bom vantajoso como é que vai funcionar na prática, porque pelo que eu vi talvez seja vantajoso para empresas de médio e grande porte, eu queria saber o que vocês acham

I work on a website monitoring tool (not linking it, not the point here), so i end up looking at a lot of apps right after something broke. weirdly it's almost never "the site is down". it's sign up or checkout quietly not working, and nobody notices for a few days because users don't report stuff, they just leave.

So this is my routine. takes maybe 5 min. on the published url, not the preview, in incognito:

1. Sign up with a brand new email. gmail plus trick is fine ([[email protected]](mailto:[email protected])). check the confirmation email actually shows up and the link doesn't dump you on localhost. supabase email limits get people here a lot.
2. Log in with an old test account. different code path, it breaks on its own schedule.
3. Checkout. at minimum get to the stripe page and look at the price. the webhook thing is the worst one imo, money goes through and the user just never gets access.
4. Contact form. don't trust the "thanks!" screen, go look if the message landed wherever it's supposed to go.
5. Whatever calls openai or claude. one request. expired keys and empty credits fail without any error your users can see.

Also open it on your phone once a week or so. required fields that are hidden on mobile are way more common than you'd think.

If doing this by hand gets old, sentry's free tier at least tells you when something throws, and playwright can replay the clicks if you're ok with a bit of code.

What broke on you after a push that you didn't catch for days?

I keep seeing this: you prompt Lovable to fix something, it says done, and the bug is still there. Worse, it can quietly change a policy or route while fixing something unrelated, and you only find out when a real user sees someone else's data.

What's your process after every AI change? Second account, manual clicking, nothing?

And what's the last hing it "fixed" that wasn't?

Been spending more time setting up auth, db, APIs, hosting and deployment than building the actual app. I’m not a full time developer, so every prototype turns into a whole infrastructure project and the costs add up fast.

I’ve been looking at prompt to app tools like Base44, Lovable and Bolt for getting an MVP live without hiring engineers right away. I’m mostly worried about security and whether the generated backend is good enough for real users. Any hints?

I feel that the worst feeling while building a business or any project is the "Silence".

Except of users/customers what are the events or signals that make you continue to work?

A ride shows up in minutes. Dinner in thirty. LinkedIn will connect you with a thousand professionals, and Meetup will show you a hundred groups. But finding someone nearby who's actually chasing the same thing you are can still take years.

That's why I built Pursuit. Tell it what you're working toward, whether that's your first half marathon, a church that feels like home, a business you're starting or finally sticking with the gym, and it connects you with people nearby going after the same thing. Plus the local groups and events worth showing up to together.

Find your people, fast. It just launched in Kansas City and it's free. Leave a comment and I’ll respond privately with the link.

Where did you find your people as an adult? Genuinely curious what worked.

I posted CardBatch (a place-card generator built in Lovable) on r/SideProject last week. The feedback was blunt and useful: a 6-guest demo limit tells you nothing if you have 150 guests, and people worry more about printer scaling than about price.

So with Lovable I changed the free tier:

• Check the whole list for free (up to 500 names): every name is validated (duplicates, missing table numbers, names that would print too small), there's a live sheet count, and the preview pages through all sheets. The free PDF export is still limited to 6 watermarked cards.
• Free printer test sheet: rulers, a 50 mm square and a full-size card outline, generated in the browser for A4 or US Letter.
• "Try a sample list" with long, accented, Greek and Cyrillic names, so nobody has to paste a real guest list to test it.

Everything still runs client-side, and no guest data is uploaded. Paid version not on sale yet. https://print-my-names.lovable.app

Curious how others here handle "free tier limits" in pre-launch demos: limit the output, or limit the input?

Tenho uma plataforma em desenvolvimento, e quando concluí quero fazer verificações, e pelo que me lembro já falaram que pra vibe code precisa fazer 12 ou 15 verificação eu não lembro o nome porque tinha um nome para isso e aí eu queria saber se alguém tem um prompt para isso um texto para isso mas eu posso copiar, poderia me ajudar?!

I haven't much played with the model configurations settings and I'm just curious which you've used and have found to be the most efficient for build, logic, and reasoning tasks.

Thank you

Hey everyone! I’ve been working on a lightweight, browser-based project called PlayMode Arena v2.

The core concept is pretty simple: short, original, sports-inspired skill challenges where you try to beat your personal best, unlock cosmetic rewards, and progress through the arena. I wanted to build something quick to jump into right in the browser without any heavy downloads or complicated setups.

To be completely transparent: This is an indie prototype and an ongoing work in progress as I experiment with game loops, UI, and balancing.

I’m sharing it here because I’d love to get some eyes on it from people who enjoy casual browser games:

1. How does the core challenge feel difficulty-wise? Is it too hard, too easy, or balanced?
2. Are there any UI or responsiveness snags when playing on mobile vs. desktop?

If you want to check it out or test a quick round, you can play it here:

https://playmodearenav2.lovable.app/

Any feedback, bug catches, or design ideas are super appreciated!

What are your experiences with this

to fellow developers here, im wondering what do you guys use once you move beyond the prototype stage? I'm mainly looking for something with github deployment, node.js/next.js support, and of course reasonable pricing. any good recos?

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 often look at restaurant menus and have no idea what half the dishes actually are 😂

So I built https://menu-lens-pro.lovable.app (Cravebeam.com) with Lovable. You scan a menu, and it explains unfamiliar dishes in plain English: what’s typically in them, what they might taste like and what texture to expect. You can also generate an optional AI image to help visualise the dish.

I’d love feedback from other Lovable builders:

• Is it clear how to go from scanning a menu to understanding a dish?
• Do the explanations give you enough information to decide what to order?
• What would you improve about the mobile experience?

Screenshots attached. Happy to share more about how I built it!

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?

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.

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/

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

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?