No doubt you’ve seen one of the numerous headlines talking about “mobile first” design and development. Whether or not you agree with this approach, it’s undeniable that mobile is on the rise – and WebRTC is part of that growth. Just as on a desktop, WebRTC can be used on Android mobile devices with supported browsers such as Chrome, Firefox and Opera. (Unfortunately, the technology does not yet work with iOS because Apple requires browsers to use its own Web renderer.)

 So how can developers make the most of mobile WebRTC? While it’s possible to create a mobile optimized page that works on Chrome, the preferred usage model for the mobile model in most cases is to use a native application delivered via an app store. WebRTC can be incorporated into native applications, but it does take some work and expertise. If you choose to go this route for your WebRTC application, you have two choices:

  1. Porting the source code from scratch or
  2. Use a software development kit from someone who has already done the port.

If you choose the former, the WebRTC Project has a bunch of codes available to make it easier. Unsurprisingly since the project is largely contributed to by Google, Android libraries are much more mature than the iOS ones.

Alternatively, developers could wait until this aspect of WebRTC matures a bit. WebRTC is also being added to Chromium, the internal browser that an Android app can call when it needs a web render, which will make it much easier for most Android app developers to use WebRTC.

Still, if you’re too impatient to wait, there are several high profiles examples of WebRTC being embedded inside native mobile applications today. It will get easier, but there’s no need to hold off if you can’t wait. After all, you are supposed to be designing your application to be mobile first.

Should you have interest in learning more about WebRTC and how this disruptive technology can work for you, contact our experts at