# WatchLink โ€” reliable Apple Watch โ†” phone messaging (and cross-platform capable) **URL:** \ **Category:** Related Projects\ **Tags:** bluetooth, ios, watchos, swift-package, networking\ **Created:** [April 21, 2026, 5:18pm UTC](https://forums.swift.org/t/watchlink-reliable-apple-watch-phone-messaging-and-cross-platform-capable/86154 "2026-04-21T17:18:14Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![tareksaeed](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/tareksaeed/32/45148_2.png) [@tareksaeed](https://forums.swift.org/u/tareksaeed)\ **Post date:** [April 21, 2026, 5:18pm UTC](https://forums.swift.org/t/watchlink-reliable-apple-watch-phone-messaging-and-cross-platform-capable/86154/1 "2026-04-21T17:18:14Z")
Open-sourced WatchLink today. It's a Swift 6 package that replaces WatchConnectivity with a dual-transport layer: BLE for service discovery, HTTP + SSE for data, and WatchConnectivity running in parallel as a third transport. Every message is framed, acked by the receiving device, and dedup'd by frame ID. Took our production reliability from 60% to 99% three years ago. Three modules: - WatchLinkCore: protocol layer, zero platform dependencies - WatchLink: Watch-side client - WatchLinkHost: phone-side host (HTTP server built on Network.framework, no external dependencies) Swift 6, no dependencies beyond what Apple ships. Because the host-side protocol is just HTTP + BLE, it's cross-platform capable. The v1 release is Swift only but the protocol is trivial to reimplement in any language. Android is planned. Write-up with the architecture and story: [WatchConnectivity was failing 40% of the time. So I stopped using it. โ€” tarek-builds](https://tarek-builds.dev/p/watchconnectivity-was-failing-40-of-the-time-so-i-stopped-using-it/) Repo: [GitHub - tareksabry1337/WatchLink: Reliable real-time messaging between Apple Watch and phone. Dual-transport (HTTP + WatchConnectivity). Cross-platform capable. ยท GitHub](https://github.com/tareksabry1337/WatchLink) Feedback welcome.