When I attended the SDP Summit last week, I joined the WebRTC workshop. WebRTC is a promising HTML5 standard that enables real-time multimedia communication directly in web browsers. In this article I provide a clear technical introduction to WebRTC, explain its disruptive potential across the communications industry, and discuss what those changes could mean for carriers. At the end I also list authoritative WebRTC API references and a practical Getting Started guide.
Technical introduction to WebRTC
WebRTC (Web Real-Time Communication) is an open HTML5 framework that enables peer-to-peer streaming of audio, video and data between browsers without requiring plugins when the browser implements the API natively (for example, Chrome and other modern browsers). WebRTC exposes JavaScript APIs that bring VoIP and real-time media capabilities directly into web applications.
Conceptually, WebRTC simplifies access to codecs and media handling by encapsulating four main components:
- Session management and signaling (handled outside the core spec, leaving identity and signaling choices to developers)
- Voice engine (media capture, encoding and decoding)
- Video engine (capture, rendering and codec support)
- Transport protocols (secure, adaptive transport like SRTP/DTLS and NAT traversal via ICE/STUN/TURN)
The WebRTC architecture separates the media and transport layers from the application layer, enabling developers to choose signaling and identity mechanisms that match their use case. For a deep technical reference, the official WebRTC specification and architecture pages provide comprehensive detail.
Key characteristics
- Peer-to-peer media paths for low-latency audio and video.
- Native browser APIs for media capture, encoding, and playback without plugins.
- Transport and security primitives designed for the open web (DTLS-SRTP, ICE/STUN/TURN).
- No mandated identity layer — developers can use email, OpenID, social logins, phone numbers (MSISDN) or proprietary IDs.
Why WebRTC matters: disruptive potential
WebRTC can reduce the need for native apps by enabling full-featured real-time communication from within standard web pages and progressive web apps. This capability threatens to change the landscape that made many over-the-top (OTT) players successful — apps like Skype, WhatsApp, and Viber — because it allows developers to build cross-platform voice and video services using standard web technologies.
Because the core WebRTC spec does not enforce a specific identifier strategy, developers can design services that interoperate across previously closed ecosystems. This flexibility could break down many artificial barriers between platforms, operating systems and device vendors. In practical terms, a WebRTC-enabled web experience could allow a user to call another user on a different service or device simply through standard web signaling and identity mapping. The “open web” nature of WebRTC therefore has the potential to enable more seamless cross-service communication.
What WebRTC means for carriers
On the one hand, WebRTC enables browser-to-browser communication that does not strictly require operator intervention. On the other hand, many WebRTC sessions will traverse mobile networks, representing both a risk and an opportunity for carriers.
Carriers possess several strategic assets that could be leveraged to monetize WebRTC and maintain relevance in a changing ecosystem:
- Network coverage and reliability across large user populations.
- Network-level quality-of-service mechanisms and traffic management capabilities.
- Interconnect and bridging capabilities to link WebRTC sessions with traditional telephony and landline networks.
- Established brand recognition, trusted customer relationships, billing platforms and subscriber data that can support tailored services and monetization.
If carriers can adapt business models, introduce flexible subscription or usage plans, and develop value-added services around bridging, QoS, identity or billing, they have a realistic path to monetize WebRTC traffic. However, the main barrier is organizational agility: carriers must move faster to adapt to market shifts and developer-driven adoption if they want to capture value.
Practical implications and realistic expectations
WebRTC presents a genuine opportunity for both incumbents and new entrants. It could reduce friction for users, enable cross-platform communication and challenge app ecosystems that depend on closed, proprietary boundaries. That said, history shows that technologies hyped as “disruptive” can take time to mature or be displaced by other innovations. The opportunity for carriers is real but not guaranteed; execution, speed and alignment with developer and consumer needs will determine winners.
Resources and getting started
For developers ready to explore WebRTC, the official API reference and Getting Started guides are the best place to begin. These resources cover native browser APIs, signaling approaches, media capture and examples for building WebRTC applications.
Additional recommended reading includes in-depth books and practical guides authored by contributors to the WebRTC specifications and by experienced implementers. These resources provide protocol-level detail, best practices for NAT traversal and TURN deployment, and patterns for integrating WebRTC with existing telephony and backend systems.
In summary, WebRTC is a powerful, web-native approach to real-time communication. It can disrupt current app models and offers carriers both a challenge and an opportunity: by leveraging network strengths, identity and billing capabilities, carriers can gain business from or alongside WebRTC-based services, provided they respond with speed and developer-friendly offerings.