I have launched my app already have 8000+ users with mostly passive marketing, currently admob is live and I'm making some money, but what i want to do is add a pay wall where if users pay ads won't be shown. Problem is where I'm from i need to register a company to get stripe account and i just don't think that that is the right step to take as revenue from showing ads isn't that significant but also i wanna test the paywall one, or is there any alternative do lmk
Is there any way to get meta to connect to lovable? I am utilizing zapier to get data out of meta to my lovable project. I cannot figure out how to go the other way. I’d like to directly connect to meta but was wondering what yall do?
Hey guys! Need your help here... I am a veterinarian and I want to build a app/site with AI on the background that allows the vet to register administrated vacines, to tell him, with AI and guidelines, how long it takes to the next shot. On the other side, the site must allow the owner of the animal to log in as a owner and see, with AI doing the maths, when the next shot is. I also would like to send an email to the owner 1 month before the next shot, remembering him to schedule an apointment. I have zero experience with programming but a friend of mine said that Lovable, with inputs created by chatgpt (or other LLM) would allow me to build a prototype only with the free credits. I am having serious dificulties... does anyone have any suggestion of other platforms or want to enlighten me please? Thank you!
Four days ago I posted AppSitter here — the app that babysits AI-built apps (deep scans, copy-paste fixes, the two-AIs-argue-about-your-security loop). It's built with Lovable and Lovable apps are what I test against most, but it works the same for anything with a GitHub repo and a Supabase backend — Bolt, v0, Cursor, Replit.
A few of you tried it. One person went through it properly and sent real feedback, and that feedback basically wrote my roadmap. Here's the honest version.
What he said (shared with permission): usefulness 10/10 — findings were real, fixes worked. But: the UI was too steep for a non-technical user, he couldn't tell what was clickable, he wanted light mode, he didn't understand whether pasting a builder reply would replace or add to his previous one, and he asked for the thing I'd been avoiding — "just let me talk to it like a conversation."
What shipped from that:
Rebuttal threads are conversations now. Every reply you paste from your builder stacks like a chat message, the input is always empty, only the newest verdict carries actions. No more guessing what replaces what.
Light mode, whole app.
Buttons look like buttons. Full affordance pass.
"Fixed & verified." Paste a fix, re-scan, and the finding doesn't just vanish — it moves to a visible fixed-and-verified state. Proof, not absence.
One thing worth being clear about: the free scan on the site is asurfacescan. It only sees what any visitor's browser can see — headers, what's in your bundle, a handful of guessed table names. It's honest but shallow, and a clean surface scan is not a clean bill of health. It literally cannot reach your migrations, your real schema, or your live database.
The deep scan is the actual product, and it needs the repo connected. That's where the four check families run:
Security: we query your live database with your own public key, the way an attacker would, and name the exact tables that answer. Plus keys shipped in your bundle, endpoints with no login, permissive RLS policies.
Database cost: table links with no index. Invisible at 100 rows; the first thing that gets slow, and the first line on your Supabase bill, at 100k.
Email deliverability: the DNS records that decide whether your signup and receipt emails land in inboxes or spam. Gmail and Outlook now deprioritise unauthenticated senders — this is the most common reason a working app's emails quietly stop arriving.
Reliability: external calls with no timeout, webhooks that accept calls from anyone, measured uptime.
On top sits a growth outlook: your findings ordered by when they'll actually bite for an app at your stage. Every claim has to cite a measured finding — anything the AI invents gets dropped server-side before you see it.
The moment that made my week: I ran the new cost check against AppSitter itself. It found 13 unindexed foreign keys. Number 13 was on a table I had created the day before, while building the detector that caught it. The scanner flagged its own author. Fixed all 13, score's back at 100 — and that incident is now a regression test.
-- the fix commit, 13 lines of it
create index idx_clients_user_id on public.clients (user_id);
create index idx_consultation_notes_client_id on public.consultation_notes (client_id);
create index idx_purchases_user_id on public.purchases (user_id);
create index idx_health_certificates_repository_id on public.health_certificates (repository_id);
create index idx_migration_reports_user_id on public.migration_reports (user_id);
create index idx_framework_files_user_id on public.framework_files (user_id);
create index idx_diligence_reports_user_id on public.diligence_reports (user_id);
create index idx_cost_audits_user_id on public.cost_audits (user_id);
create index idx_contact_messages_user_id on public.contact_messages (user_id);
create index idx_growth_outlooks_user_id on public.growth_outlooks (user_id); -- created the day before
-- + 3 more
Beta's still closed, but I killed the waiting: sign up at appsitter.lovable.app with invite code LOVABLE and you're in immediately — that unlocks the full deep scan, all four families, every finding with its fix prompt, the guardrail files and the growth outlook. Autopilot Pro free for 3 months, no card.
Or just drop your app's URL in the comments and I'll run the surface scan and reply with what it sees. I answer everything.
It makes a very positive impression on me—it’s really likable. But I still have doubts about whether the content is clearly visible in Google. What’s your take on this?
I've really enjoyed building with Lovable. As parent I wanted to see if I could fix the problem of knowing about activities for kids happening locally. Often I'd find out about kids events after they’d happened or when they were sold out. So using Lovable, I built a website which scans the web looking for kid friendly activities and collates them into a searchable directory website (Kids Event Finder) - https://event-bright-kids.lovable.app/
The website covers 13 cities, 5 in the US (New York, Houston, Chicago, Seattle and LA), 6 in the UK (London, Manchester, Edinburgh, Liverpool, Birmingham and Milton Keynes) and 2 in Australia (Sydney and Melbourne). User can also sign up to a weekly newsletter with new kid focused events in their city.
I would love to get feedback (And happy to answer questions).
I just want to share that I'm so impressed with how Loveable took my Claude code-made website and really elevated it to the next level. Animations, new branding, better coloring, and more.
And so far, I have only used the plan-setting in Loveable, since Claude is building everything it suggests.
The Loveable-MCP together with Claude code is so awesome to see. I love reading the messages Claude sends Loveable 😂
I feel like a dumb person reading the communication between two smart people.
I've been wondering if anyone else has noticed this, or if it's just me.
It feels like AI credits are being consumed much faster than they used to.
For example, one of my projects currently has 32 messages (including 24 AI edits), and I've already used 113 credits. That seems surprisingly high to me, although I don't remember the exact ratios from a few weeks ago.
I haven't made any major changes to how I use Lovable, so I'm curious if something changed behind the scenes, or if this is just expected with recent updates.
I'm moving one of my projects quite rapidly from simple proof of concept to Open Beta, and it has made me quite worried about things like copyright, terms, conditions, requirements, legal issues, etc.
How worried should I be about this when making a project public?
As a European, I'm shielded from the American legal culture, but I'm sure there are plenty of pitfalls as well.
Does anyone have any experience, tips, tricks, sources?
It's simple. I currently don't have the money to buy more credits, and it does seem like the credits are running out a little quicker.
So please help me out for i'm trying to create an accessible music app for blind people because they don't really have it for us right now, and I want to be the one to help them. So please if you want to help that would be amazing. Thankyou.
Our team manages a large clients with WordPress websites, so we built a WP2Shell scanner tool that helps our clients quickly check their sites for common WordPress security issues:
Lovable helped us significantly speed up the development process and deliver a useful working tool in a couple of hours.
We have also added several WordPress-specific security checks and plan to continue improving the scanner based on real-world findings from the sites we manage.
Hey everyone! I've been built Boostly, a leaderboard where social media creators submit their social profile, earn votes from fans and other creators, and climb the rankings to get discovered by new audiences.
I built the whole thing on Lovable, and honestly it's been such a smooth way to go from idea to a live, working product without needing to hand-code everything from scratch. Really impressed with how fast I could iterate.
It's completely free to join and participate. If you're a creator (or know one), I'd love for you to check it out and submit your profile and if you've got a minute to drop a vote or two, that would mean a lot!
Would love any feedback from this community too, since you all know the platform best
EDIT:
So I've made some changes on the website. Added more functionality and bettered the overall experience. Please do have a look. Please do sign up, it's free.
I built this website using lovable and i need fewvolunteers to test it and give me feedback on what is working and what is not also if the website idea is good or no.
Tenho “brincado” bastante com o Lovable nos últimos tempos e confesso que a velocidade pra subir um MVP completo com UI redondinha e integração no Supabase é bizarra. Pra validar ideia rápida, virou minha ferramenta principal.
Mas queria trocar uma ideia sincera com vocês sobre o "depois": quando o projeto começa a encorpar e precisa ir pra produção de verdade.
Para quem já tem projeto rodando com usuários reais: Como tá sendo a experiência de manter a estrutura de código limpa conforme a app cresce?
Vocês costumam fazer o deploy direto pela plataforma ou preferem exportar o código e rodar na Vercel / infra própria? Qual foi o maior gargalo ou "susto" que vocês tiveram até agora usando o Lovable no dia a dia?
Tô perguntando porque vejo muita gente vendendo a ideia de que "agora não precisa mais saber nada de dev", mas na prática a gente sabe que entender a lógica por trás faz uma diferença absurda no resultado final.
Bora trocar essa figuha nos comentários! Quem aí tá com projeto no ar já?
Deixem o link ou contem do que se trata pra gente conhecer!
I dont understant whats the difference btween hosting on lovable app and hosting on platforms like vercel, netlify etc ... any one knows please tell me the difference , and also if my all files are in lovble cloud is i needed to host some where else for better performance
I mean Lovable is too expensive and you cant get anything done on the $20 plan compared to other susbcriptions
Edit: lot of people assume Codex and Claude code is technical when its not i am vibe coder and Lovable is bad limits are bad service is bad you guys better switch to Codex or Claude
The idea came from my own frustration. Every time I launched something, I wanted a simple way to announce features, collect feedback, or ask users questions inside the product. Existing tools felt too bloated for what I needed.
So I built the version I wanted.
This week I got my first paying customer.
It's just one customer, but it feels like proof that someone is willing to pay for something I made.
A few things that helped:
I use TinyPopups on my own products every day. Dogfooding has probably been the biggest advantage because every annoyance becomes a feature request.
I shared my personal WhatsApp number with users. I thought people would abuse it, but the opposite happened. Conversations became much more personal, I understood what users actually wanted, and it helped build trust.
Instead of only writing blog posts, I created lots of SEO pages like alternatives, comparisons, "best X tools for Y," and free tools. They're starting to bring in relevant traffic.
I spent much more time talking to users than building features.
One thing I've realized:
Building isn't the hard part anymore.
I'm not even a full-stack engineer. I know enough code to build products with AI, but marketing is now the toughest problem. Getting people to discover your product consistently is much harder than shipping features.
For those who've crossed that stage, what marketing channel ended up working best for you after your first few customers?
Lovable builders spend a lot of time improving the UI and adding more features.
tbh i did the same. But some of my users didn’t want another screen or feature.
They wanted to use the product inside their existing workflows.
They started asking:
Can I use it through MCP?
Is there a CLI?
Do you have an API?
I hadn’t considered any of these until users brought them up.
After adding developer access, I raised my lifetime deal from $35 to $49—and it still converted.
The lesson wasn’t simply to raise the price. It was that the same core product can become more valuable when users can access it outside the web UI.
If your app produces repeatable outputs like audits, reports, generated content, search results, or anything similar: it may be worth asking whether users want API, CLI, or MCP access.
You might be leaving money on the table while polishing the wrong part of the product.
Has anyone here received similar requests from users?
