Capacitor lets you write a single web‑based app for iOS and Android, but Wear OS has no Capacitor runtime, so the watch side must be built in native Kotlin. To connect the two, you use Google’s Wear OS Data Layer API (play‑services‑wearable) and the Capgo watch plugin, configuring a matching capability string, identical application IDs, and the same signing certificate. The bridge enforces strict security, and mismatched keys silently return an empty node list, making debugging tricky.
Three communication paths are covered: sendMessage for instant actions, updateApplicationContext for a small, persistent state (limited to ~100 KB and ignoring unchanged payloads unless you add a unique field), and putData for queued, guaranteed delivery. The episode also explains emulator requirements, Play Services dependency, versioning JSON payloads to handle uneven update cycles, and best practices for keeping the watch app thin while using Capgo to hot‑swap phone code.
Topics:
- Configuring capability strings, app IDs and signing certificates for Data Layer security
- Choosing the right Data Layer method: live messages, context sync, or queued user info
- Handling emulator setup and Play Services requirements for testing
- Versioning JSON payloads to maintain compatibility between fast phone updates and slower watch releases
- Keeping the watch side minimal and using Capgo for instant phone‑side hot updates
Full article
https://capgo.app/blog/capacitor-wear-os-app/