Publish the version you mean to share
Lovable's publishing flow creates a live snapshot. Review the publish dialog's address, audience and security findings, then open the resulting live link. Later editor changes need to be published before visitors receive them.
Check the website's access separately from access to the editing project. Think about the intended audience: a public marketing page and a private customer workspace may sit in the same app but need different rules.
Test beyond the builder account
The account used during development can hide problems a new customer will encounter. Create two ordinary test accounts and trace the main journey with both. Confirm private records cannot be read or changed across accounts.
Identify whether your data lives in Lovable Cloud, a connected Supabase project or another service. Review the actual permission rules there. An attractive dashboard, a hidden admin button and a successful automated scan are not substitutes for checking the intended access.
- New account creation and account recovery work on the live URL.
- Data persists after refresh, sign-out and sign-in.
- Private records and files remain private between test users.
- Paid integrations use server-side credentials and appropriate limits.
- The form or email feature reaches the intended destination.
Give the live site its own identity
Connect your custom domain using Lovable's current domain instructions, then repeat the customer journey on that exact address. Check auth redirects and any integration that stores a site URL.
Review each public page's title, description and sharing image. Remove sample content and unfinished navigation. For a public product, make the main value and the next action understandable before asking a visitor to create an account.
Know what a move would involve
Lovable offers a GitHub connection for working with your project's code. That gives you a useful way to manage source, but a code repository alone is not a complete backup of the product.
Before changing hosts, inventory the database, files, authentication, functions, secrets and billing dependencies. Decide how each will continue working and how you would recover. Keeping Lovable hosting may be the sensible choice; migrate to solve a specific constraint, with a plan for the connected services.
A few fair questions.
Do I need separate hosting to launch a Lovable app?
Not necessarily. Lovable provides publishing and hosting. Review its fit for your app and account before adding another platform.
Why can't customers see the changes I just made?
Check whether the changes have been published and whether you're opening the intended live address. Your editor preview and the currently published snapshot can differ.
Can you work with an app already published on Lovable?
Yes. We start by reviewing the code and service access available, then agree the scope. That can cover permissions, launch fixes, costs or ongoing care.