Lovable on X

Praise is the bulk of the talk, and much of it is show-and-tell: portfolio sites, client dashboards, hobby projects, a hackathon try, a community app built with @Lovable and ChatGPT. One owner who moved a GoDaddy landing page across says "the results are amazing", and replies call the difference night and day. An agency says it became a Lovable Certified Solutions Partner and relaunched its own site on it, while a returning user found the same long prompt that took a multi-step build six months ago now lands in one shot. One user's count of asking ChatGPT which AI app builder to use found Lovable named in 97 of 100 answers and listed first in 67.

Speed is a smaller strand (7 people): a site prompted in about two hours, a chat mode that saved two weeks of work, a platform that felt faster one evening. On one October thread 4 people call it enterprise-ready, citing EU inference failing closed and running in its own cloud. The 8 disappointed or skeptical call it a wrapper, ask when it stopped being a vibe coding tool, and doubt built apps outlive 30 days.

The biggest group, bugs and broken UI (6 people), is a list of snags rather than one failure: "Invalid Token" in preview that a shift-refresh only temporarily fixes, desktop tabs that disappear, a Figma MCP connection that won't connect or be deleted, credits hidden behind an upgrade banner, and a build that came out themed like the backrooms.

Lock-in and handoff (5) and price and top-ups (5) are level behind it. On handoff, people say connect GitHub first so you own the code, and that HubSpot rebuilds React into its own templates and form fields get lost; without an export, "you're renting your site". On price, one user asks the company to reconsider a top-up that went from $.15 to $.30 and says they may take the site off; others mention invoices and thousands of dollars sunk into projects.

Accounts and access draw the sharpest posts: a hacked account with credits being drained, a login disabled, a production app down with only automated replies. Security worries are a separate small group: a 2025 scan of 1,645 Lovable apps where about 170 had database tables anyone could read.

The comparisons read as per-person workflow decisions rather than head-to-head picks. One owner replaced a GoDaddy Website Builder landing page with a Lovable one, and a reply in the thread called the difference "night and day"; the same thread drew someone who sticks with Generate Press starter sites because they don't want another subscription. In the other direction, users take the finished app somewhere else to keep working: one says they're going to "let claude iterate" on a build they rate as quality work for 30 credits, another is moving a Lovable web app to Modaal to rebuild it as a native mobile app.

Handoff is where comparisons turn practical. A user waiting to move a site into HubSpot is warned that HubSpot won't take the React code as is — it rebuilds it as templates, and the form fields are the part people lose. Replit and Bolt come up once each, one user taking Lovable or Bolt for a first iteration. A single user weighs PeachJam, which they say is x6 cheaper per token.

Games and music (4 people) followed a game built on it: can it make games, can it do custom sound effects on a button click, is the soundtrack made at build time or generated live. One user asks where the sounds are sourced, saying the answer could stop them using the service.

What a Cloudflare move involves is 5 posts from 2 people. One of them works through an announcement: whether it plays with Payload CMS on Workers and D1, the Lighthouse and PageSpeed gains, links to plugins and docs, and whether costs rise or the Workers paid plan stays the same. The other reads the choice as runtime first, framework second: "TanStack Start fits a Worker; Next.js assumes it's running on Vercel."

Publishing and keeping the code is asked as a how-to: how a first page goes live, and whether the project can be pushed to GitHub to finish elsewhere. Two people ask whether adding features breaks what already worked — one whether the browser QA retests earlier features after each update. The rest are one-off asks: how many credits a build takes, whether built sites leak Supabase tables or keys, whether the 70 million apps figure includes apps never opened, and what the partner programme involves.

The requests are unconnected, one person each. One user asks the company to let Perplexity drive Lovable over MCP. Another, replying to a product post, asks for "organic social post creation, scheduling, and auto posting to all channels". A third, in a conversation about recovering from a failed fix loop, suggests putting the last passing commit hash into the one-line brief so a fresh session starts from a known-good place.

Nothing here repeats, and none of the three shows anyone else agreeing, so the section says only what each person asked for. On this evidence the page can record the asks but not a demand.