We're looking for your feedback on Vivox documentation

Hi everyone, as we continue to look into ways that we can make communications implementations easier we’ve heard the feedback that our documentation can be improved. In an effort to focus that we’re looking to hear from you on topics that proved difficult. Whether a page was hard to find, understand, or if it was a topic we didn’t cover in enough depth we’re hoping to use this thread to surface the areas we can improve.

While it isn’t guaranteed that everything posted here will be addressed in the short term, we will be reviewing everything you share with us. In addition to this thread we also wanted to highlight that you can also always provide docs feedback at the bottom of any page.

Link to documentation overview page

5 Likes

You should start with the mentality first.

We would expect in a post like that, to see a link to the documentation.

Edit: Thanks for adding the link.
I provided feedback directly on the pages.

1 Like

Taps in Unity have been a major problem and I’m still dealing with figuring them out. More examples on different use cases would be extremely helpful than just reading how they should work.

Implementing a multiple channel system has been taxing with one using participant taps and another using channel taps and then trying to implement local volume/mute changes on top of that has been particularily difficult.