WristFoundry field notes · KineticWear / Software Development / IoT
There is a particular kind of optimism involved in putting a keyboard on a two-inch watch. It works. You can enter a Wi-Fi password. You can navigate the menus. And then, somewhere around the third capital letter, you remember that there is a perfectly good keyboard sitting on the desk.
In the first WristFoundry post, I introduced the ESP32-S3 watch framework: a small, independent platform with touch navigation, shared services, power management, and room for new applications. The next addition gives that platform something useful beside it: WristFoundry Companion, a Flutter application for Windows.
Plug in the watch, select it, connect, and bring its services onto a larger screen. The companion is part of the latest WristFoundry update, with source available in the project repository.
A larger workbench for a small device
I wanted the companion to feel like it belonged to the watch. The dark panels, cyan highlights, rounded cards, and compact instrument-like presentation carry over from the embedded interface. There is more room to work, but it is recognizably the same family.
It starts with a Welcome and Connect screen. USB candidates appear in a device selector; connecting begins an identity and capability handshake. Only after the watch answers does the app load its dashboard. A COM port tells us that Windows can see something. The handshake tells us that the something speaks WristFoundry.

The overview brings battery information, Wi-Fi state, watch time, and connection details into one place. From there, the sidebar leads to Wi-Fi, Time, Settings, Apps, and Diagnostics. There is also a demo mode for exploring the interface without a watch attached.
What the companion can do
| Area | Current behavior |
|---|---|
| Connection | Select a USB device, validate identity and capabilities, and load watch state. |
| Wi-Fi | Configure credentials and request scanning or connection through the watch services. |
| Time | Sync from the PC, enter time manually, select a timezone, or request NTP synchronization. |
| Apps | Inspect registered applications and request navigation on the watch. |
| Diagnostics | Read device information and copy a redacted report. |
The settings page also makes the current limits visible. Brightness and sleep intervals are firmware policy in this version; the desktop does not present working-looking sliders for controls the watch has not implemented.
Engineering note / One framework, two interfaces
The desktop sends versioned USB commands. Firmware handlers pass those commands through WristFoundry’s existing network, time, hardware, and app services. That keeps ownership of the radios, RTC, and navigation in the watch framework, rather than creating a second competing implementation for the desktop.
Setting the time without a tiny keyboard
Time controls were an especially satisfying first use. The companion separates the watch’s timezone from the act of setting its clock. Sync from this PC sends UTC; timezone selection determines the local time the watch should display. Manual entry has its own source-timezone selection so an entered wall-clock time has an explicit meaning.

After flashing the companion-enabled development firmware, I connected the physical watch and successfully used the time and timezone controls. That was the moment this stopped being a nice desktop screen and became a useful tool on the bench.
The implementation updates time through the shared service and reports RTC write failures. Independent RTC readback, longer offline continuity checks, and a systematic pass through the remaining hardware tests still need doing.
The watch was taking a nap
Getting there included a familiar embedded-system detour. Windows reported Code 43 and a failed USB device-descriptor request. This was the same cable I had used to program the watch, so the obvious cable explanation was not especially convincing.
Keeping the watch awake and reconnecting USB made it appear in Device Manager. The companion could then see the serial port, but its connection attempt timed out. That turned out to be a separate problem: I had installed the desktop companion while the watch was running the older backup firmware, which had no companion protocol handler.
The two failures looked similar from the desktop. One was a USB availability problem associated with sleep. The other was a watch that could enumerate but had nothing listening for the new handshake. Flashing the matching development firmware got the real connection working.
Engineering note / A blank display and a sleeping processor are different things
A tethered watch needs a power policy that keeps USB responsive. The latest USB-awake change is designed to keep the processor available and suspend automatic display dim/off while USB power is present, wake the display on attachment, and restore normal inactivity behavior after unplugging. The power button can still deliberately blank the display. The change has been built; its complete physical attach, idle, unplug, and reconnect sequence remains to be confirmed.
Apps, without pretending there is an app store
The Apps page lists applications registered in the firmware and can ask the watch to open them or return home. Today those applications are compiled into the firmware. Individual installation and removal need a future package runtime, so the interface explicitly marks installation as unavailable.
That is still useful groundwork. The desktop can discover what the watch supports, and future framework features have a place to appear without assuming every firmware build has identical capabilities.
Useful diagnostics, without exporting the Wi-Fi password
The diagnostic report uses a bounded event history and selected device fields. It excludes raw serial logs, request bodies, Wi-Fi names, IP addresses, device identifiers, and passwords. The development firmware also retains its existing RAM-only credential behavior; adding a desktop interface does not quietly change the storage profile.
Where this leaves WristFoundry
The Windows companion has passed analysis, its 23 Flutter tests, a release build, and packaging. The development firmware and framing/power-policy checks have also passed their recorded builds. More importantly, the watch has now made a real connection, and I have used the companion to set its time and timezone.
There is still a practical test list: the latest USB-awake behavior, systematic reconnect checks, independent RTC verification, and battery-current measurements. Wi-Fi and the other implemented controls also deserve their own full hardware acceptance pass. A working connection is a milestone, not a substitute for those measurements.
The WristFoundry repository contains the framework and companion source, with companion documentation covering setup, protocol boundaries, and testing. For the watch hardware and original framework story, start with Phase One.
The little watch still works on its own. Now, when it comes back to the desk, it has a larger workbench waiting for it.
