Wrist Cockpit

I want the watch to do more than announce that something is happening on a different screen.

The wrist-cockpit work explores small Zepp OS applications for messaging and agent interfaces. The repository includes a watchface, mini-apps such as Home, Messages, ChatGPT and Hermes Remote, and bridge components that supply data from elsewhere. Putting the interface on the wrist does not mean putting the whole service on the watch.

A conversation has to open before it is useful

One practical line of work has been removing unnecessary waiting from the message bridge. Earlier paths used fixed pauses before reading a page. A fixed pause is reassuringly simple, but the user pays for the whole interval even when the page is ready sooner.

The revised bridge uses bounded readiness checks. The relevant implementation can wait for the information it needs instead of always waiting out a timer. Local history and draft handling address another part of the experience: keeping useful context available while a refresh or connection is still in progress.

Those mechanisms are evidence of an implementation. They are not, by themselves, a measurement of physical watch-to-phone latency.

Keep the layers honest

A browser bridge, a phone companion, the transport and the watch UI can each introduce a failure. Emulator results help with interface work, but they do not establish physical-device battery life, microphone behaviour or connection reliability.

The project has working prototypes and continuing integration work. Reading messages, composing a draft and transmitting a reply deserve separate capability checks. This overview does not turn a result from one layer into an assurance that the entire conversation path works.