Pre game time: 7:30 AM rehearsal for hookflash at Innovation Showcase – big room – it was full for our presentation! via @trentjohnsen
Working with long time friend and Chief Architect @hookflash – Robin Raymond. Love this guy! (Taken with Instagram at Brookstreet Hotel)
One of the most common questions we get asked of hookflash is “how is it different from Skype™?
We could write extensively about this but Alice Waters, one of America’s most revered chefs, frames an answer perfectly in the intro to her Chez Panisse Cookbook:
“ Food must be experienced and I worry that writing about it may not make the sense I want it to. I wish I could just sit people down and give them something to eat; then I know they would understand.”
The moment you experience hookflash, you understand how different it is from Skype™.
From the simple, elegant user interface to the rich integration of social context and user identity, hookflash works and feels distinctly different from Skype™. Importantly, instead of adding complexity with another user ID and phone number to manage, or additional directories and buddy lists to maintain, hookflash provides instant HD voice, video, messaging and social connections to all my LinkedIn™ contacts in my pre-existing, self maintaining LinkedIn™ directory in the Cloud.
There are important considerations other than just how hookflash is different than Skype™. Given the phenomenal growth and success of Skype™ (over 40 million simultaneous connections was a new milestone this week); @hookflash we’re working on …
How can we improve beyond Skype™ and deliver on our vision of work, life, simplified?
At Hookflash we make it no secret that we are true believers in WebRTC. We are looking to grow our team of developers to assist in bringing Hookflash to the web.
Here is the posting…
The Hookflash team is looking for passionate, team-oriented and self-motivated Developers to help us bring the Hookflash experience to the Web. You will have a chance to integrate Hookflash solutions and WebRTC with the support of the backend services group using Hookflash & OpenPeer technology.
You will work in dynamic environment with a team of true professionals participating in defining, designing, developing, testing and documenting Hookflash for the modern world. You will work with colleagues in Eastern Europe, Canada and USA on Browser related solutions cooperating closely with colleagues developing Hookflash cross platform core library, the Audio / Video team, the User Management team and the Hookflash WebRTC team.
- Design and maintain robust and loosely coupled application code in collaboration with the team architect.
- Lead development by implementing most critical parts of the application.
- Understand Hookflash software development process and perform all required and otherwise useful practices.
Qualifications and Experience:
- BS/MS in Computer Science, Information Systems or similar.
- Extensive experience developing rich web client applications.
- Java or C++ experience would be a strong advantage.
- Self-direction – must work independently to develop application code. This role demands proactive, ‘can-do’ nature.
- Self-management – Must be highly organized and be able to prioritize work effectively. Successfully engage in multiple initiatives simultaneously.
- Team-orientation – Able to put team interests above personal, help team to move faster all together and take personal responsibility for the whole team result.
- Excellent problem solving and analytical skills
- Experience in agile software development methodologies: SCRUM
- Experience in applications that cross (and depend on) multiple client environments (e.g. variation in device driver, network connectivity etc.) would be a benefit.
All Hookflash job postings can be found here..
#Hookflash video call with Cullen Jennings (aka Fluffy – Chair for the IETF Working Group – RTCWEB) today. We discussed many items on the hit list for WebRTC / RTCWEB and the recent IETF 83 meeting in Paris, held last month.
It was interesting to hear Cullen call out to everyone, “..pay attention or risk getting run over by the WebRTC bus!”
A few of the questions asked..
- What is WebRTC and why is it important?
- What is the difference between WebRTC and RTCWEB?
- Who are the driving forces behind this new technology?
- What does WebRTC mean to the average person?
- What problems are left to resolve eg. Video & Audio Codecs, Signalling, Security, Identity?
- Will there be verified identity providers in this model like SSL cert providers?
- When will we see WebRTC used by most app and web developers?
- When will we see WebRTC hit mainstream adoption?
- Who are the big players?
- What does this mean to SIP or P2PSIP?
- Where does Microsoft / Skype or other P2P offers fit in?
- Where does Apple on mobile devices and WebKit fit in?
- What about Google & Hangouts?
- How would non-SIP players use this technology?
Thanks for the time Cullen!
Posted by: Erik Lagerway
Speaking of WebRTC, here is the most recent VUC (VoIP Users Conference) call recording on the same topic…
Contributors: Randy Resnick, Tim Panton, Dan York, Jason Goecke, Serge Lachapelle, Justin Uberti, Karl Fife, James Body, Dean Bubley, Erik Lagerway.
If I have missed anyone, my apologies and please msg @elagerway so I can add you.
We live in what is shaping up to be one of the most active periods in the evolution of communication and social interaction.
Social Media is in a total frenzy (billions of users now) and IP Communications is seeing some of the most interesting innovation (WebRTC) and development activity it has seen, arguably in the history of IP itself.
Feels good to be part of it! We can’t wait to get Hookflash out into the market! We are moving towards the next evolution in mankind’s need for social interaction and communications.
Can’t wait for the wireless carriers to get fully on board with this all IP world we live in today. An all data-centric wireless offer on a good smartphone, where I get to assign the the native phone app to a provider of my choosing, for my own voice and video communications, must be imminent, don’t you think ?
“#WebRTC via Voxeo Labs on VUC tomorrow! Try and make some time for this one. Personally, I am interested in hearing more about RAYO and how it plays a part in Voxeo’s WebRTC strategy.”
“If Apple allowed us to actually delete the phone app, I’d bet some of us would do it right away. In our evolving relationship with mobile phones, I wonder when we are going to stop calling it a “phone.”
Inventing the Future
‘The Idea Factory,’ by Jon Gertner
reviewed by Walter Isaacson, the chief executive of the Aspen Institute and former editor of Time, is the author of biographies of Henry Kissinger, Benjamin Franklin, Albert Einstein and Steve Jobs.
“The Idea Factory” explores one of the most critical issues of our time: What causes innovation? Why does it happen, and how might we nurture it? The lesson of Bell Labs is that most feats of sustained innovation cannot and do not occur in an iconic garage or the workshop of an ingenious inventor. They occur when people of diverse talents and mind-sets and expertise are brought together, preferably in close physical proximity where they can have frequent meetings and serendipitous encounters.
This is how “Open Peer” was inspired. Just over a year ago at IETF 80 in Prague my hookflash co-founder Erik Lagerway posted about “SIP thrown under the bus”
The IETF brings together a lot of the world’s great talent and this particular IETF plenary was on real-time communications on the web – “RTCweb”. Erik and our lead developer Robin Raymond were there ” in close physical proximity where they can have frequent meetings and serendipitous encounters.” with thought leaders and development executives including Dr. Cullen Jennings, Cisco fellow (hookflash Advisor – office of the CTO at Cisco) who Chairs the working group on RTCweb, along with people from Apple, Comcast, Google, Skype and most of the major international telcos to name a few.
By the end of the conference in Prague, Erik and Robin were not only convinced that SIP was in fact broken but they had conceived of creating a new protocol that would overcome the challenges with SIP. Instead of returning home, they flew directly to work with the rest of the hookflash European team and over the course of an intensive few days the conceptual framework for Open Peer was developed. It is “Open Peer”, our own new transport protocol that will power hookflash starting with hookflash for iPad, and how at hookflash we’re working on our own version of “inventing the future”.