Lovable

Users are inquiring about the capability of Lovable to manage multiple domains under a single project, given the subscription limit on the number of projects. This is relevant as it affects the usability and flexibility of the platform for users with multiple websites. 'can Lovable manage it under one project?

The user is currently using Lovable to build their website but wants to transition away from AI-generated code due to limitations and concerns about understanding the mechanics behind their site. They're seeking guidance on what skills they need to acquire to take over their site's development, citing SQL, HTML, CSS, and JavaScript as areas they need to learn. 'I want to understand the mechanics behind my site. and I don't want to be under fire for using ai.',

Users are reporting that the cost of using Lovable is prohibitively expensive for everyday use, making it inaccessible to the masses. This is a significant concern as it limits the product's adoption and usability. As one user puts it, 'Dom flesta har inte råd att betala för mjukvara lissom' ('Most people cannot afford to pay for software like this').

Users are reporting difficulties with credit limits, which is hindering their ability to use the product effectively. This issue is significant as it affects the overall user experience and productivity. As one user stated, 'some help with @Lovable credits could be pretty usable during this time

Users are finding that Lovable's AI builder can produce sites with similar designs due to the reuse of UI libraries, and are suggesting a designer marketplace for custom kits and templates to increase visual diversity. 'Lovable is great for speed, but detailed briefs can expose design limits.

Users are seeking more reliable AI models that can be trusted with real projects, emphasizing the need for stable performance, continuous availability, and monitoring capabilities. As one user notes, '模型能力不是上线一次就完事，稳定回归、持续可用、能被监控，才会让人敢把真实项目交给它。

Users are reporting that the Lovable iOS app freezes repeatedly during the building process, requiring force closure to restart. This issue is frustrating and hinders the app's usability, as one user stated: 'it froze 20+ times and required me to force close to try again.

Users are reporting that they cannot invoke the new model in their chat, as there is no option to designate which model to use, limiting their ability to utilize the full functionality of the app. This is a significant issue as it hinders the user experience and creativity. 'there is no option to designate which model to use

Users are reporting that the Lovable website is inaccessible, which may hinder their ability to create or manage their web apps and websites. This outage could impact their productivity and overall experience with the platform. As one user asked, 'Is your website still down?

Users are reporting difficulties with paying for Lovable services due to credit card issues, which hinders their ability to use the platform. This is a significant problem as it affects the user's experience and the company's revenue. As one user stated: 'can't pay, my card doesn't work for lovable :(

Users are experiencing issues with credits being deducted for centering icons and chats getting stuck in loops, causing frustration and disrupting the app-building process. '8 credits to centre icons, chats that went in loops, please fix

Users are reporting that Lovable.dev's new credits-combined system is consuming hundreds of credits for inactive projects with zero users or activity, despite having a pro plan with a limited number of credits. This issue is causing frustration and mistrust among users, who feel that the platform is overcharging them for credits they don't use. As one user stated, 'Lovable team needs to hit their “REVERT” button and go back a few stages and maybe then people could still find reason to use LOVABLE.dev',

Users are reporting that forms generated by Lovable have nowhere to submit data to, requiring manual setup of serverless functions and email services. This is a frustrating and time-consuming process, as evidenced by the creator of FormBnB who built their product to solve this issue: 'the AI generated a gorgeous contact form in seconds... that submitted to nothing.

Users are worried about being the single point of failure with Lovable, and the potential difficulty in migrating sites if issues arise with their account or billing, as evidenced by the mention: 'If my account, billing, or access has issues, multiple client sites could be affected.

Users are seeking guidance on optimizing their blog posts for SEO using Lovable, specifically regarding image alt text and meta descriptions. They want to know if Lovable's automatic renaming of file names affects SEO and if they should specify meta descriptions or let search engines decide. 'is it a risk to ask it to follow it exactly?

Users are reporting frustration with the AI suggesting multiple possible fixes, leading to a loop of trial and error, making it difficult to identify the root cause of the issue. This wastes their time and hinders the development process. 'The hardest part becomes understanding the real root cause.

Users are reporting that AI-generated code, specifically from Lovable, contains security vulnerabilities such as leaked Supabase service keys and hardcoded secrets. This is a significant issue as it can lead to security breaches and data exposure. As the developer of CodeInspectus notes, 'AI writes code that *works* — and quietly leaks Supabase service keys into the browser bundle, trusts user_metadata for admin checks, ships USING (true) RLS policies, hardcodes secrets.

Users are reporting being banned from posting on the r/Lovable subreddit without clear reason, potentially hindering community engagement and discussion. This issue matters as it may deter users from participating in the community, as one user warns others to 'beware of this my fellow vibe-coders'.