Hire a Lovable developer when your app breaks in production

Most “Lovable developer” jobs I take are not blank canvases. The preview worked. Real users arrived. Sessions die, emails never send, or everyone sees everyone else’s data. That is rescue and hardening — a different engagement from building an MVP from scratch.

#Symptoms that mean hire, not another prompt

• Works in Lovable preview, fails on the production domain.
• Auth loops, missing email verification, or OAuth callback mismatches.
• Open tables or USING (true) policies under load.
• Vercel/env misconfig — blank page after deploy.

#How rescue usually runs

Reproduce with two real accounts, fix root cause (auth/RLS/deploy), then redeploy and document. I do not polish CSS while data is leaking.

Rescue triage:
[ ] Reproduce on production URL
[ ] Two-user data isolation test
[ ] Auth + email/OAuth path
[ ] Env secrets audit
[ ] Stable URL + handover notes

#MVP vs rescue

Brand-new idea-to-live builds belong on Lovable AI MVP Developer. Existing broken apps belong on Lovable Developer. Pick the page that matches your starting point so the scope stays honest.