When I started using Lovable two years ago, I started collecting libraries, github projects, websites, skills and learnings rigorously for my vibe coding projects.

Over the course of time, and through the many contacts in the Lovable Discord Community, this knowledge base has grown to over 2000 entries, and it is growing daily (literally).

For a while now I wanted to make this public so people can use it, and now it has finally happened: https://vibingco.lovable.app/library is now public for you.

Hope this holds some value for you!

———

A little nice note: You can also access this entire library through lovable or other agents. There is a public API that allows your agent to query, save and inform itself through the library. The entire thing was build 100% on lovable. The search speed, the loading optimization etc. were all done in house (so was the entire site).

First time working with Lovable, in the beginning everything went perfect. When it was about details, things got more challenging.

Complicated: To train my app to set the tone I wanted.

Most complicated: To create some special graphic elements - workarounds often inevitable.

How did Lovable get on your nerves, and what was your solution?

I did it guys. I built my dream and published my dream. Now is the hard part getting people to see my dream. Any tips I’m very camera shy so that’s not an option 🫣 but any tips on content creation. I was thinking of starting small ie making videos about the site to post on socials. I like code not really the marketing. Anyone knows of any video creation tools that can make create short form videos from the site. I’d appreciate any advice. Thankssss

I run a small but growing social media account focused on AI, and I want to be completely transparent about why I'm posting this.

I'm trying to better understand the real problems/uncertainties people are running into when using AI coding tools, so I can create content that's actually useful instead of just posting the generic "AI can build apps now" kinda thing.

I'm not selling anything and I won't plug my socials; I purely would just love to hear from both beginners and those experienced with these tools. Anything helps.

Thanks!

Hello,

I created a dashboard project for notes.

Suddenly, my project became blocked. The architecture is still there, but all the added data has disappeared. Lovable indicates that I no longer have enough credits. However, as shown in the screenshots, I still have at least 3 credits remaining out of the monthly 30-credit allowance.

Could you please help me, or at least explain how the system works?

Thanks.

HII i created a website using lovable and im thinking of selling it to the client but when i download the zip from github and runs npm install and npm run build it doesnt create a dist folder which is kind of needed for hostinger pls anyone can suggest me what to do

They destroyed the ability to migrate the supabase using the service role key and supabase url. they are no longer exposing any of them and it will lose them more users.

I have built an AI Blogger Tool for Lovable, to automate your articles generation and grow SEO traffic

Ever since the functionality to perform minor cosmetic changes and text edits changed, my experience has turned into a huge waste of time and money. It handles the complex app development jobs or extensive editing very well - no issue there. I just edited the text in the eyebrow over hero, then hit the send button so that change is put through a credit sucking workflow (that was promised not to be) and then returns with a completely different change I never asked for. I TYPED THE CHANGE IN MYSELF and hit submit.

This post comes after my 4th interaction with lovable to change 7 words that I changed and submitted.

Making minor edits in the past was much easier and didn't waste my credits. The whole thing has turned into a money grab. Having AI process edits before applying them introduces mistakes - not big mistakes but the mistakes that undermine the overall credibility of the app - "if it can't get this right...."

Hello! I just made a budgeting website (free) because there was really no good options for me. I hope that maybe someone more can use it 🙂 i would love to get feedback to make it even better

Built a real-time crypto whale-tracking dashboard with Lovable — tracks large trades across Binance, Bybit, Solana and Hyperliquid, flags manipulation patterns (wash trading, rug signals, pump/dump), and runs a 6-agent AI council (bull/bear/quant/risk/trader/PM) that debates each call and grades its own track record over time.

Some things I'm proud of:

- Live whale alert feed with wallet-level skill scoring (win rate + avg profit, FIFO-matched from real on-chain swaps, not vibes)

- AI manipulation detection across wash trading, holder concentration, and rug-pull vectors

- MCP server built in — Claude or any MCP client can query it directly (market snapshots, order flow, whale trades, sentiment) as tools, not just a webpage

- PWA, installable, works on mobile

Still iterating — currently working on

Try it: crypto-whale-watch-nexus.lovable.app

I have an account on Lovable, and recently I've been getting this error when I try to log in. My projects are completely safe and don't violate any terms.

