Why Chromoting

In this post, I wanted to briefly explain why we chose Google Chromoting as the connnection display protocol for Chromotif Application Delivery Platform?

Good stable technology always finds its way to the customers and gets appreciated. A few stats. from the Chrome Web Store —

  1. Google Chrome Remote Desktop (built using Chromoting) has a 4*+ rating from 32k+ users
  2. Google Chrome Remote Desktop (built using Chromoting) has 59k +1s (or likes)

 

 

 

…wait it gets better. A few stats. from the Google Play Store (for Android) —

  1. Google Chrome Remote Desktop (built using Chromoting) for Android has 4+ rating from 162k+ users. A whopping ~105k of those users have given it a rating of 5*
  2. Google Chrome Remote Desktop (built using Chromoting) for Android has >5M (yes! five million) downloads

 

 

These stats. are as of April 14th, 2017. So you can tell Chrome Remote Desktop (and in turn Chromoting) gets the job done and is loved by users. From a popularity standpoint, here’s another data-point: Chromoting (or Chrome Remote Desktop) is native to Chrome browser. The #1 browser used worldwide. Chromoting is also native to Chromebooks, which make the best thin client or “netbook” style devices IMHO (fast boot, secure, affordable, cross platform — enabled by Chromotif).

 

Now let’s talk a bit about the technology.

  1. The Chromoting protocol technology is built on platform agnostic framebuffer updates as opposed to higher level graphic primitives.  Quite portable. For the 3D aficionados, Chromoting does not currently support 3d, but using 3d applications in shared environment requires massive GPU sharing and GRID computing. That isn’t our use case as yet.
  2. The Chromoting protocol technology has been around for 6+ years, is free for personal and commercial use. Yes, please read that again — free for personal and commercial use. Now compare this fact with expensive protocols like Citrix HDX or ICA, Teradici PCoIP or VMware Blast.
  3. The Chromoting protocol technology is backed by Google. You didn’t know that, did you? Yes, Chromoting is backed by Google.
  4. The Chromoting protocol technology is built on Web standards, like WebRTC , which is optimized for real time communication for browsers and mobile applications.

But most importantly…

The performance of Chromoting protocol, from an end user experience perspective is really good. The protocol is fairly optimized for media content rendering with high frame rate, audio sync, fast scrolling. In head to head comparisons with other proprietary protocols, Chromoting (or Chrome Remote Desktop) stands tall and isn’t a bandwidth hog either. For general purpose 2D applications, the user interaction is snappy. We aren’t saying it, lots of users are, at Slant.

Oh and by the way, in my next post, I will explain how we eliminated the “Single User Only” disadvantage on Chromoting or Chrome Remote Desktop, and how we made it multi-user, enterprise ready. Until then, please keep up the good work, and send the elevator back down…Ciao!