ZSWatch's development entry point is a $99 board, the final watch hardware is still in design, and the Android app is behind an invite
ZSWatch - the Open Source Zephyr™ based Smartwatch, including both HW and FW.
At a glance
- What is it?
- ZSWatch is a GPL-licensed open-source smartwatch built from scratch on the Zephyr RTOS, with its circuit design in KiCad across four separate repositories. To work on the firmware you buy a development board from a distributor rather than the watch, the phone story splits by platform with the recommended Android route being third-party software, and the newest release is seven months behind the last commit.
- Who is it for?
- Use ZSWatch if you want to read firmware that drives real sensors and a real display, and if you are prepared to learn an RTOS rather than just read a library. The hardware description is unusually complete for an open hardware project: every part is named with a datasheet link, the board design is in an open format, and the extension board is documented down to the connector part number.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly C, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- ZSWatch/ZSWatch3,446 ★ · +76
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| ZSWatch/ZSWatch | 3.4k | 3.4k |
76 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
You develop on a $99 board, because the watch itself is still being designed
The callout at the top of the README is about a development kit, and it has a price and a distributor.
The kit costs $99, is ordered from a named electronics distributor, and is described as having the same microcontroller and the same sensors as the finished watch in a larger form factor for development and debugging. The battery is optional and it runs off USB-C.
The rest of the kit's description is about what you can do with it rather than what is in it: breakout headers, USB-C with debug and serial access, power measurement headers, and a debug header.
Then, further down, the DIY section says the final miniature watch hardware is still being developed, and points DIY builders at the hardware repositories for ordering information.
Put together, that is a project where the deliverable is not yet available and the working hardware is a larger board that shares the silicon. The $99 is not a discount on the watch, it is the price of the only thing you can currently put the firmware on.
The circuit design lives in four other repositories
Every hardware design in this project is in KiCad, and none of it is in this repository.
Four separate repositories are linked: the watch board, described as 38 millimetres in diameter; a development board with breakout headers and a debug header; an extension board for health and audio; and a dock board that breaks out USB-C for debugger and serial access.
Four boards for one watch is a deliberate decomposition rather than an accident. The watch board has to fit a 38 millimetre circle, so anything that does not fit gets its own board, and the development board is a different shape entirely so the headers fit.
The firmware repository does contain a hardware directory, and the root has a submodules file, which is how those four repositories are attached to a checkout. So a clone with submodule initialisation brings the designs along, and a clone without it leaves four empty directories.
That is a reasonable arrangement for hardware, where a board is its own project with its own lifecycle, and it is worth knowing before you assume the design files are in the firmware tree.
The microphone is on the watch and the speaker needs an add-on board
The hardware list runs to ten entries, and one of them has a condition attached.
The microphone is on the main board: an I2S part for audio recording. The speaker is listed separately with a note that it requires the health extension board.
So a watch that records audio can, in principle, play it back, but only if you have also bought or built the add-on board. That is a coherent choice, since a speaker plus its codec plus an amplifier is a large fraction of a 38 millimetre circle, and the add-on board is where the audio codec lives along with the optical sensing hardware.
The same pattern runs through the rest of the list. The core board carries the chip, the display interface, the motion sensor, the magnetometer, the pressure sensor, the light sensor, the real-time clock, the microphone and the power management. The add-on carries the biometric sensing front end, its light sources and photodiodes, a sensor hub, the audio codec and the board-to-board connectors.
The add-on is described as work in progress, at roughly 16.8 millimetres in diameter, and the project says its design, bill of materials and firmware support may change.
The iOS app is on a store and the Android app is behind an invite
The phone integration section splits by platform and the two halves are not comparable.
For iOS, marked as recommended, the official companion application is on the App Store, and the watch additionally supports two of Apple's own services natively: the notification centre service for notifications and the media service for media control.
For Android, marked as experimental, the same application currently requires invite access, and the way to get it is to ask through a chat server or an email address.
So the recommended iOS experience is a public store listing, and the recommended Android experience is an application you have to be invited to. The section then says that for a stable experience you should use a different application entirely, one written by a third party and hosted on a different forge.
An open hardware project delegating its stable Android path to someone else's application is a reasonable division of labour. It does mean that the phone story for half the potential users runs through software nobody in this repository controls, and the README's own framing of the first-party Android app as experimental is the honest signal to weigh.
Watchfaces written for a different microcontroller run on this watch
One line in the software section is worth reading twice.
The watch supports watchfaces written for a different microcontroller family, contributed by a named person, and the README links a fork for details.
So a face authored on one chip family is being run on this watch's chip family. That implies a translation layer between the two faces' graphics stacks, which is either a compatibility effort worth understanding or a portability accident worth not relying on.
The rest of the software story is conventional. Bluetooth low energy communication through the companion application or the third-party one, multiple dynamically switchable watchfaces showing time, date, battery, weather, steps, notifications and environmental data, pop-up notifications, and an application picker with an extensible app framework.
The application framework is the part with legs. The README links application source directories directly inside the repository, for settings, for music control and for a compass, and says there are many more. So the watch's function set is a set of applications you can read, and adding one is a matter of following a pattern rather than reverse-engineering a binary.
A pressure sensor is quoted at twenty centimetres of accuracy
Nine of the ten hardware entries quote a function. One of them quotes a number that does not fit its function.
The pressure sensor is described as high performance, with an accuracy of about twenty centimetres, linked to its datasheet.
Twenty centimetres is a length, and a pressure sensor measures pressure. What a length in that range usually describes is the resolution of an altitude derived from a pressure reading, not the accuracy of the sensor itself.
The README does not say which it means. It gives the figure as a single number attached to the part name, in a list where every other entry states a capability: gesture navigation for the motion sensor, automatic brightness control for the light sensor, time keeping for the real-time clock, audio recording for the microphone, power management for the power chip.
For anyone writing an application that displays altitude or weather, the distinction matters more than it looks. A pressure sensor with a centimetre-scale figure is not a barometer, and a datasheet link that shows two orders of magnitude of range will change what you build on top of it.
The documentation site is in the firmware repository, and the licence file is spelled differently
Two small facts about the repository's shape.
First, the documentation lives in the same repository as the firmware. There is a website directory at the root, and the four documentation pages the README points to are the getting-started guide for the development kit, a toolchain and compiling page, a page on writing applications, and the hardware design documentation.
That means the docs are versioned with the firmware and can be read at the commit you are building. For a project whose documentation has to track a moving board design, that is the right arrangement, and it is also why the README is thin: the detail lives in the site rather than in the file.
Second, the licence file at the root is spelled with a c, not an s. The licence itself is the GNU General Public License, and the badge at the top of the README points at the same licence text, so nothing is ambiguous about the terms.
The spelling will still break a script that looks for the conventional file name. This is the kind of detail that costs an afternoon once and then gets hardcoded.
The newest release is seven months behind the branch, and two of three have titles
The three newest releases tell you where the project is.
The newest is version 0.8.1, titled with two things it fixed: automatic detection of the real-time clock, and compatibility with the development kit's battery. The one before it is version 0.8.0, untitled. The third is version 0.7, titled as the initial test firmware release for the development kit.
Those dates run from late 2025 to March 2026. The last push to the default branch main is dated 2026-10-02, about seven months after the newest tag.
So the firmware has moved considerably past anything you can install from a release, which is consistent with the project's own position that the hardware is still being developed: firmware on an unreleased board is expected to move.
The repository root also carries two directories that describe hardware bring-up rather than the application: one for power measurements and one for production testing, plus a resources directory and an editor configuration directory that is checked in. Those three are what a project looks like when firmware is written against physical boards on someone's desk.
Editorial conclusion
Use ZSWatch if you want to read firmware that drives real sensors and a real display, and if you are prepared to learn an RTOS rather than just read a library. The hardware description is unusually complete for an open hardware project: every part is named with a datasheet link, the board design is in an open format, and the extension board is documented down to the connector part number. Three things to check before you commit. What you actually need to buy, because the finished watch is not available and the recommended starting point is a development kit at $99 from a distributor, with the battery optional. How you talk to a phone, because the two platforms are not equivalent: the iOS app is on a store and is the recommended route, while the Android app is experimental and behind an invite, leaving a third-party application as the stable recommendation. And where the design might still move, since the project itself says the final miniature hardware is still being developed and that the health extension board's design, bill of materials and firmware support may change.
Frequently asked questions
What is ZSWatch?
It is an open-source smartwatch built from scratch, both hardware and software, on the Zephyr real-time operating system, which is where its name comes from. It is GPL-3.0 licensed and its hardware is designed in KiCad across four separate board repositories. Full documentation is published from a site maintained in the same repository, and the default branch was last pushed on 2026-10-02.
What hardware does a ZSWatch contain?
A Nordic dual-core wireless chip on a u-blox module with 512 KB of RAM and 1 MB of flash and a 30 MHz SPI for the display, a 240 by 240 round touch display, a Bosch motion sensor for gestures and step counting, a Bosch pressure sensor, a magnetometer, 64 MB of external flash, a light sensor for automatic brightness, a real-time clock, an I2S microphone, and a power management chip. The speaker requires the separate health extension board.
How do I start developing with ZSWatch?
With the development kit, which costs $99 and is ordered from a named electronics distributor. It has the same chip, sensors and display as the finished watch, plus breakout headers, USB-C with debug and serial access, power measurement headers and a debug header, and everything except the battery is included. The finished miniature watch hardware is still being developed.
Does ZSWatch have a phone app?
Two routes, and they are not equivalent. On iOS the official companion application is on the App Store and is the recommended route, and the watch also supports two of Apple's own services natively. On Android the companion application is described as experimental and currently requires invite access requested through a chat server or email, and the stable recommendation is a third-party application hosted on a different forge.
Can I write my own watchface for ZSWatch?
The watch has an application picker with an extensible application framework, and the README links the source directories for several applications including settings, music control and a compass. It also supports watchfaces originally written for a different microcontroller family, contributed by a named person, with a fork linked for details, which implies a translation layer between the two graphics stacks.
Is ZSWatch still being worked on?
The repository is not archived and the last push to the default branch main is dated 2026-10-02. The newest release is version 0.8.1 from 2026-03-12, titled with real-time-clock auto-detection and development kit battery compatibility, followed by an untitled 0.8.0 and an initial test firmware release from 2025-11-26, so the branch sits about seven months past the newest tag.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/zswatch-zswatch)Star history chart for your README
[](https://hysenlabs.com/projects/zswatch-zswatch)Was this useful?