CLOSING LOVABLE'S VISIBILITY GAP Independent UX

CLOSING LOVABLE'S VISIBILITY GAP Independent UX Case Study

The Problem Lovable's builders lose credits and working code without warning — not because the safety features are missing, but because cost and version history surface after the fact, not before the decision that needed them.

The Evidence Sourced directly from dozens of independent Trustpilot and G2 reviews — and confirmed in writing by Lovable's own support team, who publicly acknowledged that credits were "running down faster than expected and cutting users off mid build." Every claim in this case study links to its real source.

My Approach Two scoped UX additions built from patterns Lovable already has: a credit estimate shown before the prompt is sent (not after), and a visual version-history rail in the sidebar for one-click rollback. Paired with a proposal for Lovable Academy — a certification program modeled on Webflow University and Notion's playbook.

The Result A full research-backed case study and working Figma prototype — problem framing, sourced evidence, redesigned screens, and a business-logic section connecting every fix directly back to where the evidenced problem actually happens in the product flow.

UI/UX • Product Design • SaaS • AI Tools • UX Research • Case Study • Figma

🎨 View Interactive Prototype → [https://window-parse-39982836.figma.site ] 📖 Read the Full Case Study → [https://claude.ai/artifact/1a7PiarYskoh8YCtE4A2WH ]

📌 Project Note Independent case study, not affiliated with, endorsed by, or commissioned by Lovable. Created to explore how evidence-based UX research can turn a real, documented product problem into a scoped, defensible design proposal.

Need an evidence-backed UX audit for your AI or SaaS product? Let's talk.