Voxeet provides a platform for unified communications and collaboration. In-Flow Communications refers to the combination of voice, video, and messaging integrated into your application in a way that is cohesive for your end-users. This is in contrast to out-of-app communications where users must stop using your application and instead turn to third-party tools.
By integrating the Voxeet SDK into your application you can provide better in-flow communication experiences and retain your audience. Let's review a few key concepts for how in-flow communications can be incorporated in your application.
As the 3D Immersive Sound Demo illustrates, this refers to the ability to separate the audio from multiple participants on a call. This helps balance the dynamics of a conference so that all participants can be heard and avoids one person talking over another. It creates a more natural experience like being in the same room.
There is no additional implementation needed to enable this feature, it's part of all calls initiated with the Voxeet SDKs.
Voxeet supports HD (720p30) video calling for 1:1 and multi-party conferences.
Content sharing is a feature that enables users to present what is on their screen with everybody in the conference. This is important for collaboration as it allows for things like presentations, whiteboarding, peer review, etc.
Voxeet supports screen share, file and video sharing. You can learn how to use this feature on various platforms with the SDK: Share screen.
Voxeet supports both HLS and RTMP streaming through the REST and Webhooks APIs. RTMP is useful for streaming with service providers like Youtube and Facebook. This feature allows customers to stream their conference out to thousands of viewers with minimum programming.
Voxeet supports recording feature and provides the customization flexibility for customers to create unique recording experiences for their users. Refer to this article for more information.
There is support for Broadcast Messages that facilitate sending data to the clients for all conference participants. This could be a JSON, XML, or simple string that triggers behavior on other clients.