Feature Request: Per-App Notification Vibration Control + Watchface/Complication Builder for CMF Watch Pro 2 (Nothing X)
1. Per-app vibration/DND control
Nothing X currently only offers two DND modes on CMF Watch Pro 2: Full DND (blocks everything) or Scheduled DND (blocks everything during set hours). There’s no way to silence vibration for a specific app while keeping calls, texts, and other notifications working normally.
This matters most for health-monitoring use cases: apps that mirror glucose readings, heart-rate alerts, or other frequently-updating health data need to reach the watch screen (so the reading is visible at a glance), but shouldn’t vibrate every single update — that’s a buzz every few minutes, all day. The old CMF Watch app had a similar limitation, but with Nothing X now being the unified platform going forward, this is the right moment to add proper per-app notification control: separate toggles for “show on watch” vs “vibrate,” the same way Android itself already lets you configure per-app, per-channel importance on the phone side. It’s a small addition that would make the watch dramatically more usable for anyone monitoring recurring data (health apps, smart home alerts, delivery tracking, etc.) without forcing an all-or-nothing choice between missing important alerts and being buzzed constantly.
2. Custom watchface/complication builder
Right now, watchface customization on CMF Watch Pro 2 is limited to swapping a background image — there’s no way to add live data fields (complications) beyond the fixed built-in widgets. A watchface builder (web-based or as part of Nothing X) that let users add custom data complications — pulling from notification data, health data, or a simple API/webhook — would open up the watch to far more personal use cases: displaying CGM/glucose data, insulin pump status, or other health metrics directly on the watch face rather than only via notification. Many competing platforms (Garmin Connect IQ, Wear OS complications, Fitbit/Gadgetbridge) already support this kind of third-party data on the watch face itself; it would be a meaningful differentiator for Nothing X to offer even a basic version of this.
Both of these would make the platform meaningfully better for health-tracking use cases without requiring deep architecture changes — just more granular exposure of settings that likely already exist internally.
