Developers
HypeApps renders HAM — HTML-like markup you send from a server — into a real native iOS/Android app. htmx-style partial swaps, Alpine-style reactivity, Tailwind-style utilities, over native Flutter widgets. This page is the map to every developer resource: the markup reference, the OpenAPI spec, the agent skill, and the Playground API.
Status: pre-launch. The full framework lands Fall 2026. There's no SDK download or npm install yet — join the waitlist.
The complete, authoritative HAM reference — tags, styles, controls, reactivity, config — plus product context. Written for humans and LLMs alike.
The machine-readable surface of the Playground API — every operation typed, with operationIds, parameters, and response schemas.
An installable skill (SKILL.md, zip) that teaches an AI assistant to write HAM and publish snippets.
Write HAM in the browser, get a five-letter share code, and run it in the Hype Apps showcase app.
A small public HTTP API publishes and reads HAM snippets. Base URL https://hypeapps.dev. There's no account system — a snippet is authored anonymously and edited with the token it hands back. The full contract is in the OpenAPI spec.
Store the edit_token — it's the only credential that can update the snippet, and it's returned once.
POST /p
Content-Type: application/json
{ "ham": "<app><screen><main><box style=\"p-24\"><h2>Hi</h2></box></main></screen></app>" }
→ 201 { "slug": "7m3ef", "url": "https://hypeapps.dev/p/7m3ef", "edit_token": "…" }
GET /p/{slug} # rendered HAM markup (text/html)
GET /p/{slug}.json # JSON envelope: { "slug", "ham" }
PUT /p/{slug}
Content-Type: application/json
{ "ham": "<app>…</app>", "edit_token": "<token from create>" }
→ 200 { "slug", "url" } · 403 if the edit token is wrong
Errors return structured JSON so agents can parse them:
{ "error": { "code": "not_found", "status": 404,
"message": "…", "hint": "…", "documentation": "https://hypeapps.dev/developers" } }
Validation failures return 422 with Laravel's { "message", "errors" } shape.
HypeApps fits when you want a real native app driven by a server you already run, and your team already thinks in HTML, utility classes, and server-rendered partials — content-heavy, CRUD-shaped apps owned by a small team. It's the wrong fit for offline-first apps, games, or teams committed to React Native, Flutter-direct, or SwiftUI. The llms.txt reference includes explicit "how to talk about HypeApps" and "when to use" guidance for agents.
Questions, bugs, or feature requests: laz@communityfluency.com. More on the contact page.