WebRTC World Feature Article Free eNews Subscription

October 17, 2013

WebRTC Developers Use Select Tools as API Moves Forward

WebRTC (Web Real-Time Communication) is moving forward.

WebRTC is best understood as an API being drawn up by the World Wide Web Consortium that enables Web browsers with real-time communications capability through JavaScript.

An important step in the sector came recently when Oracle unveiled a WebRTC session controller.

When developing WebRTC applications a key concern is which tools to use. That issue was addressed in a recent article from BlogGeek.Me.

For instance, Hadar Weiss of Peer5 told the blog “the most important tool is chrome itself with its debugging capabilities.” That answer was repeated by many in the sector.

In addition, Nicholas Buchanan of OpenVRI said that “for the [development environment] I use VIM (also installed vim syntax recognition for JavaScript, jade, stylus).”

Uffe Bjorklund of XSocekts.net uses “Visual Studio 2012” as a development environment, “not because it is a better env [environment] than others for WebRTC…mainly because our underlying platform for signaling is built on C…When I am on a Mac I use Xamarin.”

It was also reported how Philippe Sultan of Apidaze said they use “C, JavaScript, AS3, PHP (with Symfony).” The tools and development environment include Linux CentOS; vim for editing; autotools; Grunt and PHPUnit for building and testing; and git and svn for versioning.

In another statement, Eric Davies of Priologic said that he uses Netbeans for editing. Colleagues use Eclipse and Textmate. XCode is used for native iOS client and Sublime is used for webstuff.

Also, Chris Matthieu of Twelephone said tools used include: the Sublime 2 editor, iTerm 2 command line, and Git/Github for source code control, as well as Node Inspector for tracing.

And Emmanuel Venisse of Bistri said they use OSX, Linux (and Windows for tests only) when it comes to operating systems. Tools include Intellij, IDEA, Komodo and Wireshark.

There are still many challenges ahead for WebRTC. No Jitter recently reported on some of the challenges for the delivery of WebRTC applications. These include, “lack of a standard video codec across all browsers; different WebRTC implementations in different browsers; the lack of compressed voice codecs; and the lack of any kind of WebRTC support from Apple.”

Even with the new Oracle session controller and the fact that some “technical issues are overcome…the bigger obstacle is to build a business case that will drive enterprise adoption,” No Jitter added.

Hopefully, the challenges will soon be addressed. Because when WebRTC becomes widespread, it will likely revolutionize communications.

Edited by Alisen Downey
Get stories like this delivered straight to your inbox. [Free eNews Subscription]


Free WebRTC eNewsletter

Sign up now to recieve your free WebRTC eNewsletter for all up to date news and conference details. Its free! what are you waiting for.