01
Capable TV browser
The available compatibility path: open player.canvasrelay.app, pair the screen and test fullscreen, autoplay, storage, sleep and restart behavior on the exact device. Amazon Silk is the common Fire OS browser route.
Player migration · Fire TV & Android TV
Compare the TV runtime before you move the menu board.
This hub separates the live Google TV direct APK, browser-compatible Fire TV path, and distinct Fire OS and Vega targets. Choose by operating system, distribution channel and real-device QA — not by a generic “TV app” label.
Cloud basedAccess anywhere
Design onceUpdate in real time
Relay everywhereAny screen, any size
Reliable & secureOffline playback built in
Choose the actual runtime
Four deployment lanes that should not be called one app.
Identify the runtime first, validate the exact board and media on that device, and keep the previous player until the replacement survives a full operating day.runtime map
Comparison hub01
Capable TV browser
AVAILABLEPublic compatibility path for Fire TV and Android TV
02
Android TV / Google TV
DIRECT APKSigned direct APK beta; Play Store not claimed
03
Fire OS Android
SOURCEDistinct fireTv flavor; Appstore not claimed
04
Vega OS
SOURCESeparate React Native target; not an Android APK
OUTPUTAssigned Canvas Relay board
Comparison and migration hub
Google TV has a signed direct-download receiver beta, while Fire TV keeps its browser compatibility route and separate Fire OS/Vega source targets. Canvas Relay is not yet listed in Google Play or the Amazon Appstore.
Four paths that should not be collapsed into one
02
Android TV / Google TV shell
The signed direct-download Google TV receiver is live with D-pad controls, pairing persistence, screen switching, recovery and diagnostics. It is a direct beta, not a public Play Store listing.
03
Fire OS Android flavor
The same Android source has a distinct fireTv flavor, preserves API 22 device compatibility and targets API 36 for Fire OS 16. It is not available in the Amazon Appstore.
04
Vega OS source target
Vega has its own React Native WebView project and Amazon SDK build path. It is not an Android flavor, and no Vega Amazon Appstore release is claimed.
A low-risk migration sequence
01
1 · Identify the runtime
Record whether each device runs Google TV / Android TV, Android-derived Fire OS, or Vega OS. Model and OS matter more than the logo on the remote.
02
2 · Validate the board
Run the restaurant menu, videos and live widgets through the browser renderer on the destination hardware. Check legibility, media playback, cache behavior and recovery.
03
3 · Move the assignment
Pair or authenticate the accepted player and assign the same board. Keep the previous screen available until the new runtime has survived a full operating-day cycle.
Platform details and restaurant setup
Android TV / Google TV status
Browser setup, development shell capabilities and the Play Store boundary.
Read more →Fire TV runtime status
Amazon Silk, the Fire OS Android flavor, the distinct Vega target and Appstore status.
Read more →Browser player
Understand the browser renderer that the compatibility path and native WebViews use.
Read more →Restaurant digital signage
Plan menu boards, dayparts and updates independently of the player hardware.
Read more →Display a menu on TV
Build the menu-board workflow before selecting or migrating the TV runtime.
Read more →Questions, answered
01Which path can I install from a TV app store today?+
None is publicly listed in Google Play or the Amazon Appstore today. Google TV has a signed direct-download Canvas Relay receiver beta; Fire OS and Vega continue to use their browser/development paths.
02Is Fire OS the same target as Vega OS?+
No. Fire OS uses the fireTv flavor of the Android WebView project. Vega is a separate React Native project built with Amazon's Vega SDK. An Android APK cannot be presented as a Vega package.
03Can I move a restaurant menu board between these players?+
Yes. Boards, schedules and media stay in Canvas Relay. Validate widget and media behavior on the destination, pair or authenticate that player, then assign the same published board instead of recreating the menu.
04Do the native development shells use different widget adapters?+
No. The Android TV, Fire OS and Vega shells use WebViews around the browser renderer, so widgets follow the browser strategy. Roku remains different because it uses a native Relay/SceneGraph capability set.
Keep the restaurant board. Change only the player.
Build and publish the menu once, then validate the runtime that fits each TV before you migrate the screen assignment.
Try the editor — no account neededFree plan includes one live screen. No credit card. No trial clock.