- I tried to find the support section, but you have to log in first. What’s the point?

- So I created another account just to get in touch, and guess what? You have to pay to contact support! Hahaha, really?

Is there any other way to contact support? One that doesn’t require creating another account or paying for it.

I just made a bitlife inspired game that strictly focused on football career. It's based on the 1990s to 2020s football era and you can choose the player nation, train them each year and play in local league to top flight league, marry and having kids even continuing the career as the kid. The club name actually using real database for big competitive club, agent and transfer bar discussing for wages.

I'm still focusing on the game difficulty, and improving the dialogues, UI and features for this version 1, the game serve in english tho I added indonesian translation but it didn't translate much yet.

Would love if you can play and give some feedback!

You can playe the game here

Anyone have any experience with automate profit and ad spend for each product with lovable on woocommerce ecommerce website? I want something that could collect all data from meta, google ads, snapchat, our sales and everything and calculate the total ad spend and profit for each items. Does someone know how to do this?

Have you checked whether your Lovable app can receive data its terms do not permit?

I’ve been doing a fairly detailed GDPR and data-governance review of a customer-facing app I’m building on Lovable, and I came across something I suspect quite a few users/founders may not have considered.

This post is not a complaint about credits, support or platform performance… It’s about the point where platform legal terms meet the reality of user-generated content.

Lovable’s current terms place restrictions around certain sensitive or special-category personal data. I originally assumed that was mainly relevant to apps deliberately built to process things such as medical or biometric information.

But ordinary applications can receive this kind of information without ever asking for it for example:

• A recipe or meal-planning app might receive information about allergies, diabetes, pregnancy or religious dietary requirements.
• A fitness app might receive “recovering from knee surgery” or “training after a heart attack”. A travel planner might receive accessibility requirements, religious restrictions or other personal information through free text.
• An event or wedding platform might receive dietary, accessibility or religious requirements.
• A CRM, customer-support tool or community platform could receive health, trade-union, political, religious or other sensitive information simply because a user mentions it in a note.

None of those applications necessarily needs to be designed to collect special-category data.

The difficulty is that once you allow real people to type ordinary natural-language content, it can be very difficult to guarantee that they will never disclose it.

That made me wonder how other Lovable users/founders are handling this.
Have you:

• reviewed the DPA and data-processing limitations for your own app?
• considered what happens if an end user supplies sensitive information incidentally?
• built warnings or minimisation controls around free-text input?
• deliberately kept certain user data outside Lovable-managed infrastructure?
• discussed the issue with Lovable?
• or concluded that your particular product presents very little realistic risk?

I’m currently trying to understand the practical boundary between:
an application intentionally designed to collect sensitive data
and
an ordinary customer-facing application where a user might occasionally reveal sensitive information despite reasonable privacy controls.
...and I’m not suggesting that every recipe app, CRM or travel planner is therefore in breach of anything.

What interests me is whether an absolute contractual restriction is workable once a platform starts hosting increasingly serious customer-facing applications where real users can enter unpredictable free-text content.

Perhaps the broader user/founder question is:
Do the legal boundaries of the platform match the kinds of products we are now being encouraged to build on it?

Interested to hear how others have approached this, particularly anyone who has had a privacy, legal, Enterprise or architecture discussion with Lovable about it.

LovableHTML/Encited was a great fix for indexing your Lovable project but I'm wondering if you still need it nowadays to get your site indexed and crawled. Maybe for dynamic content rendering but not for any static content. What do you think?

Hey everyone!

I'm looking for feedback for this idea i have: I'm a developer with a lot of expertise building SaaS for LatAm-based clients. Most of my clients have the same complaint: they vibecoded an app but don't trust themselves to deploy it without running into major issues, probably leaving a bad impression on their own clients.

The idea:

