Parlane
Doc. PARLANE-01Native front-end for AI agentsiOS · Android next

Give your AI agent a native mobile app.

Write no app code. You already built the agent; Parlane is its iPhone front-end (Android next). Serve plain JSON over MCP (or a small REST contract), and it renders native chat, voice, dashboards, and push. No SDK, no webviews, no mobile project to maintain.

Coming soon to the App StoreRead the contract// free for one app
Transport MCP / RESTRender nativeContract JSON SchemaSDK none
The Systems and Energy dashboard, rendered native in Parlane
Chat · your agent authors the UI
Add a water-reserves gauge to Systems.
Done. It's live on the Systems dashboard.

§ 1

How it works

You serve the data; Parlane draws the app. Nothing is downloaded and executed: dashboards are declarative components from a fixed native catalog, which is what keeps the App Store posture clean.

Your backend
any language or host; the agent you already built
manifest.json + UI docs
plain JSON over MCP (primary) or a small REST contract
Parlane → native app
chat · voice · dashboards · push · shortcuts · share
Figure 1server-authored JSON, rendered as native surfaces

Dashboards are declarative JSON, not code. Each component is a small object; Parlane draws it from a fixed native catalog. Long-press any component in the app to see the exact JSON behind it.

ui-document.json · one component
{
  "type": "metric",
  "props": {
    "label": "Battery",
    "value": "87%",
    "delta": "+5%",
    "intent": "good"
  }
}
Parlane's native component catalog, rendered from JSON
Figure 2 · the native component catalog, rendered from JSON.

§ 2

Surfaces you can declare

Declare only what you serve; Parlane hides the rest. Each surface is a small, documented contract.

SurfaceContractWhat the user gets
ChatPOST /chat · SSE
Streaming markdown, tool-activity, attachments. Voice rides on it with on-device speech.
DashboardsGET /ui/{id}
A component tree from 17 native types: metrics, charts, toggles, sliders, tables, maps. Free to view, interactive on Pro.
ActionsPOST /action
Interactive components invoke a tool and get a replacement UI document back.
Pushrelay · /notify
Server-triggered notifications through the optional, open-source relay. Visible previews pass through the relay and Apple.
Shortcuts & Sharemanifest
Siri/App Shortcuts and the iOS share sheet, declared as phrases and an ingest tool.

§ 3

Make your app Parlane-ready

Paste this into your coding agent. It wires the endpoints and checks its own work against the hosted JSON Schemas.

prompt.txt
Make my app Parlane-ready.

Parlane renders my backend natively (chat, voice, dashboards,
push) from plain JSON I serve. There is no SDK.

1. Serve a manifest at /.well-known/parlane.json (or MCP
   resource "parlane://manifest"). Declare only the surfaces
   I support; validate against spec/manifest.schema.json.
2. If I don't speak MCP, add REST: POST /chat (SSE: delta /
   tool / done / error), GET /ui/{id}, POST /action.
3. Require Authorization: Bearer <token> on every request.

Follow the schemas in spec/ exactly; test against
spec/examples/.
Authoritative sources
  • parlane.ai/spec/*.schema.json
    JSON Schema, draft 2020-12. The contract wins when prose disagrees.
  • parlane.ai/llms-full.txt
    The entire integration kit in one fetch, for your agent.
  • Demo Agent
    A runnable reference backend, bundled in the app. Offline, zero setup.

Serve the JSON. Get the native app for free.

Download Parlane and open the bundled Demo Agent to watch a manifest become a native app before you write a line.

Coming soon to the App StoreIntegration docs