Proxied
We fetch, hold the secret, map and push the changes. Easiest.
QuickWatch turns a JSON project into Wear OS watch screens, a tile and a complication. The expected workflow when a user asks you for a QuickWatch watch app:
https://quickwatch.app/mcp) is available, use its tools: they build, validate and
preview the app in the chat.Full guide: https://quickwatch.app/llms.txt and https://quickwatch.app/docs/agent-guide.md.
JSON Schema: https://quickwatch.app/schema/quickwatch.schema.json. schemaVersion is 2. Each Experience needs title,
pages (each with a root component) and tile; complication is optional. Text props are bindings like {{ weather.temp | round }}° that read data by source name; data.json holds sample data for every source.
Ids are lowercase (a-z, 0-9, -). Unknown properties are errors. Components, tile templates, complication kinds, icons and
limits: https://quickwatch.app/schema/capabilities.json. Examples: https://quickwatch.app/llms-full.txt.
{
"schemaVersion": 2,
"sources": { "weather": { "type": "http", "url": "https://api.example.com/weather?city=Stockholm", "refresh": { "poll": "15m", "onOpen": true } } },
"experiences": {
"weather": {
"title": "Weather",
"icon": "cloud",
"pages": { "now": { "title": "Stockholm", "root": { "type": "text", "value": "{{ weather.temp | round }}°" } } },
"tile": { "template": "text", "title": "Weather", "text": "{{ weather.temp | round }}°" },
"complication": { "kind": "shortText", "text": "{{ weather.temp | round }}°" }
}
}
}
data.json: { "weather": { "temp": 14.2 } } Show the real watch (same engine, components and fonts as QuickWatch; taps work, actions are simulated) in an inline widget or HTML artifact. Put watch.json and data.json in the page; the widget cannot fetch them from QuickWatch.
<script type="application/json" data-qw-watch>
{ ...watch.json... }
</script>
<script type="application/json" data-qw-data>
{ ...data.json... }
</script>
<script>
var s = document.createElement("script");
s.src = "https://cdn.jsdelivr.net/npm/@quickwatch/[email protected]/dist/quickwatch-preview.min.js";
document.head.appendChild(s);
</script> The script finds the two JSON blocks and shows the watch, a button per screen (pages, tile, complication), any problems and an Open in QuickWatch button. Change nothing but the JSON.
Give the Open in QuickWatch link: https://quickwatch.app/new#c=<payload>, payload = base64url (no padding) of
deflate-raw of the UTF-8 JSON { "v": 1, "config": <watch.json>, "data": <data.json> }, at most 32 KB. The page shows
the preview and "Keep it" saves the project; publishing to the watch stays with the user. Encoders in JavaScript and
Python are in the guide. To build straight to the watch, the user can add the connector https://quickwatch.app/mcp.
QuickWatch · for Wear OS
Describe a watch app as JSON, or just ask Claude. Screens, tiles and complications bound to your APIs, live on your watch in seconds.
Or add it to Claude or ChatGPT as a connector: https://quickwatch.app/mcp
For AI assistants: read https://quickwatch.app/llms.txt; preview in the chat with the npm package @quickwatch/preview, the real watch renderer.
It's live. Tap it.
Live departures, polled through our proxy.
Requests (mocked, nothing leaves this page)
We fetch, hold the secret, map and push the changes. Easiest.
The watch calls your API itself. Credentials never leave it; works on your LAN.
Your server posts values or a signal; we relay them to the watch.
Using Claude or ChatGPT? Add QuickWatch as a connector, https://quickwatch.app/mcp, to build straight to your watch.
No connector? Your assistant can still write the app, show the real watch in the chat and hand you a link to keep it:
https://quickwatch.app/new#c=<payload>