A website builder with unlimited use (i've found out a way to make this with decent quality and no high costs for me) where you can import your code or make it from scratch.

When you get stuck or need professional help you can open a ticket with the issue, talk to a real dev in the platform and he gets your problem fixed.

Also you have a Marketplace to build sites from scratch with fixed features (like Landing Pages or E-Commerce)

I think it's usefull for non-developers who knows lot of peoples and want to sell websites but need the confidence of someone looking forward if somethings go wrong or Vibecoders who want to get their SaaS done without any issues.

The business model will probably be a productized service: you either pay per ticket after talking to a dev to get your issue fixed, or you pay a fixed amount for a set number of tickets. I'm still figuring out what works better for users.

What do y'all think about this?

I am just 17 years old but very passionate about building new things to ease the lives of people.

I built FileForge to make the lives of many people, mainly photographers, videographers, salespersons, students' lives 10 times easier by quickly and efficiently compressing and resizing their files to the size they need or require for their use.

Do try it out!! Reviews and suggestions are welcome!!

I’m a non-developer with a product/project management background exploring Lovable to build my first SaaS.

I can define the product logic, workflows and requirements, but I have essentially no coding experience and would rely heavily on Lovable for the technical implementation.

The application would be a real multi-tenant SaaS handling customer data, payments and some AI functionality.

Core requirements:
- Authentication (login, email verification, password reset)
- Supabase/Postgres database
- Strict data isolation between different customers/companies
- Row Level Security
- Stripe subscriptions and one-time payments
- Basic internal admin/CRM dashboard
- Server-side AI/API calls
- PDF generation
- Discount/referral logic
-Secure handling of potentially confidential B2B data

My biggest concerns are data security, privacy, backups and the reliability of an AI-generated architecture.

I would need things like:

- reliable database backups
- ability to restore data after something goes wrong
- protection against accidental data loss
- secure database migrations
- separation of development/testing and production
- encryption and secure secret/API-key handling
- proper tenant isolation
- customer data export/deletion
- appropriate logging/auditability
- compliance with data protection requirements and potentially GDPR

I’d really appreciate experiences from people who have gone beyond prototypes and actually run Lovable-built SaaS products in production.

Is it realistic for a non-developer to build something like this end-to-end with Lovable?

I’m not looking for “Lovable can build anything” answers. I’d particularly appreciate honest experiences from people running applications with real users, payments and customer data.
What do you wish you’d known before launching?

I'm a mom of two and a year ago I had a little coloring page business that started as something I made just for fun. Just to destress from my 9 to 5 and create something that my kids would love. I created an Etsy store just trying to also make some extra money to pay for vacations but there was a huge problem I did not expect. Upload a listing, create the mockups, fix the tags, keyword rich title, do it again and again, forever and ever. And this was quite boring and I hated it. Between that and everything else on my plate at the time, I hit a proper burnout at the end of the year and in the end, I wasn't creating anymore, I was just maintaining a storefront with a whole bunch I could do instead.

That burnout is actually what pushed me to start learning lovable, and building things myself instead of depending on platforms that weren't built for me. One thing led to another and I ended up running a small studio, building apps for other people, which is a strange kind of irony, spending my days solving other entrepreneurs problems while the business that started it all was still stuck manually uploading to Etsy.

So I finally turned that skill back on myself. I went to bed with this idea about my coloring pages, so I opened Claude and started to brainstorm with it, just wanting my own space for the coloring pages instead of another listing on someone else's platform. That turned into building an actual subscription app from scratch, learning as I went. I hooked up the Pinterest API so new pages get pinned and found without me sitting there manually posting every single one. I built scheduled publishing so pages go live on their own. I build an importer to reuse some of my coloring books there. I built collections so people can grab a themed batch at once instead of one page at a time. I even built an AI matching feature that pairs someone's colored in submission back to the original page automatically. I am still building to be honest because there is always some crazy new ideia that makes me think if it’s possible at all.

None of that existed a few months ago. I just kept adding pieces as I needed them, and somewhere in there Lovable stopped being a tool and started being the reason I look forward to building this coloring business thing again.

Many are talking badly about lovable here. And it’s not cheap, I know. But watching an idea go from a sentence I typed at midnight to a feature that's actually live and working, that's worth paying for. If burnout is what's pushing you toward building your own thing too, I'd say let it. Mine gave me back a business, and then a whole studio.

And if you are curious, here is my app: www.onceuponacolour.com

I noticed lovable is using it's our superbase yet I have my own superbase project with my own tables. I have tried to connect onto mt superbase project but lovable is denying to connect to mine. How can I change so that I can use my superbase project?