Heightening high tech’s profile – interview with Trent Johnsen

As co-founder of Calgary tech start-up Hookflash, Trent Johnsen can’t emphasize enough the power of a little publicity.

The maker of Open Peer, information communication software was named a winner of the 2013 TechRev Innovators of the Year, and the recognition has meant more than just accolades.

“What it did was help validate the work we were doing,” he says. “It brought us credibility.”  And with that came investment. The company has been able to attract more than $1 million in financing — with millions more pending – to build up its fledgling business. Hookflash is now working with two large U.S. cable providers, developing pilot software that could revolutionize the way video, messaging and voice data are shared over the Internet.

Johnsen equates winning the award last October to what the Emmys does for the TV industry or the Oscars for the film industry.
Founded in 2009, TechRev is an initiative of Innovate Calgary — a partnership between the Government of Alberta and University of Calgary.

Read the rest at Calgary Herald

Event: IIT RTC Conference and Expo

The IIT RTC Conference and Expo is a globally recognized collaborative event, where industry and academia connect. Leveraging its unique academic setting, this annual conference brings together technical professionals and business executives from the data and telecommunications industry, standards bodies, policy and regulatory institutions, and academic educators and researchers to promote an open exchange of ideas to lead future development in the rapidly changing field of real-time communications.

Robin Raymond – Hookflash Chief Architect, will be on stage talking about “The Road to RTC Federation”. This is going to be a great talk and is inline with the work we are contributing to in the and Open Peer project and Federated Identities for the Open Web – W3C Community Group .

Watch This: @RobinRaymond builds federated video chat at jQuery Conference Portland on stage!

This is a great visualization of how WebRTC actually functions today.  Robin shows the message flows in a terminal, the source used, very cool! He also touches on all the bits outside of WebRTC that are needed for a secure, ubiquitous and mobile friendly user experience.

The Q&A at the end of the presentation are worth listening to as well.

The demo code used: https://github.com/openpeer/webrtc-demo

Presentation: https://github.com/openpeer/pres-jqueryconf-2013

Rolodex for Identities Mgt: https://github.com/openpeer/rolodex

Rolodex Presence – Plug-in: https://github.com/openpeer/rolodex-presence

When will WebRTC be ready for prime time?

No matter what camp you are in, pro-SDP or Object API, WebRTC feels like it’s here to stay. The fact that there is so much push-back on an Object-centric API in the WebRTC working groups tells us that there are many who are concerned about delaying v1 any longer than is necessary, there is a feeling of urgency, which seems like a good thing.

As an application developer, one looks at the current state of WebRTC as a proposed standard and it soon becomes apparent that it is not trivial. Building a commercially viable application or service will take much more than a few JavaScript APIs leveraging the WebRTC stack in Chrome and Firefox.

WebRTC is in its early infancy, building a commercial service using WebRTC in the browser today is not only unlikely it might even be a little silly. That’s not to say that the work being done in and around WebRTC today isn’t valid, far from it. It’s just that WebRTC “in browsers” is far from being ready for any service to deploy commercially and scale.

Where are we most likely to see traction early on?

What WebRTC, or specifically Google, has given us is a great media stack that we can leverage in apps.

Mobile is where WebRTC can be put to work easily and quickly. Any iOS, android or even BB10 application developer can now make use of new mobile developer toolkits that include the WebRTC media stack plus other features like social identity federation, p2p signaling and the like. Mobile is where WebRTC technology shines today.

Building for mobile first is not just convenient it’s smart. By building on mobile ahead of the browsers the developer somewhat “future proofs” the life cycle of the product being developed. When WebRTC is ready for prime time, those mobile developers will be in a perfect position to deploy to the browser, potentially edging out their competition.

When will the browsers be ready?

It’s going to be the better part of a year (some say years) before some of the hard problems are solved in the respective WebRTC working groups and even then the v1 features supported will be somewhat minimal. Even I thought this would have been done by now, but we are a long way from done.

Questions remain unanswered:  Where is Apple? What will Microsoft do with CU-RTC-Web?  What video codec will be chosen as MTI?

Regardless of how much work there is left to do, the bureaucracy and politics inherent in the standards bodies will ensure that we will not see this in production across all major browsers anytime soon.

As an example, let’s take a look at XMPP. Before it became a standard XMPP was the Jabber protocol, an open technology used primarily for instant messaging and presence. Since Jabber was already defined and deployed heavily all across the globe you would think the standardization would go rather quickly, right? Nope. That process took more than 2 years in the IETF and very little was changed.

If you are a mobile developer looking to leverage WebRTC for a mobile project, you’re in luck! There are some good mobile SDKs available today.  You might want to hold off on deployment plans for all the major browsers anytime soon, especially not if you are focusing your efforts in the Enterprise markets where MS Windows and Internet Explorer still rule the roost.

Now Hiring: Mid-Senior NodeJS / JavaScript Developer

We are looking for an experienced JavaScript developer to join our distributed team working on our open and closed source projects.

The successful candidate has proven experience working with NodeJS and networking multiple NodeJS servers to work together as a whole.  You will live somewhere in North America.

This position will require someone who can actively participate in implementing version 2 of our stack and become a core member of the team.  If building a system that will auto-scale to millions of users and be completely fault tolerant peek your interest, this position is for you.