Compatibility
CyanBridge smart glasses compatibility matrix
This is the public source of truth for device support. Supported, experimental and research labels are intentionally different: a brand mention never means every feature or firmware version works.
Last reviewed: 2026-08-23
| Device | Status | Pairing / bridge | Media | Local AI |
|---|---|---|---|---|
| HeyCyan | Supported workflow | CyanBridge includes HeyCyan-oriented connection and media workflows. | Photo/media transfer and companion-app workflows are part of the current integration surface. | CyanBridge can route supported workflows toward local-first or user-selected AI backends. |
| EyeVue | Experimental | Experimental connection, media and device-control work is being validated. | Media sync and preview behavior may vary by model and firmware. | The goal is to use CyanBridge as a bridge to private/local or user-selected AI rather than locking the glasses to one cloud assistant. |
| Meizu MYVU | Experimental | Experimental MYVU/StarV integration work is underway, including reverse-engineered and Android companion paths. | Available controls depend heavily on model, firmware and exposed APIs. | A key CyanBridge use case is connecting MYVU-style glasses to custom local or self-hosted assistants. |
| Meta Ray-Ban | Experimental | CyanBridge experiments with supported Meta Wearables developer interfaces where available. | Access is constrained by Meta's platform permissions and the capabilities exposed to third-party apps. | CyanBridge is exploring workflows where captured context can be sent to user-controlled AI components when platform rules permit it. |
| TuneBuds | Research | Compatibility research is in progress; CyanBridge does not currently claim stable TuneBuds integration. | Capabilities are being mapped across hardware sold under multiple companion-app ecosystems. | The target use case is a vendor-independent bridge to local/private AI where technically possible. |
| MemoMind | Research | CyanBridge is tracking MemoMind workflows and interoperability opportunities; direct stable support is not claimed yet. | Capabilities depend on what the device and companion software expose to third-party integrations. | Privacy-conscious users are a strong fit for CyanBridge's local-first model and personal-dataset workflow. |
How to read the status labels
- Supported workflow: CyanBridge contains an actively used integration path, while exact hardware capabilities can still vary.
- Experimental: an integration exists or is being validated, but users should expect firmware, permission or reliability limitations.
- Research: CyanBridge is mapping the ecosystem and interoperability path; stable direct integration is not claimed.
Machine-readable compatibility data
Developers and other tools can read the same status data from /api/public/compatibility. The endpoint keeps human-facing and machine-facing compatibility claims consistent.
Have a specific model or firmware?
Send the exact glasses model and firmware version so compatibility can be verified instead of guessed.
Continue