#hookflash

ORTC and WebRTC Consulting

   Hookflash is now providing WebRTC and ORTC Consulting services.

Professional Services Pack

For organizations looking for an expert ORTC / WebRTC developer to provide assistance or become a part of their teams for specific projects. Depending on your needs, the Hookflash subject matter expert can help with any aspect of your project, including consulting, design, development, and QA. The PSP…

ORTC Interview: webrtchacks’ Chad Hart & Robin Raymond #webrtc

webrtcH4cKS: ~ ORTC is not the “Other” RTC: Q&A with ORTC CG Chair Robin Raymond

Char Hart of webrtchacks.com interviewed ORTC Chair – Robin Raymond on a range of topics. Excerpt:

Biggie vs. Tupac. Gates vs. Jobs. Apple vs. Samsung.  Nothing catches people’s attention for no legitimate reason like a feud. Unfortunately this isn’t just a celebrity phenomenon. Feuds have been endemic even to real…

2014 WebRTC & ORTC Events – Fall / Winter Schedule

September

Sept 30 – Oct 2 / Chicago – IIT Real-time Communications Conference (For me, this is “the” objective gathering of the brightest technical minds in the RTC space.) Robin Raymond will be speaking on ORTC / WebRTC 1.1 and also Cloud + P2P Communications.

October

30-31 Oct / Santa Clara – W3C TPAC / WebRTC WG Meeting (W3C Technical Plenary / Advisory Committee Meetings Week which includes…

We can all learn something from Mr. Jobs, "Make it better, make it simple, make people want it!". I don't think he ever said that, but it feels like he is saying that directly to me every time I pick up my iPhone. From what I have read and heard, Steve was a magician designer, motivator, visionary, savior and brilliant marketeer. I seriously doubt anyone ever heard Steve say, "Let's ship minimum viable product!". There is a major difference between MVP and KISS (Keep It Simple Stupid). Building complex products and services that look and feel "simple" is really hard! MVPs are basically alpha builds at hookflash.  I guess it all depends on what you are building and what your goals are but for me, shipping "minimum viable product" always left me feeling a bit weak. If you are going to ship something that you want people to fall in love with and use every day, you will need to spend time reiterating before you even get to market. It will not be easy and it will always end up taking longer than you predicted. I am not saying that the Angry Birds and iFart apps aren't successful but when it comes to clearing space on my iOS device, they are the first to go. Wired recently published a great article on their blog, ‘Ship Today, Update Tomorrow’: The Modern Tablet Credo. I won't spoil the read (and it's a good one) but for me it identifies a developing trend that undermines value in new products and services. Why ship it if it's sadly lacking features and functionality? So you can buy yourself some time? Kindle Fire has shaken up the tablet market but only the market will decide if they deserve a second chance. Seth Godin had a great article that touched on this as well, "When "minimal viable product" doesn't work", excerpt below..

One of my favorite ideas in the new wave of programming is the notion of minimal viable product. The thought is that you should spec and build the smallest kernel of your core idea, put it in the world and see how people react to it, then improve from there. For drill bits and other tools, this makes perfect sense. Put it out there, get it used, improve it. The definition of "minimal" is obvious. Often, for software we use in public, this definition leads to failure. Why? Two reasons: read more on Seth's blog.

Update: Top 60 users selected

Thank to everyone for participating! We saw some great feature suggestions and general comments. We will be sending out a message to those selected by the beginning of February. We will also be updating our progress on Twitter and LinkedIn. Thanks again! -Erik  

For those who signed up for the hookflash for iPad early preview, thank you for signing up!

We have received thousands of early access requests, which we take as a great sign!

But now we are faced with a dilemma. Considering Apple limits us to 100 test accounts prior to launching in the app store, who gets in!?  We need 40 accounts for our own internal use and testing. That leaves 60 accounts for our early access users. It seemed clear to us that we should let our users decide who gets in. The process would have to be fair and would need to be publicly monitored so nobody feels jilted. So here's the deal, if you want in, this is what you need to do...

Follow @hookflash on Twitter.

Tweet about the feature you would like to see most in hookflash for the iPad. Could be a design element, feature, interoperability request etc. Be sure to include @hookflash in your post.

The top 60 people with the most Twitter mentions (must include @hookflash) before January 6 2012, will get a spot in the early preview.