Essential journey
Sign-in, PC choice, WebRTC video, audio, device-appropriate control, quality, recovery and diagnostics must yield the same user outcome.
PWAfunctional reference
3 private storesApple and Google invite-only
MSIXbuilt Windows candidate
Apple Silicon Macproven Helio sender
Where to watch and control your PC
| Client | Distribution | User parity | Proven limits |
|---|---|---|---|
| PWA · Safari / Chromium | Live beta | Reference: account, PCs, WebRTC, audio, touch/controller, virtual display, launchers, quality and Lab. | Browsers reserve some shortcuts and select decoding. Fallbacks vary by browser. |
| iPhone / iPad · Swift | Private TestFlight | WebRTC video/audio, controller-free touch mode, keyboard, per-PC settings, account, Lab and up to four controllers are coded. | The August 16 build passes 30 simulator tests; this lot still needs distribution and physical iPhone proof. AV1 only when VideoToolbox allows it. |
| Apple TV 4K · tvOS | Private TestFlight | Video/audio, controller, launchers, virtual display and Lab shared with the Swift core. | Controller-first UI: no keyboard/touch. The Lab campaign cannot invent external measurement input. |
| Android / Android TV · Kotlin | Private Google test | Video/audio, touch/controller, quality, virtual display, account and B/A/B Lab campaign are coded. | 82 tests and debug APK passed August 16. RG557 HEVC 1080p measured ~20 ms/frame; Switch mapping remains model-specific. |
| Windows Store · Flutter MSIX | Lab candidate | Same Flutter UI and WebRTC video as the PWA; a reproducible MSIX builds locally. | Not published. Native input remains gated OFF; H.264-WS/HEVC-WS/MJPEG fallbacks lack complete native engines and non-WebRTC audio is absent. |
| Windows native Rust | Separate prototype | Hardware H.264/HEVC, WASAPI and low-level input were proven locally. | It is not the Store client or the full PWA UI; WAN, reconnect and distribution remain unproven. |
| macOS · Nyx client | Browser path | The PWA can receive through compatible Safari or Chromium. | No native macOS Nyx client exists. Do not confuse it with Helio macOS, which sends. |
| Xbox / Linux / SteamOS | Architecture | Shells and plans exist for Xbox/SteamOS. | No publishable app or proven parity. Xbox notably requires ID@Xbox and a compliant GDK transport. |
Which computer can send
| Sender | Status | What works | Deliberate gap |
|---|---|---|---|
| Helio Windows 0.1.115 | Primary beta | Screen/window capture, H.264/HEVC/AV1 depending on GPU, audio, input, virtual display, launchers, diagnostics and signed updates. | Mattéo 5 diagnoses hybrid PCs; a successful probe does not replace a streaming soak test. |
| Helio macOS · Apple Silicon | Technical beta | ScreenCaptureKit, VideoToolbox H.264/HEVC, system audio, mouse/keyboard and WebRTC produced a real ~56 fps session. | No Windows virtual display, Windows launchers, virtual Xbox controller, power controls or self-update. Not published on Mac App Store. |
| Helio Linux | Unavailable | No distributed sender. | Architecture still needs design and proof. |
What must be shared — and what remains platform-specific
Platform integration
Touch on mobile, remote/controller on tvOS, keyboard/mouse on computers and Store constraints remain native implementations.
No fake parity
Missing, gated, build-only or untested features are labelled as such. The site never turns a green build into field proof.
The codec depends on the sender–client pair
H.264
The broadest fallback. It can be less efficient at equal quality, and latency depends heavily on the hardware path.
HEVC
Highly efficient on devices with a good hardware decoder. On a small SoC, decode time can become the limiting factor.
AV1
One AMD → Chrome path has been measured. AV1 being visible in the Lab does not mean universal availability on iOS, tvOS or Android.
How to read the statuses
- Validated / active beta: a real setup worked, with published limits.
- Lab: the path exists or has first evidence, but is not ready to be presented as general.
- Exploration: architecture or prototype only; no product commitment.
Is your device missing?
Include its model, network and intended use in your beta request. It helps us choose the next test runs.