> For the complete documentation index, see [llms.txt](https://help.twinr.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.twinr.dev/website-builders/lovable.md).

# Lovable

Turn a Lovable project into an iOS and Android app, and let Lovable's agent write the Twinr code for you.

Lovable builds your site; Twinr turns it into a mobile app. Because Lovable can connect to Twinr's MCP server, its agent can read your Twinr account and write the native code into your project for you.

## Before you start

* A published Lovable project with a live URL.
* A Twinr app created from that URL — see [Create App](https://help.twinr.dev/create-app/create-app.md).

## Steps

1. [**Add the Twinr MCP server**](https://help.twinr.dev/website-builders/lovable/add-mcp.md) so Lovable's agent can read your Twinr account and Twinr's guides.
2. [**Add push notification support**](https://help.twinr.dev/website-builders/lovable/add-push-notifications.md) so you can send notifications to your users.
3. [**Integrate the login script**](https://help.twinr.dev/website-builders/lovable/integrate-login-script.md) so the app knows who is signed in.

Each step stands on its own — do the ones you need.

## What to expect from the agent

Lovable's agent asks a question before it writes anything. For push notifications, it usually asks whether notifications go to everyone or to specific signed-in users. That is deliberate: sending to individuals needs sign-in and somewhere to store each person's device token.

It also tends to build a little more than you asked for, because these features depend on each other — ask for per-user push and you may get sign-in and a user table along with it. Read what it proposes before accepting.

{% hint style="info" %}
Some steps finish in the Twinr dashboard, not in Lovable. The agent will tell you which — for example, push notifications do nothing until the integration is switched on for your app.
{% endhint %}
