A flexible cross-platform WebRTC client framework based on GStreamer.
OpenWebRTC is built on the belief that the WebRTC standard would transcend the pure browser environment and that native apps, implementing the same protocols and API's, would become an important part of the WebRTC ecosystem. This is especially true on mobile platforms where native app distribution is often preferred over pure web apps. Native OpenWebRTC apps can either talk to other native apps or browsers that support WebRTC. OpenWebRTC can also provide the WebRTC-backend to web browsers.
Having independent, interoperable, implementations is important for the health of any standard, and WebRTC is no exception. The ambition of OpenWebRTC is to follow the WebRTC standard closely as it continues to evolve.
OpenWebRTC was designed for flexibility and modularity. The bulk of the API layer is implemented in JavaScript, making it super fast to modify and extend with new functionality. Below is a simplified sketch of the architecture.
Applications built on top of OpenWebRTC will be interoperable with popular WebRTC-enabled browsers such as Chrome and Firefox.
Take a look at the Building OpenWebRTC wiki page for information about how to build the framework.
For support, questions and discussions:
- Public mailing list
- Twitter: @OpenWebRTC
- IRC - irc://chat.freenode.net/openwebrtc
- OpenWebRTC blog (maintained by Ericsson Research)
- Issue tracker
Bowser is a mobile browser that uses OpenWebRTC as a WebRTC back-end. As you can see here, Bowser is in fact a very thin layer of UI code on top of OpenWebRTC.
We are also writing some example code and applications to help you get started using OpenWebRTC on various platforms.
Before being released publicly, OpenWebRTC has been used by Ericsson Research to build several research prototypes such as this and that.
OpenWebRTC is released under BSD-2 clause. See LICENSE for details.