Publishing your Lovable app gives you a link to share. It does not yet tell people why they should open it. Your first launch needs a clear audience, a useful demonstration and one next step that works.

This guide uses a fictional app that turns scattered client requests into a project plan. Replace that example with the action that makes your own app useful. Lovable builds the product; Hamla helps prepare the marketing and connect it to product activity.

1. Choose who should try the app

Start with a specific problem: freelance designers receiving client requests across several messages. Show how your app turns those messages into a usable plan, using a real example with private details removed.

Ask Lovable: “Review the first-use flow. A freelance designer should be able to paste a client brief and create a project plan. Keep one clear call to action, explain whether registration is required, and verify the flow on mobile. Tell me about any errors before changing unrelated features.”

If the app is ready, invite people to create their first plan. If it is not ready, say so and offer a waitlist. Test the published URL as a new visitor, not only in the builder preview.

2. Connect Hamla to the published app

If you already own a Hamla business, give Lovable the website snippet from that business. For a new installation, paste the following request into your project chat. Use the published app’s real domain.

Add Hamla to this app using its public install API.
1. POST https://app.hamla.io/api/install with JSON {"website":"<my published app domain>"}. No API key or authentication is required.
2. Add the returned data.snippet to the <head> on every page, exactly as returned. Never invent a business ID.
3. Show me data.claimUrl privately. It is single-use and expires in 72 hours. Never put it on a public page or in a repository.
4. If you cannot make the request, tell me and ask for the snippet. Do not pretend installation succeeded.
Do not add a Hamla secret key, or send customer emails or phone numbers as part of this installation.

Follow Hamla’s installation instructions if you need to make the request yourself. Open the private claim link and sign in or create your account to take ownership. The agent creates an installation, not your personal account. Before you claim it, only anonymous activity is recorded and campaigns cannot launch.

Hamla installation ownership screen with illustrative visitor activity.

Lovable supports direct API integrations. This procedure uses Hamla’s public API and website SDK; you do not need to assume a dedicated Hamla connector is installed. After the change, publish the updated app and check that a visit appears in the correct Hamla business.

3. Track signup and the first useful action

Visits show interest. Product events show whether someone tried the feature. After claiming your installation, ask Lovable to add these example events using the Hamla Events guide:

  • account_created: record a successful registration, not a click on the signup button.
  • project_plan_created: record a successfully saved first plan, not merely opening the editor.
  • subscription_started: if you sell a subscription, record a confirmed payment from the server with type: purchase, value and currency.

Use your app’s stable customer ID to connect activity to the right person. These event names are examples, not required names. Keep any Hamla secret key on the server, in your backend’s secret storage. Lovable’s secrets documentation explains its Cloud setup; never put the key in browser code or a VITE_ variable.

Run a test signup and create a plan. Check that both events arrive in Hamla, and that a failed action does not produce a success event. For server retries, use the same idempotency key so a repeated request does not create a duplicate event. Follow the event reference for the payload.

Hamla event timeline with example signup, project-plan and subscription activity.

4. Show the app to people who need it

Give Hamla the actual demonstration, audience and app link. For example: “Prepare a LinkedIn launch post for freelance designers. Show the supplied client brief and the plan my app generated. Invite designers to try it with their own anonymized brief. Use this published URL. Do not invent testimonials or results.”

Review the draft and link before publishing through a supported connected account. If your potential users are in a specialist community, contribute where they already discuss the problem and follow its sharing rules. You handle personal outreach and community conversations; Hamla can help prepare the content.

An invitation could be: “You mentioned that client requests arrive across several messages. I built a tool that turns them into a project plan. Would you like to try it with an anonymized brief and tell me what needs work?” Ask before sending a private demo, and leave room for a no.

5. Follow what happens after the visit

Compare visits, registrations and successful first plans. If visitors do not register, examine the promise and signup flow. If they register but do not create a plan, try the first-use experience with them. Small samples give you questions to investigate, not proof that one channel caused a result.

Once you have permission to contact users, you can configure a signup-triggered welcome sequence. Set the first plan as its conversion goal to stop remaining follow-ups when the user succeeds. Receiving events alone does not configure or launch this campaign for you.

  • Try the published app on desktop and mobile as a new visitor.
  • Confirm the snippet loads and test events reach your claimed Hamla business.
  • Choose one audience, one demonstration and one action. Review the content before sending it.
  • Ask testers what helped and what confused them, then fix the point where they got stuck.

For the broader launch workflow, read Marketing for vibe coders. To see what Hamla can prepare for your app, explore AI marketing for vibe coders. Screenshots here show Hamla demo content, not a Lovable project or verified campaign results.