Quick Start

Test out the TelemetryTV media player in your browser (Chrome, Firefox or Edge) by visiting https://player.telemetrytv.com and pairing it.

Deploy our ChromeOS app on a ChromeOS device by downloading it from the Google Play Store.

Deploy our Windows app on a Windows 10 device by downloading it from the Windows App Store.

Demo and Testing

If you're looking to demo TelemetryTV you likely don't yet have a dedicated hardware device and TV in order to deploy on. The easiest way to demo what a device is like with TelemetryTV is to use the Progressive Web Application by visiting it in a compatible browser (latest Firefox, Chrome and Edge -- Safari or other browsers are not supported):

From there, you'll be presented with a pairing code and will be able to enter this code on the TelemetryTV "Devices" page to pair the browser with TelemetryTV.  From then on you'll be able to control what the browser displays just as if it were a physical device attached to a TV.   When you revisit the URL, it will continue to display this playlist. There is no need to re-pair.

You can also use this URL to test your playlists as you work with TelemetryTV in the future.

Deploying your First Device

Once you've decided to adopt TelemetryTV and wish to deploy it on TV's through out your organization, you'll need to acquire hardware to deploy it on.  Specifically what hardware you should acquire will depend on the platform you decide to use for deployment.  TelemetryTV supports two hardware platforms based on ChromeOS and based on Windows 10.  There are tradeoffs associated with each platform and which one is appropriate for you depends on your particular environment.

Automatic Provisioning vs Pairing

TelemetryTV can be deployed at scale on hundreds or thousands of devices. Manually pairing devices can be cumbersome if you're doing many devices. However, setting up automatic provisioning takes some significant knowledge and work so there's a balance between ease of use and automation. 


TelemetryTV has a ChromeOS player app available on the Google Play Store.
ChromeOS is an operating system by Google that runs on ChromeOS devices (Chromeboxes and Chromebooks).  For TelemetryTV we support deployments on Chromeboxes and encourage the use of Chromeboxes that are designed for digital signage along with Google Enterprise management systems.

ChromeOS provides the most inexpensive hardware to deploy at scale and is ideal if you wish to configure automatic provisioning of devices. 

However it doesn't handle video walls larger than two screens, the hardware is lower end and less performant than what you can get under Windows 10, and it will not automatically start into TelemetryTV on boot when only using pairing.  

We therefore recommend ChromeOS only if either you are an existing Google device user or need the lowest cost deployment and wish to invest in learning and adopting Google Enterprise.  Otherwise use Windows 10.

For more information on ChromeOS devices please see our ChromeOS device deployment guide.

Windows 10

TelemetryTV has a Universal Windows Platform player application available on the Windows app store. This application will work on Spring 2018 releases of Windows 10 and later.  Please make sure your version of Windows 10 is up to date.

Windows 10 provides a huge range of possible hardware to deploy on.  However the hardware is not standardized and each specific configuration is going to require testing on your behalf.  

You can easily place Windows 10 in assigned access mode and set the TelemetryTV app to start on boot. Additionally, using supported hardware and display-stitching software with Nvidia, AMD or intel drivers, you can create video walls of unlimited size.
We recommend Windows 10 for users of small deployments (up to 10's of devices) who haven't already invested in the ChromeOS device ecosystem. For larger deployments you'll find that ChromeOS devices are generally cheaper and easier to manage, though there is an investment and technical challenge to learn how to use the ecosystem.

For more information on deploying on Windows 10 please see our Windows 10 device deployment guide.

Did this answer your question?