Your watch
Connect the watch by USB and wait for it to appear as a drive, then pick it below.
This browser can read the watch but cannot write to it: only Chromium-based desktop browsers (Chrome, Edge, Opera) implement the directory-write API. You will get a ready-to-run install script instead. This browser also cannot remember the folder, so it has to be picked each visit.
Pending changes
Install script
Catalogue
Nobody reviews these apps. Kira compiles most of them from a named commit and publishes the recipe, so you can check that a binary came from the source it claims. Whether that source is any good, or safe, is something Kira cannot tell you. Anything marked pre-release is UNA’s own unreleased build, republished as-is with no recipe of Kira’s. The watch has no code signing, so integrity here is a SHA-256 against this catalogue plus the file’s own CRC, which catches corruption but not a hostile publisher. What this does and does not prove →
Loading catalogue…
Your own app can be listed here. You send a repository, a commit
and the SDK release to build against, not a binary. Kira compiles it in the same
pinned toolchain as everything above, checks the result against what your
CMakeLists.txt declares, and lists it in these same grids with the
source and commit on its card.
How to submit an app →
Release notes
from the upstream SDK releases
Upstream publishes no per-app changelog, so these are the release notes for each
apps-v* tag. Whether a given app’s code actually changed in a release is
shown on its card, derived from the binary and not from the prose. Submitted apps
ship on their own schedule, so their notes are on their cards.
Questions and problems
on GitHubKira is unofficial, and not a support channel for UNA Watch. Anything about the watch itself, or how an app behaves once installed, belongs with UNA Watch. Everything below is about this catalogue and installing from it.
- Ask a question. Answers stay searchable for whoever asks next.
- Suggest something: a change, or an app worth carrying.
- Report a bug in the catalogue, an install, or the site itself.
- Get your own app listed. You send a commit for Kira to build, not a binary to upload.
- Report a security problem privately. Kira writes binaries to your watch, so please don’t post those publicly.
- Ask for an app to be removed, and see what that does and where to go if I’m not answering.
All of these need a GitHub account. If that’s a barrier, say so in a suggestion, or ask someone who has one to raise it, and another route can be added.