A watch collection is more than a shopping list. It is purchase dates, reference numbers, who serviced a piece, and whether it is running fast or slow this month. Spreadsheets work, but they are easy to neglect. Social apps are fun, but they are not always where you want a full private inventory.
Zen Horology is our answer for iPhone and iPad: a single vault that treats your watches like the valuables they are. Add what you own, log how each one performs, sync checks against precise time when you want, and keep the lights-on details in one dark, readable interface. It is live on the App Store, not a future teaser.
Why we built it
We kept hearing the same friction from collectors. Photos live in the camera roll. Specs live in email. Timing notes live on scraps of paper. The moment you ask, "Which one had the bracelet swap in 2022?" nobody wants to hunt three apps deep.
So the goal is simple: reduce shame around organization. You should be able to open one app after dinner, add a quick accuracy reading, and trust that tomorrow the history is still there. No feed, no performative flex, just your bench and your timeline.
Privacy and offline-first habits
Your watches are personal. So is the spreadsheet of what you paid, what you would sell for, and which box lives in the safe. Zen Horology is designed around local storage first. You are not logging into our servers to see your own Submariner. Exports are there so you can keep a copy under your control.
If you want the full legal wording, the privacy policy and terms on the app pages spell out subscriptions, billing through Apple, and what we do not collect.
What you can do in the app
You do not need a lecture on escapements to use the product. At a high level, Zen Horology helps you:
- Organize watches with the fields collectors actually use, not a toy template
- Track accuracy over time and compare against a reliable time source when you choose
- Keep notes on service, provenance, and the small details you would forget in six months
- Search and filter when the collection outgrows memory
- Export to CSV or JSON when you want a backup or to move data elsewhere
Who it is for
If you rotate a few mechanical pieces and like seeing drift charts more than scrolling ads, you are the audience. If you run a small desk where friends bring watches for quick regulation checks, the same structure applies. If you only want a single countdown timer, other tools may feel lighter.
How this fits zenproducts
zenproducts builds apps where the data matters: Zen Slate for notes, Zen Passwords for credentials, and Zen Horology for the shelf of metal and glass you actually touch. The through line is local-first where it fits, honest limits, and copy you can read without a law degree.
Try it
Start on the Zen Horology page for screenshots, the full feature list, and App Store details. Questions welcome at hello@zenproducts.ai.
The problem a watch owner actually has
Collections grow sideways. A watch arrives, the box goes in a drawer, the receipt goes in an email, the service is remembered as "a few years ago", and the serial number exists only on the caseback. None of that is a problem until an insurer, an heir or a buyer asks a specific question.
The second problem is quieter. A mechanical watch tells you when it needs attention, in the form of a rate that has drifted or an amplitude that has dropped, and almost nobody is measuring, so the signal arrives as a watch that has "suddenly" gone wrong.
Why these two belong in one app
They look like separate jobs and they are the same record. A timing run is only meaningful next to the service history, because a rate of plus eight seconds means one thing on a watch serviced last year and something else on one last touched in 2011. Splitting them across a spreadsheet and a timing tool is how both end up unused.
- The catalogue answers what you own, what it cost and what proves it.
- The timing history answers how each piece is behaving, and whether that is changing.
- Together they answer the only question that matters in practice: which watch needs attention next.
Why it stays on the device
A watch catalogue is an unusually sensitive document. It is an itemised list of portable valuables, with serial numbers, purchase prices and an implied address, all in one file. It is the exact shape of thing that is damaging in a breach in a way that most personal data is not.
Keeping it on the phone, with export when an insurer or a solicitor genuinely needs a copy, means there is no server holding a directory of collections to be breached in the first place. That is a structural answer rather than a policy one, which is the only kind worth relying on.
Where to start with a collection you already own
- Enter the watches you would miss most first, rather than working in the order they sit in the box.
- Photograph the caseback as well as typing the serial. The photograph is the evidence, the field is the search.
- Take a baseline timing run on each while it is fully wound, in dial up and crown down. Today is the reference every future run is compared against.
- Record the last service date even where the honest answer is that you do not know.
- Export once when you are done, and keep that file somewhere other than the phone.
