Build

SDK docs

Updated October 24, 2026

Your app saves student progress by calling kitequad, a tiny API KiteQuad adds to every published app. There's nothing to install — it's already there when your app runs.

Start with the KiteQuad-ready prompt

The quickest way to get an app that works here: paste this at the top of your request to Claude, Gemini, ChatGPT or AI Studio, then describe the app you want. It tells the AI how to save progress and which few things to avoid so your app passes KiteQuad's checks the first time.

Build this as a single-page web app that will run on KiteQuad, a safe host for classroom apps. Follow these rules so it works and passes KiteQuad's checks.

SAVING PROGRESS
- Save and load with KiteQuad's built-in "kitequad" API instead of your own server or a database.
  Call  await kitequad.ready()  once at the start, then:
    await kitequad.store.set("level", 4)          // value can be any JSON, up to 64 KB
    const level = await kitequad.store.get("level") // null if nothing is saved yet
  Pass { scope: "class" } as the last argument to share data across the whole class; the default is per-student.
- For a scoreboard use  kitequad.board.post(score)  and  kitequad.board.top().
- Do NOT ask students for their name, email, or anything else that identifies them.

NO OUTSIDE CONNECTIONS
- Do NOT call fetch, XMLHttpRequest, WebSocket or EventSource to any other website — network access is blocked.
- Do NOT load fonts, images, scripts or styles from other websites. Use system fonts, or include the files with the app.
- Do NOT navigate to another page or open pop-up windows.

HOW TO WRITE SCRIPTS
- Put your JavaScript inside <script> tags in the page, or in .js files. Both are fine.
- If your code creates a <script> element, set its text BEFORE you add it to the page; don't add an empty one and fill it in later.
- Do NOT use import() from inside a <script> that your code adds while the app is running.
- Do NOT put a <script> inside the srcdoc of a sandboxed <iframe>.
- Use at most one document.write() per <script>.

TEST IT FIRST
- Add  <script src="https://kitequad.com/sdk/v1.js"></script>  to the top of the page to try "kitequad" on your own computer before publishing. KiteQuad replaces this line with the real version when you publish.

Saving progress

Wait for kitequad.ready(), then read and write with kitequad.store. A value is anything JSON can hold.

await kitequad.ready();

// save (per student by default)
await kitequad.store.set("level", 4);

// load — null if nothing is saved yet
const level = await kitequad.store.get("level");

// share across the class
await kitequad.store.set("teamScore", 120, { scope: "class" });

The kitequad API

try {
  await kitequad.store.set("level", 4);
} catch (err) {
  if (err instanceof kitequad.KiteQuadError && err.code === "quota_exceeded") {
    // too much saved — clear something first
  }
}

Limits

Test on your own computer

Before publishing, add this one line to the top of your page and open the file in a browser. kitequad then works with a fake student called “Test Student” and saves to that browser's storage, through the same code as the real SDK — and makes no network requests of any kind.

<script src="https://kitequad.com/sdk/v1.js"></script>

When you publish, KiteQuad removes that line and wires in the real SDK, so you can leave it in while you build.

A note on scripts

When you publish, KiteQuad moves the code written inside your pages into files so each page can run under a stricter safety rule. Most apps work exactly as before. A few patterns behave a little differently — a script that builds another script and uses it at once, or a short timer that expects a later script to already be on the page — and the publish check tells you when it spots one. The prompt above steers your AI clear of them. There's more on the help page.