FickleSticks
Member
As I dive more and more into the Hydros ecosystem, it's become quite disappointing to see the misinformation from CoralVue and it's delivery as to how Hydros works.
Don't get me wrong, I think this is a phenomenal idea, but the fact that you pitch the single-pane of glass management yet fail to provide any documentation and interoperability between the Control and Wave Engine is just downright wrong.
As mentioned in another post about the single power outlet being marketed with features that are not yet available, I feel that CoralVue is pitching their roadmap, not actual delivered features. This past month has been a lot of trail and error since CoralVue has failed to provide detail documents and articles leaving many users in the dark.
It was the initial concepts and ideas that persuaded me to buy into this product, yet I am seriously contemplating boxing this all back up due to the limited documentation and details. I do not want to have to reach out this the forum and / or support every time something is not documented. It's time to work on your Information Experience to the end user experience.
Hopefully you all can get you act together and provide detailed documentation for users who want to make the most of your product. Why offer a command bus interface on the Wave Engine if you can't even add it to a collective? Are we just all alpha / beta testers?
Don't get me wrong, I think this is a phenomenal idea, but the fact that you pitch the single-pane of glass management yet fail to provide any documentation and interoperability between the Control and Wave Engine is just downright wrong.
As mentioned in another post about the single power outlet being marketed with features that are not yet available, I feel that CoralVue is pitching their roadmap, not actual delivered features. This past month has been a lot of trail and error since CoralVue has failed to provide detail documents and articles leaving many users in the dark.
It was the initial concepts and ideas that persuaded me to buy into this product, yet I am seriously contemplating boxing this all back up due to the limited documentation and details. I do not want to have to reach out this the forum and / or support every time something is not documented. It's time to work on your Information Experience to the end user experience.
Hopefully you all can get you act together and provide detailed documentation for users who want to make the most of your product. Why offer a command bus interface on the Wave Engine if you can't even add it to a collective? Are we just all alpha / beta testers?