Vivox Product Update: Recent Releases and What’s Coming Next
Hi everyone!
We wanted to share a quick update on some of the latest Vivox voice chat releases, along with a preview of features we’re working on next.
Recent Releases
Real Time Recording
We recently introduced Real Time Recording, a new feature that streams voice data in real time from the Vivox backend to external services. This enables developers to capture voice data for use cases like analytics, moderation, compliance, or storage.
Learn more in the docs:
Vivox Building Blocks
We’ve also released Vivox Building Blocks: ready-to-use Unity prefabs that make it faster and easier to add Vivox Voice and Text to your Unity game. This also includes an audio device selector, making it simple to support input/output device selection in your settings menus.
Docs:
Global Call Quality Dashboard
We now offer a Global Call Quality Dashboard, which gives developers an objective view of call quality around the world, including usage trends and average quality scores by country. This helps teams better understand player experience across regions and make more informed decisions.
Upcoming Features
Here’s a look at some of the features currently on our roadmap:
Zero Downtime Upgrades
Vivox upgrades will no longer require maintenance windows on customer domains, reducing disruption and making service updates more seamless.
Unified SDK
We’re working toward feature parity across Unity, Unreal, and Core SDKs, helping teams build across engines with a more consistent Vivox experience.
Voice Fonts
This upcoming feature will allow users to customize or alter their voice in real time, opening up new possibilities for gameplay, identity, and social experiences.
Message Translation
We’re also exploring real-time text message translation between clients, helping players communicate more easily across languages.
We’d Love Your Feedback
Which of these upcoming features are most interesting to you?
And for roadmap visibility: is Zero Downtime Upgrades something you’d want called out publicly, or is that less important from your perspective than end-user-facing features?
We’d love to hear what would be most valuable for your team.