Roon Remote Chromebook or Browser support

We have no plans to do this at the moment.

Keeping our client software unified on top of one technology stack crucial to making forward progress. As soon as we fork and have to maintain two or more independent fully-functional client packages, everything we do slows down noticeably and permanently.

We evaluated HTML5/JS as a potential “unified” platform target many times over the years while developing Roon, and each time we do a serious evaluation, we find that the performance isn’t adequate to execute the types of UI designs that we like to build.

I think if this were to happen it would be based around something like NaCL since that could avoid starting from scratch.