Building apps
A channel app is built the way you build any web app — you write it. You author an HTML/JS front end and, when the app needs server-side logic, a Python back end, add any supporting files, and publish it to your machine. It's ordinary web development, with one difference: the app runs grounded on your machine, so it computes through the key-free proxy and its activity lands on your audit chain.
Two ways to author
By hand
Write the HTML, JS, and Python yourself, in whatever editor you like — including the VS Code extension — and publish. No black box, no required tooling.
In the workbench
Scaffold and preview an app in the browser workbench, publish in a click. A convenience for getting started fast, not a requirement.
With optional AI assist
If you want it, the workbench can draft or edit an app for you — one feature on top, never the only path. The app is still your code.
It's your app, grounded on your machine
However you author it, the result is the same primitive: a versioned app on your machine's pages shelf. It computes against your machine, its traffic is on your audit chain, and it's published as an immutable version you can roll back. You own the code and the machine keeps it honest — nothing about how you wrote it changes what it can prove.
Building apps needs no AI at all. A developer writes the front end and back end and ships it; the framework's job is to host it, meter it, and prove it — exactly as it would for any other app. AI assistance is available as a feature for those who want it, and invisible to those who don't.
Read next
- Publishing & serving — how an app is versioned, hosted, and computes key-free.
- Channels — what a channel app is made of.
- Applications — apps built on the framework, running live.