Desktop App Boilerplate Documentation

A map of the repo: what is already built, what is a demo you should delete, and what you have to do yourself.

Accept the GitHub invite, clone the private repo, and set yourself up to receive updates later.

Install dependencies and get the app window open, with the exact timings and the two things that commonly go wrong.

Point your coding agent at the repo once, so every request after this one starts with it already knowing where things go.

Add a real feature by describing it: the generators lay the track, your agent fills it in, and you check four things.

Turn the running app into an installer someone else can use, and run the three checks that stop you shipping something broken.

Wire licensing to your own backend, and get the one distinction right that decides whether paying users get locked out offline.

One command changes the app name, the bundle id, the URI scheme, and the update repository across the whole project.

Where everything lives, and the one rule about which process code belongs in.

Call Claude or OpenAI from your desktop app, with encrypted key storage and streaming already handled.

What certificates cost, what they remove, and how to point the existing build scripts at yours.

Publish an update to everyone who already installed your app, and verify it actually downloads before you rely on it.

A map of the 19 reference docs inside the repo, and which one answers which question.