Ship it

Click Publish in the top-right corner of the editor.

Two things happen. First, Lovable runs a security scan. It checks your RLS policies, looks for API keys in your code, and verifies that authentication is protecting the right routes. It takes about a minute or two. If it flags something, the messages are specific. Fix what it finds, and we even have a "Try to fix all" button that does it for you. If you followed the steps in Lesson 7, you should pass clean, but if not, clean them up.

Second, it deploys. Your app goes live at your-project-name.lovable.app. Real URL that works right now.

Copy the URL and open it on your phone. Upvote loads: cards, votes, categories, the form, dark mode, all of it. Submit an idea from your phone, then walk to your laptop and open the admin panel. The idea is already there. Draft an AI response, save it, and check your phone. The response is on the card.

Now send that URL to someone: a co-founder, a friend, a beta user. Ask them to submit a feature request and watch it appear in your admin panel. Draft a response. They see it on their end. Two people, using software you built, exchanging real information. That's a product.

Here's what you built in the last hour. A feature request board where users submit ideas, vote on what matters, and see real responses from you. Voting is enforced so nobody can game it. An admin panel that only you can access, with AI that drafts responses and categorizes requests for you. User accounts with email and Google login. Security rules so no one can touch another person's data. A polished theme with dark mode, animations, and a layout that works on any screen. All of it live, right now, at a URL anyone can visit.

You described what you wanted, one piece at a time, in the right order, and refined until it was right. The plan-build loop kept each step focused. The version history meant you never had to worry about breaking things. And the build order — skeleton, then function, then polish — meant every prompt added to the foundation instead of fighting it.

That rhythm doesn't change. Bigger projects have more lessons, more features, and more complexity. But the loop is the same: describe, see, refine, then ship.