Notes stay on disk. Plain HTML, CSS and JavaScript — no build, no dependencies, no tracking.
.dmgmacOS .deb / .rpmLinux .msiWindows MIT / Apache-2.0
Each well is a mock built from tokens — swap one for a real capture when you have it, keep the grid when you don't.
Say the outcome, not the mechanism. These rows and chips are placeholders — keep them honest, or swap in a real screenshot.
Rows with a name, one line and a switch read as a real product screen. Two rows beat five — this well is a drawing, not a data table.
Connections look real when they show state: connected, syncing, done. The percentages here are placeholders — keep them plausible.
Show the work, not the promise: a short changelog proves the product moves. Mono type plus one badge is enough.
Chips, tiles and wires are placeholders: connect your real services and keep one language from hero to footer.
Signed builds for macOS, Linux and Windows. The buttons below resolve the latest release automatically.
Each button queries the GitHub API and points at the latest release asset for its platform; if that fails it falls back to the releases page. The mechanism is in download/README.md.
Download the latest release, or take the template and make it unmistakably yours.
MIT / Apache-2.0 · no build · no dependencies
Something else? Open an issue on GitHub.
Say the license, then say what it costs to run. Honesty here buys trust everywhere else.
If the answer is "no", make it specific: what never leaves the machine, and what (if anything) the website measures.
Describe the update path in one sentence. If the app checks for updates, say how often and where it checks.
List the platforms and the minimum versions. Update this answer the day a platform changes, not later.