01
Persistent receiver pairing
Pair the six-digit code once. The Google TV app retains its device credential, selected board and cached release, then opens directly into playback on later launches.
Player · Android TV / Google TV
Pair once, then launch directly into your screen.
The internal Google TV APK is ready for emulator and hardware QA. It keeps the paired screen across launches, renders through the hardened browser player, and provides a small D-pad menu for resume, screen switching, forget and re-pair, recovery, and diagnostics.
Cloud basedAccess anywhere
Design onceUpdate in real time
Relay everywhereAny screen, any size
Reliable & secureOffline playback built in
Internal receiver flow
Pair, play, switch, recover.
The internal APK and emulator flow are testable. Signed store distribution and physical-device certification are not claimed yet.android tv
APK ready for QA01
Install internal APK
QA BUILDGoogle TV debug flavor from local Gradle or CI
02
Pair once
SAVEDClaim the six-digit code and select a board
03
Play and manage
D-PADBack opens resume, switch, and forget controls
04
Store distribution
NOT PUBLICNo public Google Play listing is claimed
OUTPUTAssigned Canvas Relay board
Browser available · native shell in development
Internal Google TV APK builds are available for emulator and hardware QA. Google Play Store availability is not claimed.
What is usable now — and what the source shell means
02
Small TV control menu
Press Back during playback to resume, switch to another published screen, or confirm Forget this TV and return to a new pairing code.
03
Browser renderer in the WebView
The shell does not replace scene and widget rendering with unbuilt adapters. WebView content follows the same browser compatibility strategy as the web player.
04
Test the exact TV hardware
Built-in browsers and system WebViews vary. Validate startup, fullscreen behavior, recovery, storage and media playback on the device you will install.
05
No Play Store badge
Development source and a locally built APK are not Store distribution. This page will not show a Play Store availability claim without a public listing.
06
Existing entitlements only
The development shell is playback/access software. It disables native purchases and does not add checkout or an external upgrade prompt.
Keep exploring
Compare TV migration paths
Compare browser, Google TV, Fire OS and Vega targets without treating them as one interchangeable app.
Read more →Browser player
See the fully supported desktop-class browser-player behavior and offline/recovery model.
Read more →Raspberry Pi
A stronger fully supported choice for unattended installations today.
Read more →Questions, answered
01Is there a native Canvas Relay Android TV app in the Play Store?+
No. The repository and CI produce an internal Google TV debug APK for emulator and device testing, but Canvas Relay does not claim a signed Play Store release.
02Can I still use Canvas Relay on Android TV now?+
Yes. Install the internal Google TV APK, pair its six-digit code once, and it opens the saved screen directly on later launches. Back opens controls to resume, switch to another published screen, or forget and re-pair the TV.
03How does the development shell render widgets?+
It is a hardened native TV shell around the browser renderer. Widgets therefore use the browser strategy inside its WebView; Canvas Relay does not claim a separate unsupported native widget adapter.
Try the screen before you commit to the player.
Design in the no-account editor, then validate the hardware path that meets your deployment needs.
Try the editor — no account neededFree plan includes one live screen. No credit card. No trial clock.