What engineering leaders and their teams report about Lovable, with every finding tied to its evidence.
Read the findingsPractitioner sentiment, leaders and teams
+27 Positive from 30 sources that take a side
How this figure is madeFrom 30 authors in 26 discussions. Run a pilot build to measure how much of the generated app ships without hand-written fixes.
Jan 2025 to Oct 2026.
110 sources from practitioners, by month and sentiment.
Teams and leaders mostly use Lovable to put a working prototype in front of stakeholders or build an internal tool. 8 of the 30 team and leadership sources describe this. Of the 8 who say where the code ends up, 5 keep Lovable to prototypes. The concerns raised most are fixes that break other parts of an app (6 of 7) and gaps that surface once real users arrive (6 of 6).
Positive, mixed and negative sources
The score counts each source once, as the split does. See How the numbers work.
See the evidenceBelow: 4 praise themes, 3 concerns, 4 points of agreement and 1 disagreement.
Counted for Engineering leaders and teams, from 30 sources. Change group
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
Counted for Engineering leaders and teams.
Positive
Guido Schmitz, CTO and co-founder, OneTeam
Building an AI-powered team & why narrowing our ICP doubled our win ratePodcast interview, Love At First Try (podcast)
OneTeam's CTO screenshots the product into Lovable to prototype feature changes for customer feedback. This cuts each iteration from four or five days to under a day. Designers then rebuild it in the design system.
"Previously it would take so long, you sit down, make wireframes, talk with designers, then iterate, and each iteration step was maybe four or five days. Now it's less than a day. Why Lovable and not Claude…"
Positive
Eric Hoffert, CTO at Kargo
Taking Innovative Products from Idea to Large-Scale | Eric Hoffert, CTO, KargoInterview, Yeka newsletter (Substack)
Kargo's CTO reports that product leaders there use Lovable to build prototypes for new products much faster than before, which helped the company explore new ideas more rapidly.
"For product leaders, tools like Lovable and more have been used here to vibe code prototypes for new products much more quickly than before."
Mixed
Elena Levi, Director of Product, Payoneer
EP 144 - AI Tools: Lovable with Elena LeviPodcast interview, Product for Product Management podcast (Apple Podcasts)
Payoneer's Director of Product Management explains choosing Lovable for prototyping, user tests and developer handoff, and where engineering expertise, privacy, maintainability and the last mile still limit it.
Positive
Zac Hays, CPO at Luxury Presence
The Secrets Behind a 30x AI Product Team | Zac Hays, CPO (Luxury Presence)Podcast interview, LogRocket LaunchPod podcast
Luxury Presence's CPO cut the team's design sprint from five days to three. On day two each person takes a tool such as Lovable, v0 or Bolt and has an hour to come back with a prototype. He calls the speed amazing.
"…the second day we all picked different tools, V0, Bolt, Lovable, and said…"
Positive
Teresa Torres, Product discovery coach and author (Product Talk), reporting interviews with named product leaders
AI Prototyping: How 11 Real-World Teams Are Transforming Their Work with LovableNewsletter, Product Talk
Eleven product teams describe Lovable discovery prototypes, from an EQS customer test built in about an hour to a Kallidus feature engineers built from a prototype. They report limits on complex dashboards, fidelity and production.
Positive
Moritz Homann, Director of Product Innovation and AI at EQS Group
AI Prototyping: How 11 Real-World Teams Are Transforming Their Work with LovableInterview article, Product Talk (Teresa Torres)
EQS Group's Director of Product Innovation and AI built a data retention prototype from a screenshot of the platform in about an hour, against a week before. Customers gave detailed feedback because it looked live. He prompts step by step because Lovable gets confused when asked too much at once.
"It took maybe an hour or something, which would have traditionally taken a week."
Mixed
Jared Stephens, leads the product design team at TimelyCare
AI Prototyping: How 11 Real-World Teams Are Transforming Their Work with LovableInterview article, Product Talk (Teresa Torres)
TimelyCare's product design lead built an interactive user test in six hours with real LLM sentiment analysis on a Supabase backend, which customers used to flag real risks. Colleagues asked when it would ship, logins slowed from half a second to 25 seconds, and he calls it far from production.
"When I first started logging in, it took half a second. By the end, it took 25 seconds…"
Mixed
Zack Nolette, senior product manager at LexisNexis Risk Solutions
AI Prototyping: How 11 Real-World Teams Are Transforming Their Work with LovableInterview article, Product Talk (Teresa Torres)
A LexisNexis Risk Solutions product manager built two early prototypes for homeowner insurance in minutes and showed them at a carrier advisory meeting before engineering or design were involved. Getting specific visuals right took hours, and sections came out in different styles.
"And Lovable cranked out a beautiful prototype. It took like five minutes…"
Positive
Ok_Sprinkles_6449, Reddit poster in r/lovable
Post: Lovable For My Small BusinessReddit post
Turned the company's paper records, spreadsheets, maintenance books, estimates, and invoices into a job-management app in a couple of hours for about US$8 of usage, to deploy through GitHub.
Mixed
Olga Alekseeva, Growth hacking expert with over 10 years at Kanbanchi
Building Internal Tools With AI: a Bootstrapped Team's Honest Account (NOT a Case Study!)Company blog post, Kanbanchi blog
Kanbanchi built its internal time, pay and leave Hub in Lovable with no hand-written code. The whole team uses it daily, but non-standard pay calculations misfire and credit top-ups reach about EUR 600 a month.
Positive
Jamie Wright, Project manager and former web designer and developer
AI made me a developer again. Kind of.dev.to post
A project manager builds small internal tools in an afternoon, including a Lovable scoping app for the team, and checks what each does before the team relies on it.
Mixed
Anton Zaides, Author of the Manager.dev newsletter for engineering managers
Explaining to business people why building software is still hardNewsletter, Manager.dev
His hackathon team picked Lovable so recruiters could maintain the app. Day one reached 90% of the project, then minor changes broke everything until they slowed down to plan each area.
Positive
Growtika, Runs an agency (per HN profile: Growtika)
Comment on: Claude DesignHacker News comment
Their agency throws together quick interactive drafts in Claude or Lovable to show clients' designers intent, shrinking feedback loops from weeks to minutes.
Mixed
Andreas and Sjimi (madewithlove partners), Partners at madewithlove, a CTO-as-a-service and software engineering firm
What to do with Lovable prototypes & Claude Cowork - The SaaS Show #5Video, YouTube (madewithlove)
madewithlove's partners discuss a client's Lovable prototype that raised security, compliance and ownership questions, arguing teams need clearer boundaries, permissions and experienced technical leadership.
"…that switch when you need to. I think that's my take. Yeah, the thing is here, they realize that they can not use this with actual customers. It's also already because of ISO requirements that they have in terms of security, but…"
Positive
Phill Lord-David, Senior Product Manager at Kallidus
AI Prototyping: How 11 Real-World Teams Are Transforming Their Work with LovableInterview article, Product Talk (Teresa Torres)
Kallidus's senior product manager rebuilt an existing feature in Lovable in five minutes, added the requested feature, and handed the prototype to engineers in place of finalized designs. Simple formatting took him an hour and ten prompts, and Lovable sometimes said it had fixed a problem when it had not.
"We used Lovable to show the engineers what we meant."
Positive
lbreakjai, Employee at a very small startup
Comment on: Is Lovable getting monetization wrong?Hacker News comment
Their CTO builds internal CRUD tools in Lovable. Code is only OK and needs a human in the loop, but it does work they estimate would need two full-time developers.
Positive
Alex Wittenberg, CEO of airCFO
The next Excel: The skill that will define tomorrow's top operatorsNewsletter, The AI CFO (Substack)
airCFO's CEO, with zero coding experience, built a content workflow tool in Lovable over a weekend that the team now uses regularly, then moved to Cursor and Claude Code to build faster.
Counted for Engineering leaders and teams.
Positive, 5
Mixed
tradematesHQ, Reddit poster in r/lovable
Post: Many of you asked how we moved our Lovable app to our own VPReddit post
The team moved its Lovable app off Lovable hosting to its own VPS. It migrated code through GitHub plus the database, users, storage, functions, secrets, payments, emails, and cron jobs. It now deploys from GitHub.
Mixed
Aatir Abdul Rauf, VP of Marketing at vFairs
Vibe Coding 101: 23 practical tips to build functional prototypesNewsletter, aatir.substack.com
vFairs moved to Lovable prototypes, and the author praises its design output and GitHub bridge to Cursor, but warns that AI bug fixes burn hundreds of credits and that RLS gets overlooked.
Positive
Ok_Sprinkles_6449, Reddit poster in r/lovable
Post: Lovable For My Small BusinessReddit post
Turned the company's paper records, spreadsheets, maintenance books, estimates, and invoices into a job-management app in a couple of hours for about US$8 of usage, to deploy through GitHub.
Mixed
Brenden Cambier, CTO in residence (madewithlove) for a client
"Good news, I built it in Lovable.": an engineer's guide to surviving that sentenceEngineering blog post, madewithlove blog
A CTO in residence describes a geologist's Lovable internal tool that cut errors and raised productivity but quietly duplicated ETL logic in Supabase. GitHub, LOVABLE.md and CI guardrails were added to contain it.
Negative
hansonkd, CTO (per HN profile: getdynasty.com)
Comment on: Le Chat: Custom MCP Connectors, MemoriesHacker News comment
Their engineer used Lovable for about a day, then cloned the repo and continued in Cursor, which was more productive.
Mixed or negative, 1
Mixed
Jack Steele, Director of Engineering, Knak
How Knak's Designers Prototype Directly in the CodebaseEngineering blog post, Knak blog
Knak's designers used Lovable to work out interactions alongside Figma, but the separate artifacts caused handoff churn, so Knak replaced Figma and Lovable handoffs with Claude Code prototyping on one git branch.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Git sync is on every plan and two-way. Lovable creates a new repository without importing an existing one and edits one branch at a time. Code editing and download in Lovable need a paid plan. Sync with GitHub, GitLab, or Bitbucket
Open them in the recordCounted for Engineering leaders and teams.
Positive, 4
Positive
Alex Wittenberg, CEO of airCFO
The next Excel: The skill that will define tomorrow's top operatorsNewsletter, The AI CFO (Substack)
airCFO's CEO, with zero coding experience, built a content workflow tool in Lovable over a weekend that the team now uses regularly, then moved to Cursor and Claude Code to build faster.
Mixed
Brenden Cambier, CTO in residence (madewithlove) for a client
"Good news, I built it in Lovable.": an engineer's guide to surviving that sentenceEngineering blog post, madewithlove blog
A CTO in residence describes a geologist's Lovable internal tool that cut errors and raised productivity but quietly duplicated ETL logic in Supabase. GitHub, LOVABLE.md and CI guardrails were added to contain it.
Positive
Teresa Torres, Product discovery coach and author (Product Talk), reporting interviews with named product leaders
AI Prototyping: How 11 Real-World Teams Are Transforming Their Work with LovableNewsletter, Product Talk
Eleven product teams describe Lovable discovery prototypes, from an EQS customer test built in about an hour to a Kallidus feature engineers built from a prototype. They report limits on complex dashboards, fidelity and production.
Mixed
exiguus, Hacker News commenter on a team with product owners and architects
Comment on: The Architecture Behind Lovable and BoltHacker News comment
Their team trials Lovable alongside v0 for fast prototypes built by product owners and architects, used with stakeholders, and then discards the code.
Mixed or negative, 2
Mixed
Anton Zaides, Author of the Manager.dev newsletter for engineering managers
Explaining to business people why building software is still hardNewsletter, Manager.dev
His hackathon team picked Lovable so recruiters could maintain the app. Day one reached 90% of the project, then minor changes broke everything until they slowed down to plan each area.
Negative
bears123, Engineer at a very small startup
Ask HN: How to fight back against Lovable, Replit, etc. in enterprise productsHacker News thread (Ask HN)
Non-engineers at a very small startup produce screens in Lovable and want to ship them. Even as inspiration it led to poor, inconsistent UX.
Counted for Engineering leaders and teams.
Positive, 4
Mixed
Valtech EU Design, Valtech EU design team (team newsletter)
Static Figma Files Aren't Cutting It: What Bolt vs. Lovable Taught Our Design Team (June 2025)Company design team newsletter, Valtech EU Design (Substack)
Valtech's design team found Lovable produced better-looking designs and a Figma-like visual editor, but needed more specific prompts, was prone to errors and missed fonts and styling.
Mixed
SubstantialTap81, Reddit poster in r/lovable; operations lead at a 50-person startup
Post: Our Lovable bill keeps climbing every month. Is this normal?Reddit post
A 50-person startup's ops lead finds the upkeep of three internal tools built on Lovable keeps raising the bill. The plan price is not the cause. The lead is trying Softr, Glide, and Budibase.
Mixed
Jack Steele, Director of Engineering, Knak
How Knak's Designers Prototype Directly in the CodebaseEngineering blog post, Knak blog
Knak's designers used Lovable to work out interactions alongside Figma, but the separate artifacts caused handoff churn, so Knak replaced Figma and Lovable handoffs with Claude Code prototyping on one git branch.
Mixed
Aatir Abdul Rauf, VP of Marketing at vFairs
Vibe Coding 101: 23 practical tips to build functional prototypesNewsletter, aatir.substack.com
vFairs moved to Lovable prototypes, and the author praises its design output and GitHub bridge to Cursor, but warns that AI bug fixes burn hundreds of credits and that RLS gets overlooked.
Mixed or negative, 3
Negative
bears123, Engineer at a very small startup
Ask HN: How to fight back against Lovable, Replit, etc. in enterprise productsHacker News thread (Ask HN)
Non-engineers at a very small startup produce screens in Lovable and want to ship them. Even as inspiration it led to poor, inconsistent UX.
Mixed
Zack Nolette, senior product manager at LexisNexis Risk Solutions
AI Prototyping: How 11 Real-World Teams Are Transforming Their Work with LovableInterview article, Product Talk (Teresa Torres)
A LexisNexis Risk Solutions product manager built two early prototypes for homeowner insurance in minutes and showed them at a carrier advisory meeting before engineering or design were involved. Getting specific visuals right took hours, and sections came out in different styles.
"And Lovable cranked out a beautiful prototype. It took like five minutes…"
Mixed
Olga Alekseeva, Growth hacking expert with over 10 years at Kanbanchi
Building Internal Tools With AI: a Bootstrapped Team's Honest Account (NOT a Case Study!)Company blog post, Kanbanchi blog
Kanbanchi built its internal time, pay and leave Hub in Lovable with no hand-written code. The whole team uses it daily, but non-standard pay calculations misfire and credit top-ups reach about EUR 600 a month.
Every concern practitioners raise, most raised first.
Counted for Engineering leaders and teams.
Mixed
Brenden Cambier, CTO in residence (madewithlove) for a client
"Good news, I built it in Lovable.": an engineer's guide to surviving that sentenceEngineering blog post, madewithlove blog
A CTO in residence describes a geologist's Lovable internal tool that cut errors and raised productivity but quietly duplicated ETL logic in Supabase. GitHub, LOVABLE.md and CI guardrails were added to contain it.
Mixed
Elena Levi, Director of Product, Payoneer
EP 144 - AI Tools: Lovable with Elena LeviPodcast interview, Product for Product Management podcast (Apple Podcasts)
Payoneer's Director of Product Management explains choosing Lovable for prototyping, user tests and developer handoff, and where engineering expertise, privacy, maintainability and the last mile still limit it.
Mixed
Jared Stephens, leads the product design team at TimelyCare
AI Prototyping: How 11 Real-World Teams Are Transforming Their Work with LovableInterview article, Product Talk (Teresa Torres)
TimelyCare's product design lead built an interactive user test in six hours with real LLM sentiment analysis on a Supabase backend, which customers used to flag real risks. Colleagues asked when it would ship, logins slowed from half a second to 25 seconds, and he calls it far from production.
"When I first started logging in, it took half a second. By the end, it took 25 seconds…"
Negative
Chaitanya Shetty, founder of thechaicoder.com, which builds products for startups
Lovable, Bolt and v0 are a disaster for MVPs (a small rant)X post
A founder came to his studio after spending over US$2,000 on Lovable credits with an unusable prototype. He sees screens built before the backend, fixes that break other parts, and data that does not save once real users sign up, and keeps the tools to showing an idea fast.
Mixed
Andreas and Sjimi (madewithlove partners), Partners at madewithlove, a CTO-as-a-service and software engineering firm
What to do with Lovable prototypes & Claude Cowork - The SaaS Show #5Video, YouTube (madewithlove)
madewithlove's partners discuss a client's Lovable prototype that raised security, compliance and ownership questions, arguing teams need clearer boundaries, permissions and experienced technical leadership.
"…that switch when you need to. I think that's my take. Yeah, the thing is here, they realize that they can not use this with actual customers. It's also already because of ISO requirements that they have in terms of security, but…"
Positive
lbreakjai, Employee at a very small startup
Comment on: Is Lovable getting monetization wrong?Hacker News comment
Their CTO builds internal CRUD tools in Lovable. Code is only OK and needs a human in the loop, but it does work they estimate would need two full-time developers.
Counted for Engineering leaders and teams.
Raised as a concern, 6
Mixed
Anton Zaides, Author of the Manager.dev newsletter for engineering managers
Explaining to business people why building software is still hardNewsletter, Manager.dev
His hackathon team picked Lovable so recruiters could maintain the app. Day one reached 90% of the project, then minor changes broke everything until they slowed down to plan each area.
Negative
Enzo (design prism), Founder of Prism, a website agency
my honest experience using Lovable for client websitesVideo, YouTube
Agency founder running client sites on Lovable reports constant breakage, such as refusing a supplied image and deleting existing recipes, and finds Replit, v0 and Cursor more reliable.
"…goes beyond that right with these these kind of ripple effect changes like I'm saying like deleting all of the recipes from the website when you're trying to add a new one like that's really messed up man. So, I don't know. I have a…"
Mixed
Aatir Abdul Rauf, VP of Marketing at vFairs
Vibe Coding 101: 23 practical tips to build functional prototypesNewsletter, aatir.substack.com
vFairs moved to Lovable prototypes, and the author praises its design output and GitHub bridge to Cursor, but warns that AI bug fixes burn hundreds of credits and that RLS gets overlooked.
Positive
Phill Lord-David, Senior Product Manager at Kallidus
AI Prototyping: How 11 Real-World Teams Are Transforming Their Work with LovableInterview article, Product Talk (Teresa Torres)
Kallidus's senior product manager rebuilt an existing feature in Lovable in five minutes, added the requested feature, and handed the prototype to engineers in place of finalized designs. Simple formatting took him an hour and ten prompts, and Lovable sometimes said it had fixed a problem when it had not.
"We used Lovable to show the engineers what we meant."
Negative
Chaitanya Shetty, founder of thechaicoder.com, which builds products for startups
Lovable, Bolt and v0 are a disaster for MVPs (a small rant)X post
A founder came to his studio after spending over US$2,000 on Lovable credits with an unusable prototype. He sees screens built before the backend, fixes that break other parts, and data that does not save once real users sign up, and keeps the tools to showing an idea fast.
Positive
Teresa Torres, Product discovery coach and author (Product Talk), reporting interviews with named product leaders
AI Prototyping: How 11 Real-World Teams Are Transforming Their Work with LovableNewsletter, Product Talk
Eleven product teams describe Lovable discovery prototypes, from an EQS customer test built in about an hour to a Kallidus feature engineers built from a prototype. They report limits on complex dashboards, fidelity and production.
Discussed without concern, 1
Mixed
Valtech EU Design, Valtech EU design team (team newsletter)
Static Figma Files Aren't Cutting It: What Bolt vs. Lovable Taught Our Design Team (June 2025)Company design team newsletter, Valtech EU Design (Substack)
Valtech's design team found Lovable produced better-looking designs and a Figma-like visual editor, but needed more specific prompts, was prone to errors and missed fonts and styling.
Counted for Engineering leaders and teams.
Raised as a concern, 4
Negative
Chaitanya Shetty, founder of thechaicoder.com, which builds products for startups
Lovable, Bolt and v0 are a disaster for MVPs (a small rant)X post
A founder came to his studio after spending over US$2,000 on Lovable credits with an unusable prototype. He sees screens built before the backend, fixes that break other parts, and data that does not save once real users sign up, and keeps the tools to showing an idea fast.
Mixed
SubstantialTap81, Reddit poster in r/lovable; operations lead at a 50-person startup
Post: Our Lovable bill keeps climbing every month. Is this normal?Reddit post
A 50-person startup's ops lead finds the upkeep of three internal tools built on Lovable keeps raising the bill. The plan price is not the cause. The lead is trying Softr, Glide, and Budibase.
Mixed
Olga Alekseeva, Growth hacking expert with over 10 years at Kanbanchi
Building Internal Tools With AI: a Bootstrapped Team's Honest Account (NOT a Case Study!)Company blog post, Kanbanchi blog
Kanbanchi built its internal time, pay and leave Hub in Lovable with no hand-written code. The whole team uses it daily, but non-standard pay calculations misfire and credit top-ups reach about EUR 600 a month.
Mixed
Aatir Abdul Rauf, VP of Marketing at vFairs
Vibe Coding 101: 23 practical tips to build functional prototypesNewsletter, aatir.substack.com
vFairs moved to Lovable prototypes, and the author praises its design output and GitHub bridge to Cursor, but warns that AI bug fixes burn hundreds of credits and that RLS gets overlooked.
Discussed without concern, 2
Mixed
Elena Levi, Director of Product, Payoneer
EP 144 - AI Tools: Lovable with Elena LeviPodcast interview, Product for Product Management podcast (Apple Podcasts)
Payoneer's Director of Product Management explains choosing Lovable for prototyping, user tests and developer handoff, and where engineering expertise, privacy, maintainability and the last mile still limit it.
Negative
Enzo (design prism), Founder of Prism, a website agency
my honest experience using Lovable for client websitesVideo, YouTube
Agency founder running client sites on Lovable reports constant breakage, such as refusing a supplied image and deleting existing recipes, and finds Replit, v0 and Cursor more reliable.
"…goes beyond that right with these these kind of ripple effect changes like I'm saying like deleting all of the recipes from the website when you're trying to add a new one like that's really messed up man. So, I don't know. I have a…"
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Plan mode costs 1 credit per message plus any research it runs, and Build mode bills by complexity. Since June 18, 2026, Cloud hosting and AI features draw on the same balance, and owners and admins on paid plans can set limits and alerts. Credits and usage
Open them in the recordStatements this group's sources agree on, then the ones close to agreement.
Lovable is strongest for prototypes, MVPs, and first versions. Production needs more engineering.
12 supporting sourcesThe usual path is syncing the code to Git and continuing in an IDE or with a coding agent such as Cursor or Claude Code.
8 supporting sourcesLovable works well for internal tools, dashboards, and admin apps used by a known group of colleagues.
8 supporting sourcesResults depend on planning, small scoped requests, and written project rules more than on one detailed prompt.
7 supporting sourcesQuestions the sources split on, with the count on each side.
Evidence remains split
Runs in production, 3 sources
Some run Lovable-built apps with real users, adding environments, local setups, or review as they go.
Prototype only, 5 sources
Others use Lovable only to agree a design or test an idea, and rebuild or move the work elsewhere for production.
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on Engineering leaders and teams.
30 sources. These accounts focus on how teams, startups, and leaders use Lovable for prototypes and internal tools, who builds, and when the work moves to engineers.
80 sources. These accounts focus on speed, credit spend, fix loops, and taking over the code for people building on their own, from non-technical founders to engineers.
110 sources. This gives the broadest read, but combines non-technical builders, engineers, and teams whose expectations of the code differ.
110 sources from practitioners, by the context they work in. Filled rows count for this group.
Emphasizes Speed, credits, and fix loops
Emphasizes Prototypes to align people, and who maintains them
Emphasizes Internal tools and handoff to engineering
Emphasizes Governance and where Lovable stops
What changes with scale. Individual builders talk most about speed and credit cost, and about getting stuck in fix loops. Teams and leaders talk about who builds, prototypes as a way to align stakeholders, and the point where engineers take the code over. The security findings come mostly from outside researchers who scanned many apps.
Where this group's sources were published.
Counted for Engineering leaders and teams, from 30 sources. Change group
45 sources for this group, 15 of them documentation
Older evidence is retained when it still applies. Sources that depend on a retired plan, the old message limits, or the pre-TanStack Start template stay in the history, marked Needs a recheck.
See sources by originWho each source is, how it knows, whether it still applies and what it counts toward.
Newest first, on its own page. Every count above opens its sources there.
Read all 125 sourcesAbout this read
A running review of what engineering teams report about Lovable, from individual builders to engineering leaders. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Flagged for a recheck, of the sources that take a side: leaders and teams 0 of 30, individual builders 7 of 79, all practitioners 7 of 109.
Each row opens its sources for the group you are reading.
| Finding | Engineering leaders and teams | Individual builders | All practitioners | Sources |
|---|---|---|---|---|
| Current readCurrent sentiment | 12 positive, 14 mixed, 4 negative | 37 positive, 20 mixed, 22 negative | 49 positive, 34 mixed, 26 negative | Sources |
| PraiseSpeed to a Working App | 17 of 17 positive | 31 of 35 positive | 48 of 52 positive | Sources |
| PraiseCode You Can Take Over | 5 of 6 positive | 13 of 22 positive | 18 of 28 positive | Sources |
| PraiseBuilding Without Engineers | 4 of 6 positive | 18 of 21 positive | 22 of 27 positive | Sources |
| PraiseBuilt-in Backend | 1 of 2 positive (under the minimum) | 11 of 14 positive | 12 of 16 positive | Sources |
| PraiseGenerated UI Quality | 4 of 7 positive | 9 of 16 positive | 13 of 23 positive | Sources |
| PraiseValue for Money | 0 of 1 positive (under the minimum) | 2 of 3 positive (under the minimum) | 2 of 4 positive (under the minimum) | Sources |
| ConcernFix-and-Break Loops | 6 of 7 raise it | 16 of 21 raise it | 22 of 28 raise it | Sources |
| ConcernCredit Spend | 4 of 6 raise it | 13 of 27 raise it | 17 of 33 raise it | Sources |
| ConcernSecurity & Data Exposure | 1 of 2 raise it (under the minimum) | 8 of 9 raise it | 9 of 11 raise it | Sources |
| ConcernComplexity Ceiling | 3 of 3 raise it (under the minimum) | 8 of 10 raise it | 11 of 13 raise it | Sources |
| ConcernProduction Readiness | 6 of 6 raise it | 6 of 7 raise it | 12 of 13 raise it | Sources |
| ConcernLearning Curve | 1 of 1 raise it (under the minimum) | 3 of 4 raise it (under the minimum) | 4 of 5 raise it | Sources |
| ConsensusPlan first, then build in small steps | 7 supporting | 15 supporting (below threshold) | 22 supporting | Sources |
| ConsensusEngineers or coding agents take over the code | 8 supporting | 10 supporting (below threshold) | 18 supporting (below threshold) | Sources |
| ConsensusReview before real users and data | 4 supporting (under the minimum) | 9 supporting (below threshold) | 13 supporting (below threshold) | Sources |
| ConsensusStrongest for prototypes and first versions | 12 supporting | 8 supporting (below threshold) | 20 supporting (below threshold) | Sources |
| ConsensusA fit for internal tools | 8 supporting | 6 supporting (below threshold) | 14 supporting (below threshold) | Sources |
| DisagreementCan a Lovable-built app run in production, or is it a prototype to rebuild? | Runs in production 3, Prototype only 5 | Runs in production 7, Prototype only 2 | Runs in production 10, Prototype only 7 | Sources |
| DisagreementDoes Lovable save time overall once fixes and rework are counted? | Time saved 2, Rework absorbed it 1 (under the minimum) | Time saved 3, Rework absorbed it 2 | Time saved 5, Rework absorbed it 3 | Sources |
| Current readEvidence mix | 45 sources | 95 sources | 125 sources | Sources |
GILD's checks of claims against official documentation, kept apart from the source counts.
