@gmt Now that’s not strictly true is it? RoonSpeakers is already released and working, it is in the audio path of my MacMini acting as a remote client. I fully appreciate the staggered release of RoonSpeakers to all and sundry, not much point doing that unless there are apps to control it on other hardware.
We aren’t artificially holding this stuff back in order to time things better or “stagger” releases.
An early prototype of RoonSpeakers was snapshotted and used to implement private zones. This was done in a fairly quick way shortly prior to the 1.0 release because it was a feature that we thought was important to launch with. Back in the beginning of this year, the RoonSpeakers code was working well enough to satisfy that simple, constrained use case. That doesn’t equate to a suite of standalone RoonSpeakers apps for the various platforms waiting in the wings.
While the protocol is relatively mature, the implementation of the “real RoonSpeakers” that’s coming later this year is quite different under the hood. It has been re-implemented in a way that’s friendly to hardware manufacturers, lighter-weight for mobile platforms and embedded devices, and in a way that allows for future evolution in a world where many different companies are managing slightly different implementations. Most of this work is not directly related to streaming audio, but it’s still required to release that stuff.
Anyways, like everything else. When it’s ready, it will be released. We appreciate your patience 