Why WatchMyCalendar exists

Short version: I bought a Wear OS watch assuming "smartwatch" meant it would know what's on my calendar today. It didn't. So I built that myself.

The moment

The actual trigger was unremarkable: glancing at my wrist before a meeting and seeing an empty space where my next event should have been. My watch model shipped with nothing usable for this out of the box — no real event details, no on-watch calendar view worth the name. Google has since shipped its own Calendar app for Wear OS, but it only works with a Google account and isn't preinstalled on every watch. For everything else — Outlook, Samsung, CalDAV, shared work calendars — the watch is still blind to this day.

Why I built it myself

WatchMyCalendar is a solo project — no team, no investor, no product roadmap decided by anyone other than me and the feedback of the people who actually use it. That shapes everything this app is and isn't:

• No subscriptions. Every tier is a one-time purchase. For an app whose core job is "show me my events," I don't think anyone deserves a recurring payment relationship — including me.
• No background telemetry. No Firebase Crashlytics, no analytics SDK quietly logging in the background. If something breaks, there's a "Report bug" button that opens an email with the relevant diagnostics — with your active consent, not automatically.
• An honest roadmap. The tiers page only shows what's actually built — no feature marketing for things that don't exist yet.
• Honest support expectations. I answer requests myself — usually within a few days, but without a ticket system, a team, or a 24/7 promise behind it. A real bug gets my full attention; a feature request may take some patience.

What's next

The app moves forward in small, shipped steps rather than big announcements. What comes next depends heavily on what people actually miss while using it — not on what looks best in a feature-comparison table against competitors. If something's missing or behaving oddly, tell me — through the feedback channel or directly at support@nuumoo.com. I read it myself.