Built with Lovable?
Fixes for the problems Lovable apps run into once real users arrive, each checked against Lovable’s own documentation. Start with taking a Lovable app to production.
Export Lovable code: GitHub sync, zip download and running it outside LovableConnect GitHub, GitLab or Bitbucket from Project settings, then Git. It works on every plan and keeps syncing both ways. Download codebase gives a one-off .zip on paid plans. Neither includes your secrets, database data or stored files, so export those separately and set environment variables before you build.Lovable app slow: finding the real bottleneck and fixing itIn most slow Lovable apps the database is the bottleneck: queries without indexes, row level security policies that call functions per row, or a small instance under load. Check the pressure cards under More, then Database, then Manage, then Settings, ask Lovable for the slowest queries, fix those, and only then pay for a bigger instance.Lovable auth not working: redirects, email confirmation and lost sessions fixedMost Lovable auth failures come from four places: your live or custom domain missing from the Redirect URLs list, users stuck unconfirmed, a page guard that runs before the saved session loads, or row level security returning nothing. Check More, then Users, then Settings first, then your auth code and table policies.Lovable mobile layout broken: why it looks fine in preview and how to fix itLovable's Mobile view shrinks the preview inside your desktop browser, so it misses phone toolbars, the keyboard and touch. Most breakage comes from fixed widths, full-height screens built on 100vh, wide tables and classes written desktop first. Find the overflowing element, fix it in code or with a targeted prompt, then test the published app on a real phone.Lovable SEO not working: client-rendered vs server-rendered projectsIt depends on when the project was created. Lovable apps from 13 May 2026 use TanStack Start and render every page on the server. Older React and Vite apps render in the browser, and only verified crawlers get pre-rendered copies, which can miss late-loading content. Run the SEO and AI search review, fix metadata per page, and consider upgrading older projects.Lovable Stripe payments: choosing the right setup and making it reliableLovable offers built-in payments (any paid plan, Paddle or Stripe, webhooks managed for you) or your own Stripe account connected with a restricted or secret key. With your own Stripe, webhooks are off by default and subscriptions are checked by email at sign-in, so add a verified webhook and store subscription status before you take real money.Lovable Supabase issues: empty data, paused databases and schema drift fixedMost Lovable Supabase problems come from row level security returning nothing, a paused database, schema changes made outside Lovable's migrations, or two Lovable projects sharing one Supabase project. Work out which backend you are on first, because Lovable's built-in backend and your own Supabase project are fixed in different places.
See if BlackFig fits what you’re building (it probably does)
A quick 20 minute call. No slides, no hard sell. You leave with a clear next step either way.