近 7 天 · 编程与应用搭建
Lovable
从想法到应用与交互原型
体感分37.6/10038 条评论
来源 全部
大家怎么看
近 7 天的 38 条评论中,整体体验偏负面。批评最集中在「价格与额度」(12/24 条负面摘录)。好评最集中在「工作流与集成」(5/12 条正面摘录)。有用户表示结合Lovable、Codex、ChatGPT和Codemagic,已成功从Lovable发布了两款应用。有用户因Lovable生成的低效Supabase认证查询,使其仅有几百行记录的数据库性能表现却像查询几十万行。
用户反馈
29 条评价摘录
展开原文
I used a combination of Lovsble, Codex, ChstGPT and codemagic and have published two apps from Lovable so far.
展开原文
keep shopify as the backend and just hit their storefront api from lovable. trying to rebuild carts, checkout, and inventory tracking yourself is a massive headache when shopify's headless setup handles all of it out of the box.
展开原文
So I always say Lovable for development/testing only. Code on Github. Selfhost on a vps for launch if you know how or Vercel/Supabase Cloud if you dont.
展开原文
Therein lies the problem as Lovable has written an auth loop into my code before too. Also Lovable loves writing very inefficient supabase queries to do with Auth stuff. However, you won't know that unless you use Supabase cloud/selfhost - the Supabase advisor says how badly they perform but Lovable cloud doesn't have that feature.
展开原文
Most people don't know about the usage/hosting charges as accounts have a certain amount free. I had a site with a few hundred rows in a db but it was performing like I was querying a couple of hundred thousand all because of those bad queries. Also the three days of test only traffic was eating 3 credits a day so anything after launch was going to be horrific.
查看评论上下文
问题就在于此,因为Lovable之前也在我的代码中写过auth循环。另外Lovable喜欢写非常低效的Supabase查询来处理Auth相关的事情。
机器翻译展开原文
Therein lies the problem as Lovable has written an auth loop into my code before too. Also Lovable loves writing very inefficient supabase queries to do with Auth stuff.
展开原文
I had a site with a few hundred rows in a db but it was performing like I was querying a couple of hundred thousand all because of those bad queries.
查看评论上下文
另外Lovable喜欢写非常低效的Supabase查询来处理Auth相关的事情。
机器翻译展开原文
Also Lovable loves writing very inefficient supabase queries to do with Auth stuff.
展开原文
I'm just saying it so people don't consider Lovable as more than a development platform. Too many posts on here where they reach the find out phase (costs/migration pain/Lovable ToS/whatever).
展开原文
Lovable hosting is not free and if you scale in any way it will wreck you in costs.
展开原文
Also, Vercel free tier prohibits commercial use, which rarely is an issue as most projects have to pay the $20 subscription due to practical limits.
展开原文
But you can't say Vercel has the same offering as Lovable compared to cyber security and ease of us.
展开原文
But you can't say Vercel has the same offering as Lovable compared to cyber security and ease of us. Basically everything that a non technical person needs.
查看评论上下文
Vercel 有免费套餐,作为托管商它能做 Lovable 能做的一切,甚至更多。如果你只是想要一个托管服务,根本没有理由为 Lovable 付费,尤其是如果你已经在同步到 GitHub 并在 Lovable 之外开发的话。你在为本来可以免费获得的东西付费。
机器翻译展开原文
Vercel has a free tier and does everything lovable does as a host, plus much more. There is simply no reason to pay for a lovable if all you want is a host, especially if you're already syncing to GitHub and developing outside of lovable. You're paying for something you could get for free.
展开原文
They should pay $500 on Lovable as its a small cost to what the opportunity cost would be developing a "scalable" solution 😆 Another exaggerated example sure
展开原文
My advice is for non-technical people using lovable with the plan to sell apps or release paid services to immediately start gaining the knowledge of what lovable is doing and what they should do with the code to host it properly.
展开原文
All the data I keep it in BigQuery and avoid using Lovable Cloud, because credits burn now after the changed it.
展开原文
I don’t get why everyone hates on Lovable for hosting tbh. Granted, the apps I’ve built for businesses tend to max out at about 60 concurrent users each, so hardly load, but I’ve never really had an issue?
展开原文
If you use Chrome extensions that abuse the Lovable credit system to bypass what you usually pay for, this is breaking the terms of service of Lovable. You risk your workspace being removed indefinitely, along with all the projects that were remixed in the workspace, and that originated in the workspace. Further, Chrome extensions like these usually track every message you send and try to fish for API keys, credentials, and personal information. If you utilize extensions, your account and workspaces will be compromised.
展开原文
And no one with any sense would pay anyone $799 for a vibe-coded AI crap website.
查看评论上下文
我还设置了 Stripe 用于收款,所以我计划前期收费 799 美元,外加每月 99 美元的“运营”网站费用,并包含免费迭代。
机器翻译展开原文
I also setup stripe for payments so I plan to have an upfront cost of $799 with a $99 monthly fee for "running" the website along with free iterations.
展开原文
Lovable is really convenient as a cloud service, especially when you have a lot of small or medium-sized projects
展开原文
DON'T host it on lovable!!! This is where you need to start learning more about web development. Especially around properly hosting websites. Lovable will get you in some serious jams if there's high traffic or resources used. You can't afford for a paid site to go down. Best thing to do is host it on their current platform or find a proper web host or vps or cloud for them to host on and don't take on hosting responsibility.
展开原文
It can deploy your code to Cloudflare (free) as well as to Supabase (free), while committing all of the code to Github.
查看评论上下文
Claude 无法通过一个提示词来处理托管、域名、数据库、认证、邮件发送、定时任务等。还是说我遗漏了什么?
机器翻译展开原文
Claude does not handle hosting, domains, database, auth, email delivery, cron jobs etc with one prompt. Or am I missing something?
展开原文
This is something lovable is better at.
查看评论上下文
不过,Codex在大型项目中很快就会变得非常沉重。必须不断编写“交接”文档并开启新的对话。
机器翻译展开原文
Codex gets really weighted down quickly though in large projects. Have to write continuous "hand off" documents and start a new chat.
展开原文
although there are better hosting platforms to use (Vercel for example) than Lovable since they are optimizing toward different customers
展开原文
I spend 1500+ credits to explore it (about 400 euro for one month), so I satisfied, but I wanted to find cheaper way to develop instead.
展开原文
the frontend export is usually easy since it's just standard react
展开原文
but dealing with the supabase side is where it gets annoying. untangling generated rls policies and getting all the edge functions running cleanly in your own environment usually takes the most manual cleanup.
展开原文
zero control
查看评论上下文
事实上,我已经不再考虑使用Lovable或任何类似Lovable的工具进行开发,因为它们实际上是在以非常高的加价转售token。 Claude code/Codex几乎什么都能做,那为什么还要花高价通过同样的模型用Lovable来完成任务,而且毫无控制权呢?
机器翻译展开原文
As a matter of fact, I have stopped considering Lovable or any Lovable like tools for development because they are effectively re-selling tokens at a very high markup. Claude code/Codex can do just anything so why pay for Lovable to get something done through the same models at a very high prices and zero control?
展开原文
they are effectively re-selling tokens at a very high markup
查看评论上下文
事实上,我已经不再考虑使用Lovable或任何类似Lovable的工具进行开发,因为它们实际上是在以非常高的加价转售token。
机器翻译展开原文
As a matter of fact, I have stopped considering Lovable or any Lovable like tools for development because they are effectively re-selling tokens at a very high markup.
展开原文
Lovable like tools can be a good start for someone who has zero technical knowledge
展开原文
But its not 100% working. If you do changes with chatgpt and then publish but after that if you changes with lovable it will break the design or code.
展开原文
It's also really easy to start with an architecture that makes future changes really hard. When you look at the code there's duplicated logic everywhere so the longer you build the worse it gets.
展开原文
It’s all a hidden credit sink as the transparency from them is gross
展开原文
lovable is just giving you access to cheaper models for a higher price and providing alot less value to you as a consumer
展开原文
Que merda parem de usar lovable , porra o Claude code agora está igual e melhor via web via desktop ou via cli e com habilidades superiores
展开原文
Every time a user goes through the site, it's this problem or that problem. Almost like for every bug or problem that is fixed, another one is created.
展开原文
it's good for small scale projects, but you shouldn't use it for large scale projects.
展开原文
Yup, it now seems to have gone X 3 credits. I'm bowing out over next few months, it's been fun.
查看评论上下文
之前,如果你让Lovable删除一段普通文本,它最多会花费0.6个积分。 现在,删除一段普通文本最少需要2.10个积分。
机器翻译展开原文
Previously, if you asked Lovable to delete a normal text, it'd spend maximum 0.6 credits to do that. Now, it costs minimum 2.10 credits to delete a normal text.
展开原文
no hate for lovable, its just that i dont like to depend on single application for complete development
展开原文
using lovable for frontend is good
展开原文
canceling the Lovable sub helped a lot
展开原文
Never understood the need for something like lovable when I can just use Claude code or antigravity to build what I need and host it on vercel or something similar.
展开原文
I first started Travi, I did it on Lovable, quickly hit a wall in terms of functionality
展开原文
both are an hour to fix, and both are invisible from inside the lovable editor.
查看评论上下文
那个没人列出但应该列出的:没有隐私政策。
机器翻译展开原文
the one nobody lists but should: no privacy policy.
可怕的技术问题是 supabase 表可以用公共匿名密钥读取,在同一批次中发现了 6 个这样的问题。
机器翻译展开原文
the scary technical one is supabase tables readable with the public anon key, found 6 of those across the same batch.
展开原文
the scary technical one is supabase tables readable with the public anon key, found 6 of those across the same batch. both are an hour to fix, and both are invisible from inside the lovable editor.
展开原文
The important thing is your hosting platform for the website ahead of time so it's not hosted on lovable if you ever want to move off of it
展开原文
you can stop paying for lovable and use the 5 free credits for small daily changes
展开原文
I think using these intensively has really helped with my confidence level re the basic stack I'm using.
查看评论上下文
目前,我依赖我的测试用户。我密集使用我的两个应用——一个记录我一个赛季的所有比赛,另一个是队长应用,用来记录我团队的表现。
机器翻译展开原文
For now, I'm relying on my test users. I use 2 of my apps really intensively - one records all my matches over a season, the other is a captains app so I record the performance of my team.
展开原文
I know there is a lovable feature that can monitor your apps but there is a cost and I need to get some more paying customers first.
展开原文
Now I think Lovable is only decent for people who really know NOTHING about IT, I think there's still a market, just less.
展开原文
sometimes it uses all daily tokens just to even read file … before even making any changes
展开原文
Getting another customer's response is a very very serious security issue from my point of view
此筛选下暂无评价。