When WebRTC was first published as open source project in 2011, Google started their mission of making audio and video available through a uniform standard set of APIs. Today, it’s more than an unknown IETF draft and many well-known video-calling tools such as Facebook Messenger, Google Hangouts are based on WebRTC. That is why it’s the perfect time to talk about the beauty of this amazing framework and how to use it natively on Android.
After a short wrap up of the core principles, I will summarize the Pros and Cons of existing libs and approaches (such as Opentok, EasyRTC and OpenWebRTC) to integrate WebRTC into native Android applications. We at Viscopic chose the way of using the chromium library (published by webrtc.org) to realize a multi-platform collaboration solution. This approach is known as having a complex library build process, but it’s worth it. By walking through some code samples, I will show what the library is about and how to implement a basic Android WebRTC application. For all those who are interested in app architecture, I will describe our system design concept of encapsulating application logic (WebRTC signaling, room handling, etc.) into one native core. Maintaining just a single core code base constitutes a flexible solution for realizing scalable distribution on multiple mobile platforms.
What’s next? Finally, I will briefly address latest achievements within the WebRTC world like ORTC and VP9.