WristBridge: Wear OS Data
Turn manual values, Tasker updates, and supported HTTPS JSON data into native Wear OS complications, with phone-first setup and watch-local cached state.
Coming Soon to Android + Wear OS
WristBridge: Wear OS Data is currently in active development. The features listed below represent the planned scope. Want to know when it launches?
Notify me when this launchesPlanned Features
- Create manual/custom values on the Android companion and synchronize them to the paired Wear OS app
- Accept user-configured Tasker values through the supported Tasker/Locale plug-in surface
- Read supported scalar values from user-configured HTTPS REST/JSON GET endpoints on the phone
- Bind WristBridge sources to native Wear OS SHORT_TEXT, LONG_TEXT, RANGED_VALUE, and GOAL_PROGRESS complication types where the watch face supports them
- Render complications from watch-local persisted state rather than performing remote network acquisition during a complication request
- Preserve the last valid snapshot when a source refresh fails so stale or error state can be shown without fabricating a current value
- Keep REST credentials on the Android phone in Android Keystore-backed encrypted storage; credentials are not synchronized to the watch
- Use durable versioned Wear Data Layer state synchronization between the phone and watch
- No WristBridge account or developer-operated cloud backend is required for the current V1 architecture
- Current source contains no third-party analytics or crash-reporting SDK; production release qualification is still in progress
Frequently Asked Questions
Is WristBridge a watch face?
No. WristBridge is a data-source utility. It supplies values through native Wear OS complications that compatible watch faces choose how to render.
Does WristBridge support Tasker?
Yes. The current implementation includes a Tasker/Locale setting plug-in path for sending bounded values into configured WristBridge sources.
Can WristBridge show JSON API data?
Yes. The current phone implementation supports bounded HTTPS GET acquisition and constrained JSON scalar extraction. Network acquisition happens on the phone, not during watch complication rendering.
What happens if my phone or network is temporarily unavailable?
The watch complication renders from its local persisted replica. WristBridge preserves the last valid synced snapshot and represents freshness or error state instead of inventing a current value.
Does WristBridge send my values or API credentials to a developer server?
No WristBridge-operated backend is required for V1. REST requests go to endpoints you configure, and REST credentials remain on the phone rather than being synchronized to the watch.
Is WristBridge available on Google Play now?
Not yet. The repository is still in release qualification, so this page intentionally describes WristBridge as coming soon until a public Play release is verified.
Resources
Submit a Bug Report
Found an issue with WristBridge: Wear OS Data? Let me know the details below.
