despia-v3-extensions
Installation
SKILL.md
Despia V3 Extensions
For the Despia V3 runtime only, and experimental. You write native files, describe them in a JSON manifest, and serve them from the web app. Despia approves the files and compiles them into a new native build. The page then calls extension://<name>/<route>?<params>. All facts are in references/; read the file for the step you are on. Never invent manifest fields, types, hooks or error codes. If a fact is not in the references, say so and point to https://docs.despia.com/experiments/v3-extensions .
Workflow
- Confirm the app is on Despia V3 and the capability is not already a Despia feature. Read
references/limits.mdand tell the user the platform limits that apply. - Lay out
public/despia/extensions.jsonandpublic/despia/<name>/manifest.jsonwithios/andandroid/beside it (references/manifest.md). The folder name is the extension id and matches[a-z][a-z0-9]{1,23}. - Declare each route, its typed parameters (
string,int,bool,enum,https_url), itsoutputvariable and callback, and any events (references/manifest.md,references/routes-and-answers.md). - Write the iOS handler (
references/ios.md) and the Android handler (references/android.md). Answer every call once, with data or an error code and message. - Declare native work as typed or custom (
references/manifest.md). Dependencies must be pinned files in the approval; nothing is downloaded at build time. - Write the web call and its answer handling (
references/routes-and-answers.md). - Copy the pattern from
examples/recorder/(the Background Recorder sample, notes inreferences/recorder-sample.md) when a complete template helps. - Tell the user the approval flow: Despia approves
extensions.jsonand every referenced file, eachmanifest.jsonincluded. Any change needs a new approval and a new native build, never over-the-air. Extensions are enabled per app by Despia. The user owns and maintains the native code; Despia does not support customised code.