Real-Time Audio & Video Development Guide
Welcome to RC Real-Time Communication (RTC). Our RTC service is built on a room-based model, supporting one-to-one and multi-party audio/video communication. Powered by RC Chat signaling, it ensures stable connectivity during prolonged calls and under weak network conditions.
This page provides a brief introduction to RC RTC capabilities and SDK products.
Client SDKs
RC client SDKs offer extensive APIs with most features ready out-of-the-box. Combined with RTC server APIs, they can fulfill diverse business requirements.
SDK Use Cases
CallPlus, CallLib/Kit, and RTCLib are three flagship client SDKs for RC RTC services:
- CallPlus/CallLib/Kit: Designed for call functionality development
- RTCLib: Core audio/video library for customizable scenarios like conferences or live streaming
| Category | Recommended SDK | Key Difference | Typical Scenarios |
|---|---|---|---|
| Calls | CallPlus, CallLib/Kit | Auto-handled room IDs | 1-to-1/group calls (similar to WeChat calls) |
| Conferences | RTCLib | Pre-agreed room IDs required | Meetings, online interviews, remote notarization |
| Live Streaming | RTCLib | Supports host/audience roles with mic access | Social live streams, product launches, audio chat rooms |
SDK Selection Guide
Choose carefully based on your business needs:
-
For call functionality:
- CallPlus (recommended): Next-gen call SDK with ongoing feature development
- CallLib/Kit: Legacy versions (CallLib = no UI, CallKit = with UI components)
- ⚠️ CallPlus and CallLib/Kit use different backend architectures and aren't interoperable
-
For core RTC capabilities without call features: Use RTCLib alone
Quick recommendations:
- Need just RTC core? → RTCLib
- Building call features with pre-built UI? → CallKit
- Building call features without UI components? → CallPlus/CallLib (CallPlus preferred)
- Need extended functionality? → Explore our plugin ecosystem
We recommend evaluating our quickstart guides and sample projects before development.
Advanced Features
Key RTC capabilities include:
- Cross-room streaming: Multi-host live collaborations
- Call analytics: Detailed periodic call metrics
- Screen sharing: Via custom video streams
- End-to-end encryption: Optional media stream security
- Plugin support: Beauty filters, CDN players, etc.
- Cloud recording: Individual/merged participant recordings for calls/live streams/meetings
- Content moderation: RTC Server transcodes streams for review, with results returned to your app server
Some features require RTC server API integration. Platform-specific support details are available in our SDK and server documentation.
Platform Compatibility
Platform Compatibility
CallKit, CallLib, and RTCLib support mainstream mobile operating platforms with consistent client-side features across multiple devices and cross-platform interoperability. CallPlus currently supports only Android, iOS, and Web platforms.
| Platform/Framework | Language | Supported Architectures | Notes |
|---|---|---|---|
| Android | Java | armeabi-v7a, arm64-v8a, x86, x86-64 | Requires Android 4.4 or later |
| iOS | Objective-C | --- | Requires iOS 9.0 or later |
| Windows | C++, Electron | x86, x86-64 | Windows 7 or later |
| Linux | C, Electron | --- | Recommended: Ubuntu 16.04 or later. For other distributions, consult sales |
| macOS | Electron | --- | Requires macOS 10.10 or later |
| Web | JavaScript | --- | See client documentation for Web compatibility details |
| Flutter | Dart | --- | Requires Flutter 2.0.0 or later |
| uni-app | JavaScript | --- | Requires uni-app 2.8.1 or later |
| React Native | JavaScript | --- | Requires React Native 0.65 or later |
| Unity | C# | Android (armeabi-v7a, arm64-v8a), iOS (arm64, armv7) | --- |
| HarmonyOS | ArkTS, TypeScript | arm64-v8a | Requires HarmonyOS NEXT 0.0.31 or later |
Version Support
Here's the translated version of the source document while strictly adhering to the provided glossary and style guide:
The latest versions of RTC client SDKs for each platform/framework are as follows (--- indicates currently unsupported):
| SDK/Platform | Android | iOS | HarmonyOS | Web | Electron | Flutter | Unity | uni-app | Mini Program | React Native | Windows - C++ | Linux - C |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| RTCLib | 5.6.x | 5.6.x | 1.5.x | 5.6.x | 5.6.x | 5.2.x | 5.2.x | 5.2.x | 5.0.x | 5.2.x | 5.1.x | SeeNote 1 |
| CallLib | 5.6.x | 5.6.x | 1.5.x | 5.0.x | 5.1.x | 5.1.x | --- | 5.1.x | 3.2.x | 5.1.x | --- | --- |
| CallKit | 5.6.x | 5.6.x | 1.6.x | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| CallPlus | 2.x | 2.x | 1.6.x | 2.x | --- | --- | --- | --- | --- | --- | --- | --- |
Note 1: For Linux platform support, please contact RC sales.
Real-Time Communication Server API
The RC RTC server API helps you build backend services that integrate RC's real-time communication capabilities into your app.
Use the server API to integrate RC services into your real-time communication system—for example, obtaining user authentication tokens (Token) from RC, banning users, or removing participants from rooms through your application server.
Go to RC server documentation · Integration Guide »
Real-Time Communication Analytics
Visit the Analytics page in the Console to query and view RTC usage metrics, service health checks, and—after enabling relevant services—business analytics.
RC also provides real-time call quality monitoring tools that visualize quality metrics for each call, helping identify issues and improve troubleshooting efficiency.
RC doesn't utilize customer data. We implement comprehensive data privacy policies. See SDK Privacy Policy.