Hey guys, I created a virtual fortune reading website via AI lovable and would like to get some feedback to enhance the site. Do try out the 1 free full reading and compatibility reading per month using the link provided. Share with me your feedback so that I can make improvement to the site. Thanks in advance.

Hi everyone. It is abundantly clear that SaaS as we know is being disrupted. Everyone is becoming headless (e.g., Salesforce, Notion, etc). Why are YOU wasting time, money, and energy by building a SaaS that won't bring you money? Why not build agents? My two cents... don't be a bag holder. Silicon Valley has moved on to agents.

Hi! I've been working on a small website called DateTips lately, where the goal is to make it a little easier to find things to do on a date. I am based in Oslo, wo as of now, its only for Oslo, Norway.

The idea is quite simple: Instead of sitting and googling "things to do in Oslo" every time you need to find something, you can go in and get suggestions for different types of dates - restaurants, activities, creative things, outdoor activities, etc, based on your preference.

I've now launched a first version, and would really appreciate honest feedback from people here.

👉🏿 Datetips.no

What I'm particularly wondering about:

Does the website look useful?

Is it easy to understand what the site is for?

Would you actually use such a site when planning a date? What would make you come back to the site?

I'm not just looking for "looks good" comments - feel free to give me criticism too. I'm trying to figure out if this actually solves a problem or if I just made something I think is cool.

Thanks!

Please delete if this doesn't fit, i wasn't sure what flair this should go under.

Ok so recently, I've had a lot of trouble marketing my app. TLDR; it's an AI agent called NeoNexus, no third-party API's, own engine, but I want to start making money and it's hard for me to see users actually wanting a subscription. How do I do it. In case you guys can help, https://neonex.lovable.app/ is the URL. Thanks.

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

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?

Hey guys! Built this app cause I was struggling with keeping up with my daily routine and life but a habit tracker doesn’t tell me why my days keep falling apart… it doesn’t help me understand where things got away from me or what habits are keeping me in the loop… stillcloud.lovable.app is the answer to that problem. I tell it my day, it finds the patterns and gives me one way to interrupt it…

After so many people provided feedback on the app and the language, I wanted to do one more showcase of the latest version to hear what everyone thinks.

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.

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

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!

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...."

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

Why does Lovable all of a sudden take up so many credits, I got a 100 credit plan ran out in a day, I got a 200 credit plan, ran out in that same day. I think it’s all because of agents eating credits like they are breakfast. Why do you think so? Please give tips on how to lower daily credit usage.

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.

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?

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.