Watchapp distribution: UUID, appinfo, versioning and install path #70

New issue

Open

opened 2026-09-01 17:35:55 +02:00 by robert · 0 comments

robert commented

2026-09-01 17:35:55 +02:00

(Migrated from git.butzei.de)

Goal

Answer "how does anyone other than me install this?". The plan covers building and sideloading via Dev Connect (#3), and nothing else. For a public MIT repository that is a gap.

Acceptance criteria

Watchapp UUID generated once and recorded; the companion addresses it and it must never change casually
package.json / appinfo complete: name, author, version, capabilities, targetPlatforms for emery and gabbro
App icon and menu icon for both geometries
Versioning scheme for the watchapp, and how it relates to PROTO_VERSION (docs/PROTOCOL.md section 6) - they are not the same number
Companion APK versioning aligned, so a user can tell which pair they have
Install instructions in the README covering both halves, and what happens if only one is updated (#53 should catch it, and should be named)
Decide and document the distribution route for the watchapp - Rebble store, the Core Devices store, or GitHub releases with sideload instructions
Release checklist: both builds, both versions bumped, protocol version reviewed

Files

watchapp/package.json
README.md

Notes

PROTO_VERSION bumps on contract semantics; app versions bump on releases. Conflating them is a trap - most releases change neither side's protocol.

## Goal Answer "how does anyone other than me install this?". The plan covers building and sideloading via Dev Connect (#3), and nothing else. For a public MIT repository that is a gap. ## Acceptance criteria - [ ] Watchapp UUID generated once and recorded; the companion addresses it and it must never change casually - [ ] `package.json` / `appinfo` complete: name, author, version, capabilities, `targetPlatforms` for `emery` and `gabbro` - [ ] App icon and menu icon for both geometries - [ ] Versioning scheme for the watchapp, and how it relates to `PROTO_VERSION` (docs/PROTOCOL.md section 6) - they are not the same number - [ ] Companion APK versioning aligned, so a user can tell which pair they have - [ ] Install instructions in the README covering both halves, and what happens if only one is updated (#53 should catch it, and should be named) - [ ] Decide and document the distribution route for the watchapp - Rebble store, the Core Devices store, or GitHub releases with sideload instructions - [ ] Release checklist: both builds, both versions bumped, protocol version reviewed ## Files - `watchapp/package.json` - `README.md` ## Notes `PROTO_VERSION` bumps on contract semantics; app versions bump on releases. Conflating them is a trap - most releases change neither side's protocol.