Despia Lovable Setup: No Master Prompt Needed
Despia Lovable setup takes no master prompt. Add the MCP server once, then pull in each native feature from the docs exactly when you need it.
A common first question when starting a Despia app in Lovable is some version of "which master prompt do I paste in before I begin?" The assumption is that there is a big block of setup prompts you feed the builder up front, and the app only works once it is in there. There isn't, and it doesn't work that way. Here is what to do instead.
There is no master prompt to feed Lovable
You do not front-load anything. Lovable imports npm packages directly now, so despia-native installs like any other dependency at the point you need it. You build your app the way you normally would, and when you want a native capability you ask for it in plain English or drop in the one call that does it. Nothing about the initial project setup depends on a wall of pasted prompts.
The idea of a master code block is a holdover from older setups where the builder had no way to know the API existed. That gap is closed a different way now, covered below.
Where the prompts actually live
Every native feature has its own ready-to-use docs page and its correct syntax in the docs at setup.despia.com. Haptics, biometrics, GPS, storage, push, OAuth, and the rest each have a page with the exact call and the behaviour to expect. You copy the prompt for the feature you are adding, when you are adding it, not all of them at the start.
So the honest answer to "where are the prompts" is: in the feature docs, one per capability, pulled in on demand.
Add the Despia MCP to Lovable
There is one setup step worth doing before you start, and it replaces the whole master-prompt idea. Add the Despia MCP server to Lovable. It gives the builder always-current knowledge of the despia-native API, so it writes correct calls and does not fall back to Capacitor or Cordova patterns that do not apply here.
Copy the MCP URL:
https://setup.despia.com/mcpIn Lovable, open your project settings and find Add MCP or MCP Settings.
Paste the URL into the MCP field and save.
That is the setup. From then on the builder knows the API without you pasting docs into the chat for every feature.
How to add a native feature
Once the MCP is in place, adding native capability is a single gated call inside your existing code. The one pattern to get right is the environment check, so native calls only fire inside the Despia runtime and your app still runs in a normal browser during development.
import despia from 'despia-native'
const isDespia = navigator.userAgent.toLowerCase().includes('despia')
async function saveTask() {
await persist()
if (isDespia) despia('successhaptic://')
}
A more real example is in-app purchases. Launch the native paywall through RevenueCat, then read entitlements back from the store, all from the same web code and gated the same way:
if (isDespia) {
despia(`revenuecat://launchPaywall?external_id=${userId}&offering=default`)
const data = await despia('getpurchasehistory://', ['restoredData'])
const active = (data.restoredData ?? []).filter(p => p.isActive)
if (active.some(p => p.entitlementId === 'premium')) unlockPremium()
}
Purchases run through StoreKit and Play Billing natively, so it passes store review, and the entitlement check queries the store directly with no backend required.
Keep the despia() calls inside the isDespia gate. Global callbacks are the exception and get assigned outside it, but for the common case this gate is all you need.
The whole Despia Lovable workflow
You do not prepare Lovable for Despia with a master prompt. You add the MCP once, then build normally and pull each native feature in from the docs when you reach it. That is the entire workflow.
Add native features from your existing app
Every native capability is one JavaScript call away inside the web codebase you already have, with the prompt and syntax for each one in the docs. Add the MCP, then build.
