Whether to have recording capability in your WebRTC video or audio application is incredibly important to decide on BEFORE you build. You must also consider how much recording, recording layouts, where and how long you keep it, and how secure it needs to be. Let’s look at how recording affects your app’s architectural choices, as well as the question of recording as composite or individual streams.
There are a variety of ways you can use traditional telephony in your WebRTC video app, as well as different architectures you can choose to support it from commercial to open source. Let’s explore the reasons you might want to integrate a dial-in or dial-out capability into your WebRTC video or audio application and look at a sample architecture.
Even a custom development shop like ours often uses a CPaaS solution when our clients need to get to market quickly or require a large range of communication options within their WebRTC application. Vonage’s comprehensive suite of Communication APIs is a definite go-to for us. We even built it into our own SimplyDoc Telehealth Starter Kit.
The Amazon Chime SDK allows developers to quickly add messaging, audio, video, and screen sharing capabilities with the Amazon Web Services infrastructure as its backbone. Let’s explore its core functionality and try building a simple videoconferencing app.
