All roads lead to WebRTC.Java in the browser no longer an option
This started happening in 2015, and is growing as a trend. Half a year ago we witnessed browsers killing off plugins and Flash with a slew of new security issues getting shunned by browsers for a few days.
This left developers with 4 available alternatives for VoIP in a browser:
- Flash, with the assumption it is being declining in popularity and support
- Plugin, which is getting harder and harder to build and maintain in a way that browsers will support it at all
- Java, the promising technology from a decade or two ago that got outdated for frontend browsers, but still available
Oh and there’s this Java Web Start thing, but seriously – you planning on enticing your customers to INSTALL something on his desktop in 2016?
With Flash and Plugin options becoming deprecated as we move further, it seems that Java will be taking the deprecation plunge as well. Oracle just announced they won’t be supporting their Java plugin moving forward.
You are yet again left with WebRTC.
The real implications aren’t for those using WebRTC, but rather those who are trying to support browsers without WebRTC:
- Up until today, they were two ways of supporting non-WebRTC browsers: Flash or a plugin (Java or other)
- Flash was always a challenge due to the mismatch in media codecs between Flash and WebRTC, along with crappy echo cancellation
- Plugins meant you could support WebRTC by wrapping it as a plugin, but this is becoming harder to do with each passing day
- Java seemed like a good enough alternative:
- Many organizations had to enable Java in browsers because their internal systems worked with Java applets and programs
- With Java you could implement WebRTC on the network on your own – there was an implementation or two of this nature
- The problem is that Java will stop supporting plugins, so if you relied on Java to get WebRTC for you – that route is closing as well
The future of communications is in WebRTC.
Planning on introducing WebRTC to your existing service? Schedule your free strategy session with me now.
The post First Plugins, then Flash and now Java – WebRTC is now the only alternative appeared first on BlogGeek.me.
It is. But it really isn’t.
Confused?Still thinking WebRTC = P2P?
There’s so much misunderstanding about WebRTC that it is funny at times. People throw into a conversation sentences like “WebRTC is just peer-to-peer – it can’t do a large conference service like you can with [PLACE-YOUR-COMPANY-NAME-HERE]”.
As with anything else in life, such comparisons are plain wrong. As I always say: WebRTC is just a technology. It is up to you to develop your service on top of it. If that service happens to be a large conferencing service, then why not?
WebRTC being P2P is just as P2P as SIP is. Or H.323. The only difference is that you get to choose your own signaling and your own client. For the first time in history, you get to choose how the topology of your solution will look like from a media and signaling perspective while using a standard specification – and not be bogged down by how people decided to define SIP. Or XMPP. Or whatever.
I had a call with a customer recently. A question that was asked during that call is do I see anyone using WebRTC in mobile just because of cost inefficiencies – not because there’s a browser requirement hiding somewhere in there. The immediate answer I gave was “definitely”. Followed with a few examples to show the point.
WebRTC is P2P? WebRTC is for browsers only? WebRTC only works in Chrome and Firefox?
There are two ways to think of WebRTC:
- A standard specification with a default implementation in browsers
- An open source media engine
If you miss that second option of open source media engine then you are missing out on a lot of the use cases out there that are based on WebRTC.
The same applies for server implementations.
There are 3 main components to a WebRTC deployment on the server side:
- Signalling – how do you get the WebRTC clients connected in the first place?
- NAT traversal – STUN and TURN needs to be mediated
- Media processing
The first two are mandatory. You’ll have them in all production services with WebRTC no matter what. The media processing one is a bit less obvious, but it is necessary in many use cases. I’ve touched this briefly recently on a post on Dialogic’s blog – oftentimes, you’ll need a server. Be it for recording, multiparty or something else. When that time comes – it isn’t that WebRTC doesn’t cut it for the job because it is P2P – it is that you’ll need to search beyond Google for a solution.
And when you search beyond Google, there are tons of different alternatives:
- DIY from Google’s WebRTC open source stack (or by other means)
- Open source frameworks and SDKs, with and without paid support options
- Commercial products, hardware and software based
- Commercial SaaS offerings for specific media components
- Commercial SaaS offerings for the whole shebang
- You can build/integrate it with your own developers or use outsourced developers or software houses
Next time someone dismisses WebRTC for his project because it is only peer-to-peer – tell them to check his initial hypothesis so he won’t miss out on some of the options he has available to him.
Planning on introducing WebRTC to your existing service? Schedule your free strategy session with me now.
Messaging is a platform.
We’re used to messaging. All of us. SMS has been around for ages. And it feels like iMessage, WhatsApp and Facebook messenger were here in the last few decades as well – they are so ingrained in how so many of us behave that we fail to even acknowledge how new they are.
For those of us who have VoIP in their veins – who learned, worked and breathed VoIP in the beginning of the second millennium, messaging is just an extension of VoIP. A buddy list, with the ability to send a message to a buddy.
Some even believe you can charge for messages (RCS – I am looking at you).
The truth of the matter is, that today, messaging is free. It is an expected “utility”, where money is made elsewhere. Facebook spent countless of billions to own WhatsApp – a messaging service with boatloads of users and little by way of features and bells and whistles. Oh – and in most cases and places, WhatsApp never charge its users for the system, and now, it probably never will.
For me, these are the things that are important from these two posts:
- That whole phone number replacement thing
- Is irrelevant in many cases
- It might work. It might not
- But that’s not where the action or money is anyway
- The future is in messaging services that may acknowledge the phone number but don’t rely on it alone
- The business model is in the business
- Messaging services doesn’t rely on consumers to pay. They rely on having a huge active subscribers base – attracting businesses to pay for the opportunity to interact with the users. Facebook is headed there. WhatsApp announced going there. WeChat is already there
- This means having an API, a market place/discoverability, good integration points
- B2C conversations
- Should you build a website for your company? A smartphone app?
- Maybe it needs to be embedded into the messaging services your customers are using instead?
- And if it is, will it be as brand pages, or just direct messaging to users?
- For the most part, messaging platforms will end up connecting people not only to other people, but to businesses and maybe even devices (for those of us in love with IOT concepts)
- Artificial intelligence and messaging bots
- Everyone is headed there in the past couple of months for some reason
- Most don’t know what it means
- I can’t say I grok it to the level I wish that I did
- For me, this is about bringing a Siri/Cortana/Google Now like experience into the messaging platform
- Delighting users
- Focusing only on the job-to-be-done of the platform isn’t enough
- Rationalizing a great UX and putting a polished design isn’t enough
- Users need to enjoy the service – it is about experiences for them – even in a work environment
- Here’s how Slack does it – which is a lot more telling than the Facebook examples
Messaging is a lot more than messaging and signaling protocols these days. It is less about the underlying network technology and more about business aspects and usability. It takes away a lot of the power and ego out of the VoIP guys. Just like that, they don’t really know what should be in their core competency. I come from this VoIP background, and I need to struggle with it daily.
What are your messaging plans for 2016?
Planning on introducing WebRTC to your existing service? Schedule your free strategy session with me now.
S doesn’t stand for Simple in SFU.What are you doing about your WebRTC SFU requirements?
I have noticed recently that more and more companies are attempting the creation of their own SFU. SFU stands for Selective Forwarding Unit, and it is by far the most popular and cost efficient architecture today for multiparty video with WebRTC. With it, all participants send their video to a single entity (usually in multiple resolutions/bitrates), and that single entity decides (selectively) how to route the incoming video to all the participants.
One such popular framework is the Jitsi Videobridge.
Up until today, an SFU for WebRTC was rather simplistic. You had VP8 to contend with as a developer but that’s about it. Life was good. You built your service and mostly whined about incompatibility between browsers.
Things have changed.
Here are a few things that you need to take into consideration when you either build your own WebRTC SFU or adopt/acquire one from others:
- Do you use VP8 or VP9 in your SFU?
- Google is already adding VP9 to Chrome
- How long will it take until it catches on for some use cases?
- VP9 is a better codec, so why not use it?
- Can it support multiple codecs simultaneously?
- Before the end of this year, we will have VP8, VP9 and H.264 available to us in browsers
- Not all browsers will support them all
- VP8 seems like the lowest common denominator at the moment
- This may change to H.264 when Microsoft Edge and Chrome support it though
- An SFU supporting only VP8 will start looking old pretty fast – and won’t work on Edge
- Staying in H.264/VP8 land will not perform as well as VP9 in terms of perceived quality for the users
- So it would be beneficial to be able to use whatever is available at the best possible quality
- Which makes it a lot more complex for an SFU – more decisions to make with more data points to take into consideration
- Mobile doesn’t like multiple, simultaneous video decoders
- Especially not when this is hardware accelerated – not all smartphone hardware can work this way
- For mobile devices, you just might want to select a single video stream to send it – or combine multiple video streams to a single one (which looks more like an MCU, but who cares?)
- In many new use cases, people want to have multiple participants chatting, but many more passively viewing
- Can an SFU scale there? And if it can’t, what will you do instead?
Like any other technology, once you get down to it, there’s more to do than the proof of concept. Consider these aspects at the beginning of your project – and not when you need to seriously rethink your architecture.
Nobody cares anymore.Nobody cares if you are a silo or federated as long as you’ve got an API
It used to be important. Interoperability. Federation. Communication across networks, devices and vendors. All useless now.
We’ve got our lowest common denominator: IP, HTTP – the web. We have our point of federation/aggregation – they now call it the home screen of a smartphone.
People got all riled up on my blog last week something about Wire needing to federate – check the comments. My view? Federating wouldn’t move an inch in their user’s base needle.
Today’s openness and messaging is all about being the platform and enabling others to connect to you. How is that achieved? By way of APIs. And by this new stupid word – “Bots” – which most probably stands for automation.
Why is Bots stupid? Because it just means using the API in a certain fashion.
Back to Messaging.Silo
If you have a service. What happens if it is a silo?
You gain users to it. Slowly or faster. Doesn’t matter that much (though it probably does to you).
One day you want to add more utility to the service – some stickiness – making sure people don’t leave. So you add features. But you understand at some point that going it alone won’t move you fast enough, so you open it up to external developers and services.
You publish an open API.Federation
Federation you say? You make your service accessible to other networks by interacting with them using the same protocol?
But what does that give you exactly? Same set of features you have, give or take a feature or two. Same utility. No stickiness. No differentiation. Not enough.
So you again wish to add features, but getting out of the core you’ve federated just places you in the position of proprietary features. And again you’ll one day understand it isn’t enough. Faster “innovation” and growth are required on that front – you can’t cater all of your customers’ needs. So you… open up! Slap an API on top of your service.No one cares
Two alternatives. Same end result.
Time to move on. Nothing here to see.
Just make sure you have a solid infrastructure – and an API on top of it for others to integrate with.
The post Messaging. Federated? Silo? Does it Matter with an API and Bots? appeared first on BlogGeek.me.
Interesting how vendors define themselves.
Oftentimes, when you ask companies to define themselves, you get a complete shopping list. The end result is that you are left without an answer that you can use. Enter Twitter, with its razor sharp 140 character descriptions of the account.
Here’s what the WebRTC PaaS vendors I covered in my report (that weren’t taken off market) and how they define themselves:#Cloud #Communications #WebRTC #API Start building on https://developers.apidaze.io Makers of @ottspott_co. Happy New YearApizee is a provider of real-time communications on webFollow us for mobile app development news, hackathons & events. Check out our community link below. For questions about your device tweet our experts @ATTCaresPlatform as a service and free APIs, SDKs to integrate text, audio, video chat, web conferencing and more into your websites and applications.Bit6 revolutionizes how developers integrate communications into their mobile & web applications. Download beta SDK for iOS now!WebRTC pioneer, real-time communication for mobile & web, customer & workforce contextual collaboration, in-app video & live assistance, visual self-serviceUnify delivers world leading collaboration & unified comms solutions. Talk to us about #NewWayToWork #NW2W #futureofwork Tweets by Sally ^SH & Jett ^JMMaking the future of digital communications services happen. #Mobile #Messaging #Telecom #Cloud #IoT #WebRTC #SS7 #Monetizing #MessagingSecurityPowerful, Intuitive #RealTimeCommunications for an all IP-World #WebRTC #OTT #mobile #cloud #KandyMobile #Disruptor50OnSIP is a leading provider of real-time communications services for businessesThe SDK that has everyone talking. Grab yours at http://developer.oovoo.com . Now with in-call messaging and filters too!Communications for Internet of Apps. Open, cloud based video, voice, data communications for enterprise, social, consumer apps across #WebRTC and mobile.Plivo is a Cloud API Platform and a Global Carrier Services Provider for Voice Calls and SMS. Sign up for a free trial today.Add video, voice, and messaging features to your app in minutes with #respokeShow What You See! Deliver a better experience by adding real-time interactions to your web or mobile app. #CX, #FieldService #Telehealth, #CustServ & moreUse the Sinch APIs to enhance your app with Voice, SMS, Verification, Video, and Instant Messaging.Skylink – WebRTC, audio, video, embeddable real-time communication.TokBox,a @tefdigital company, operates the #OpenTok Platform, making it quick and easy to integrate real- time communications into your websites and mobile appsTropo, now part of Cisco, is a cloud communications API that makes it easy to build voice & text messaging apps. Completely free to try, pay-as-you-grow pricingChanging communications forever by empowering software people to build the future of our modern communications apps. For support: @TwilioHelpCloud platform for real-time communication app development
A few interesting observations:
- Some don’t have an API specific Twitter account – rather a corporate wide account. This makes it hard for developers to understand they have an existing offering for developers
- Some explain their position in the organization and not what they do, which is somewhat sad
- Some definitely are pivoting
As these vendors are in the same place, there’s obviously a lot of shared use of words. I’ve taken the Twitter definitions above, removed unique words and placed them in a tag cloud – the bigger the word – the more appearances in makes:
Community is the derivation of communications, which makes a lot of appearances.
Most focus on Mobile.
To be expected.
WebRTC was less popular in the description. Refreshing and interesting.
Messaging isn’t high on the agenda of most platforms.
Some suggestions to the vendors are in order:
- If you are a service within a larger organization, make sure to have a Twitter account dedicated to developers
- Focus on the developer who reads the description and needs to understand what you can do for them, and not who you are within the company
- Bring the same clarity that Twitter description forces you to all your marketing collateral
2016 will be the year of video!
I heard that in 2005 I think. And then 2006. And then in almost every following year.
I used to work in a video conferencing company. So it really mattered.
When video did happen… it happened outside of the domain of enterprise video conferencing systems. And it continues to grow predominantly there.
But the thing is – video still is minuscule. Voice isn’t that interesting or important as it used to be either.
If I had to chart the use of our basic communications options these days, it would probably look like this:
I’d also say that the only reason video is almost as big as voice is due to WebRTC and the passing of time – It is easier today than ever before to implement and add video chat capabilities anywhere. And there are people who tend to do video calls instead of voice ones – because they can, but not because video is that critical, mystical part we’re often led to believe.
Video definitely has its place in the world and is extremely useful. I do most of my own business through video calling with clients all over the world. Most of them have never met me in person and are still happy to work with me. With voice, it would be slightly harder to achieve.
What ticked me to this topic was a piece on Ars Technica about the adoption percentage of IPv6 in 20 years (hint: the smallest 2 digit number). While the two things are different, video hasn’t fared much better and has been around for even longer.
Video will be a slow process, but the end result will never be the pervasiveness of voice or the current ubiquity and growth of messaging in all of its forms.
You still waiting for video to happen?
Test and Monitor your WebRTC Service like a pro - check out how testRTC can improve your service' stability and performance.
The post 20XX will be the Year of Video! Not… and how is this related to IPv6? appeared first on BlogGeek.me.
Who needs to communicate in enterprises anyway?
Everyone.Communication is… overrated
But do we really need to treat it as if it is the most critical piece of the enterprise world?
I use multiple systems to make my calls these days. They are WebRTC based or proprietary apps such as Skype, WebEx or GoToMeeting. I grumble when I have to use a proprietary system and install stuff on my laptop, but that’s life.
It was like that for me even when working for enterprises in the past – big and small. Somehow, you always need to have a “phone system” and be reachable. But other than that? I’d say “omnichannel” as a buzzword has stuck to the contact center but is just as important in unified communications.
But in Unified Communications, Omnichannel means something really different – it means that you can now reach out to people on lots of different channels and mediums – picking up the ones most suitable for the taks – which most often than not ends up being different than what the corporate IT has decided you should be using.
And you know what? I couldn’t be bothered with it.
The essence of Unified Communications is the here and now. Real time communications. If a minute passed, it is no longer interesting. It is lost.
Hangouts. Talky. A phone call (international or otherwise). Skype. Anything else.
Just pick one and lets meet.
Enterprise Messaging though is a different story.
It isn’t focused in the here and now, but rather in collecting data and making it accessible. It is about synchronizing teams and aligning them – asynchronously.
And “omnichannel” there? It means integrations with anything and everything that is enterprise software.
Which makes it the point of access for an employee to his daily life in the office.
It is a lot more sticky these days than unified communications.
Unified Communication is on another rebranding rampage. We used to call it “Convergence” a decade or two ago. And when that felt old, we started calling it Unified Communications. There are analysts that are now coining the term WCC – Workstream Communications and Collaboration. A mouthful that simply says Unified Communications need to look at the Enterprise Messaging space and copy it.
The end result will still be a focus on the here and now. And it will still be overrated.
[show promotion title=”strategy-session”]
A shy over a year ago, I wrote about 3 startups: Talko, Wire and Switch
All of them looked promising. All were using WebRTC.
In 2015, Switch had a meeting with $35 million, along with quite a few successful deployments in businesses big and small.
A month ago, Talko got acquired by Microsoft. I’ve interviewed here the Talko team in the past. Selling to Microsoft shows. Shutting the company. With little objections from customers. It all points to a single conclusion – Talko has been a failure when it comes to the business side of it. It probably had a solid technology – otherwise – why would Microsoft acquihire the team and fold it into Skype? I am sure Ray Ozzie and the team of Microsoft veterans in Talko added to this acquisition, but there was no other value in this transaction.
The Talko Team expresses it best on their updated homepage:
However, as engaged as many of you have been, the reality is that the broad-based success of communications apps tends to be binary: A small number of apps earn and achieve great viral growth, while most fall into some stable niche.
Talko didn’t grow fast enough or big enough. Clementine’s acquisition by Dropbox is similar. A communication solution geared towards team/group/enterprise communications gets acquired for its team with the service being left behind, never to be seen again.
And that’s in the less competitive domain of the enterprise. What will be with Wire? The third company I wrote about.
On Android, Wire reportedly has 100K-500K installs. Assuming iOS has twice as much (I am trying to be positive), that still falls way short of any of the messaging services we usually hear about – they are measured by 100’s of millions. Of active monthly users – not installs.
It is hard to see how Wire can change its abysmal future without a serious pivot or a drastic change in current market trends. Some will say this is a matter of a directory service and network effects. I think it is a matter of strategy and luck. Where Wire failed to attract the crowds, a different messaging service – Telegram, with 50M-100M installs on Android and a reported 60M monthly active users.
Wire was formed in 2012 and Telegram in 2013. So we can’t say Telegram had any head start here.
WebRTC makes it too easy to build and launch a communication service, which in turn, makes it hard to build a viable business with it. The role of product managers and people who need to think of the business case is more important than the technologists building the service when it comes to WebRTC. At the same time, finding good developers who grok WebRTC isn’t easy either.
2016 is going to be crucial for Wire.
What do you see for your initiative in 2016? Do you have a business case and route to market and money, or are you tinkering with the technology, assuming that if you build it they will come?
When it is the wrong metric to track.Microsoft playing the number games with Edge adoption stats
That’s how long people have been using Microsoft Edge “just last month”, according to Microsoft:
Over 44.5 billion minutes spent in Microsoft Edge across Windows 10 devices in just the last month.
That other number of 200 million monthly active devices using Windows 10 is much more impressive.
I am interested in Edge due to WebRTC and ORTC. It is one of the missing pieces of our puzzle to get adoption (or at least that’s what we’ve been told).
So how can 44.5 billion minutes can be so unimpressive?
Do the math.
Let’s assume only half of Windows 10 users make use of Microsoft Edge.
This gets us to an average of 445 minutes a month per user, placing it at less than 15 minutes a day (!)
How many of these minutes are spent with an idle browser? I got a laptop and a desktop open 24/7 with Chrome running on them. Even when I am engaged in other applications.
Microsoft decided to announce a largish number to hide the fact that Microsoft Edge isn’t really getting the love and adoption they expected, which is sad. I’ve used it a couple of times on my own Windows 10 laptop. It does what it is supposed to do and does it well, but that’s about it.
The challenge is migrating from Chrome. It stores my credentials to the many sites I visit, it has that nice search bar that often times just finds the URL I need without really searching (it automatically completes from its history), there are the few extensions I’ve got installed. All in all, it does the work. It is bloated and a memory hog, but the time when this mattered (a year or two ago) passed already, so there’s very little incentive for me to switch browsers.
Microsoft is killing Internet Explorer 8, 9 and 10 in the same day next week, pushing businesses into Internet Explorer 11 or Microsoft Edge. This might gain them a percentage or two more in adoption of Microsoft Edge – not nearly enough. Microsoft will probably announce end of life for Internet Explorer 11 in a year or two – the sooner the better if they want Microsoft Edge to grow.
What else can Microsoft do to improve its position? I don’t know. I don’t believe they can. The opportunity to surpass Google Chrome had come and gone. They will need to wait for the next opening when Google falters with Chrome or make something enticing enough for people to switch. It is sad, as Microsoft Edge is technically sound – it made browsers interesting again.
For WebRTC, Microsoft Edge still makes no difference at all. We’ve seen a few announcements of ORTC support by some vendors, but that’s about it. There’s no urgency in vendors to support it. The discussions are still about Internet Explorer when it comes to WebRTC.
Where does that leave us?
- Companies who waiting for Microsoft to adopt WebRTC will continue to wait
- Those who haven’t waited have made the correct choice – deal with what’s available and don’t wait for the forces that be to save you
- While Apple might get WebRTC properly, Microsoft hasn’t. Introducing ORTC into Internet Explorer is what the market needs, but it won’t happen by Microsoft
- Mobile is unaffected, as consumption there is done by apps, so browser adoption issues are irrelevant for most
Time to fix the stupid notifications of all them apps. Especially messaging ones.Push notification for messaging apps – not as easy as you thought
When it comes to messaging, they are probably the most chatty applications out there when it comes to push notifications (not including Candy Crush).
I’ve had my share of bad experiences with messaging and notifications to know what works for me and what annoys the hell out of me. This is also where you see the true leaders shine and the rest slumbering along.
IP messaging is considered by most developers a rather simple thing to implement. It isn’t.
Here are a few things you should incorporate into your push notifications implementation when you want to deal with messaging capabilities.#1 – Synchronize devices
Your service is sending me messages? Great.
You are aware I am the proud owner of a smartphone, tablet, laptop and PC? And that I generally connect through all of them interchangeably.
So when I am receiving a message (or sending one for that matter), it would be nice if said messages would magically appear in all of my devices. And in a timely fashion.
One of the reasons I’ve been using Skype less and less this year is that it just didn’t synchronize properly – not showing messages on all devices, or popping notifications on the app on my laptop a day or two after I’ve already received them on my phone or on the PC. It seemed like Skype just weren’t seriously prepared for this world of multiple devices per person.
Assume that if I sign in from a new device, I don’t want a “fresh” start – I want all of the data and context that is available to me on my other devices to be availalbe in this new device of mine as well.#2 – Clear notifications. Everywhere
You know that fuzzy feeling inside when you receive an email? My whole house is pinging (or used to ping), each device trying its best to be the first to announce that incoming email.
The main problem is, that handling the notification (=opening it) on one device didn’t necessarily clean it from all other devices.
Google Mail got it right after a year or two on Android. WhatsApp got it right the first time – it was almost a magical feeling when they came out with their web interface and messages got cleared on the web or on the phone automatically – and FAST.
The most annoying thing is an app that doesn’t clear its notifications. I know there are many who don’t care, but I like my notifications windows clean. Going over multiple devices to clean the same message is a show stopper for me these days (and again, up until a few months ago, Skype didn’t get this one right).#3 – Mobile and web
Notifications should occur both in mobile apps and in web browsers. Modern browsers already support notifications, so make sure to utilize it when needed.
You need to remember that knowledge workers may sit all day in front of a computer – so why not leverage that to show notifications there instead of making them pick up the phone?#4 – How urgent is it again?
Not. Every. Single. Message. Is. The. Same.
How are you going to report them? Or even notify them?
You may have them notified separately. Or bunch them up under a single icon.
Slack just added a Do Not Disturb feature. Great. I can now silence notifications in Slack. The problem is, they decided that my work day is 8am-10pm. Anything not in this timeframe isn’t notified to me. It would have been fine – but only if when 8am arrived – they’d pop up a notification about things I’ve missed.
Groups in Whatsapp can be silenced, or certain people. You can even do it for a period of time (I don’t really care about kindergarten related chatter when I am abroad). But it is manual. It would have been so much better if somehow, WhatsApp magically would decide what I prefer and what I didn’t when it came to notifications.#5 – How do I reply?
The vinyl Android SMS application enabled me to mark messages as read – right from the notification. No need to enter the app just so it knows I’ve read it. Some other apps enable replying to notifications without getting into the app.
What are you doing regarding your app? Is the only thing I can do is enter the app, or can I act from the notification itself? (guess what I prefer)#6 – Where in the view stack will I be landing?
Got the notification on my phone. Pressed it. Where will it lead me?
LinkedIn’s terrible app (even the latest incarnation of it) does a great job at putting you in the wrong view – try accepting an invite to connect and you’ll end up preferring to open it inside your browser.
Skype gets you to the conversation. Pressing the back button on Android leaves the app. But if you then enter the Skype app explicitly, after several incoming notifications of a group conversation there – it will lead you to the same conversation over and over again – at least to the same amount of times you pressed on the notification of new messages in that group. Something is terribly wrong there.
WhatsApp does a decent job here – there’s a single WhatsApp notification for everything. If all notifications are from the same conversation – that’s where you’ll land. If there are multiple conversations you are being notified of – you’ll land at the WhatsApp homepage. Oh – and if you press back? It takes you from the conversation view to the homepage of WhatsApp before letting you leave the app.Gmail does the same.#7 – Think Offline
Bonus points for handling unconnected use cases. Many miss this one when it comes to notifications.
When you press the notification, the app is launched and it goes to the server to grab the actual reason for notification. But what if I am INSIDE an elevator? Some apps do a miserable job at making sure that the launched app can show me the message without being connected (you already got me that notification – why not get the whole damn message while at it?)Why is it important?
IP Messaging is probably one of those areas where developers go NIH. They know it all. How can sending a couple of messages be hard? Oh – you also need push notifications on top? No worries! There’s that simple API in iOS that does that.
But that’s usually only the beginning of the saga when it comes to IP Messaging and push notifications. If you decide to develop it in-house – you better be ready to writing down the exact spec in detail to get it right. Otherwise, find someone who does that for a living.
Consider this my end of year review for WebRTC in 2015.
Tomorrow will mark the last day of 2015. As we head into 2016, it is time to review what we had this year in WebRTC. For me this year proved to be a real rollercoaster, but somehow I get a feeling 2016 won’t be any different.
I dug some of the statistics I regularly collect, with differences and trends in 2015 in mind. From there, the road to an infographics about WebRTC State of the Market was a short one. For those who have membership access to my site, I will be spending the next Virtual Coffee discussing these findings in detail.
<p><strong>Please include attribution to BlogGeek.me with this graphic.</strong></p><br />
<p><a href=’https://bloggeek.me/webrtc-state-market-2015/’><img src=’https://bloggeek.me/wp-content/uploads/2015/12/201512-WebRTC-infographic.png’ alt=’WebRTC State of the Market – Are we there yet?’ width=’540px’ border=’0′ /></a></p><br />
See you all in 2016!
WebRTC Broadcast will be all the rage in 2016.
As I am working my way in analyzing the various use case categories for WebRTC, I decided to check what’s been important in 2015. The “winner” in attention was a relatively new category of WebRTC broadcast – one in which WebRTC is being used when what one is trying to achieve is sending a video stream to many viewers. These viewers can be passive, or they can interact with the creator of the broadcast.
Up until 2014, I had 4 such vendors in my list. 2015 brought 15 new vendors to it – call it “the fastest growing category”. And this is predominantly a US phenomena – only 3 of the new vendors aren’t US based startups.
Periscope and Meerkat are partly to “blame” here. The noise they made in the market stirred others to join the fray – especially if you consider many of them are based in San Francisco as well.
TokBox just introduced Spotlight – their own live broadcast APIs – for those who need. At its heart, Spotlight enables the types of interactions that we see on the market today for these kind of solutions:
- Ability to produce video by using WebRTC – either from a browser or a mobile app
- Ability to view the video content as a passive participant – usually via CDN by way of Flash, HLS or MPEG-DASH
- Ability to “join” the producer, creating a 1:1 video chat or a video conference that gets broadcasted to others
Here are some of my thoughts on this new emerging category:
- Most of the focus today is using WebRTC broadcast on the producer’s side. The reasons are clear:
- Flash is dying. HLS and MPEG-DASH are replacing it on the viewer side, but what is going to replace it in the producer side? Some go for specialized broadcasing applications, but WebRTC seems like a good alternative for many
- This is where vendors have more control – they can force producers to use a certain browser – it is much harder to force the viewers
- WebRTC plays nice in browsers and mobile. No other technology can achieve that today
- The producer side is also where most constraints/requirements come from today:
- You may want to “pull in” a viewer for an interview during a session
- Or have a panel of possible speakers
- You may wish to split the producer from the “actor”, facilitating larger crews
- All these fit well with the capabilities that WebRTC brings to the table versus the proprietary alternatives out there
- H.264 is the predominant requirement on the viewer side at the moment. VP9 is interesting. This means:
- Trnascoding in necessary in the backend prior to sending the video to viewers
- H.264 in Chrome can improve things for the vendors
- There’s a race towards zero-latency. Vendors are looking to reduce the 10-60 seconds of delay inherent in video streaming technologies to a second or less (not sure why)
- This would require attempting to replace viewer end of the architecture to a WebRTC one
- It will also necessitate someone building a backend that is optimized for this use case – something that wasn’t researched enough up until today
- Peer assisted delivery vendors such as Peer5 and Streamroot is another aspect. These kind of technologies sit “on top” of a video CDN and use WebRTC’s data channel to improve performance
- I’ve started noticing a few audio-only vendors joining the game as well. This will grow as a trend. The audio based solutions tend to be slightly different than the video ones and the technologies they employ are radically different. The technologies and architectures may converge, but not in 2016
2016 will be a continuation of what we’ve seen during 2015. More companies trying to define what live WebRTC broadcast looks like and aiming for different types of architectures to support it. In most cases, these architectures will combine WebRTC in them.
Is it just me or are browsers fun again?
While there are many browsers and vendors out there, there are probably only 4 that matter: Chrome (Google), Firefox (Mozilla), Edge (Microsoft) and Safari (Apple).
Who haven’t I included?
- Microsoft’s Internet Explorer. Microsoft is actively transitioning away from it to Edge
- The rest of the pack, as far as I can tell, are nice wrappers around Chromium – and are negligible in their market share anyway
What should we expect in 2016 from the browsers? A lot.Google Chrome
For Google, Chrome is an important piece of the puzzle. It lives in the web and the more control points it has over access to information the better positioned it is.
The ongoing activity of Google in WebRTC is part of the picture, and probably not the biggest one.
Google is the company with the least amount of regard to legacy code that there is. When something requires fixing, Google developers are not afraid to rewrite and refactor large components, and management allows and probably even encourages this behavior – something I haven’t seen anywhere else.
A few examples for recent years:
- Google forked WebKit into Blink, essentially replacing the page rendering inside the browser. The first order of the day after the fork? Spring cleaning – removing code that isn’t necessary for Chrome
- Google switched EVERYTHING from OpenSSL to BoringSSL. OpenSSL seemed to have some vulnerabilities lately, so Googlers took the time to fork it, clean it up – and deploy the new project across Google
- Introducing SPDY and getting HTTP/2 out the door
That said, it seems that Google have been somewhat complacent in the area of speed and size with Chrome. I am sure the Chrome team is aware of it and working hard to fix it, but the results haven’t been encouraging enough. This will change – mostly because of the actions of the other browser vendors.Mozilla Firefox
Mozilla is in transition. From relying on Google as its main benefactor to spreading the risks.
In the past few months though, Mozilla has started trimming down its projects:
- Mozilla plans on splitting Thunderbird, its email client, from Mozilla
- Mozilla stopped developing and selling Firefox OS smartphones – I wonder how will this affect its relationship with Telefonica, TokBox and the Hello project
These changes indicate that Mozilla understood it can’t just try and replicate every cool new Google project and open source it – it will now focus on making Firefox better. This is a much needed focus, with Firefox slipping in market share for quite some time now.
On the browser front, the notable changes Firefox is making are around privacy and the pornprivacy mode.Microsoft Edge
Edge is new. It is a complete rewrite of what a browser is. It is speedy, clean and with huge potential. It has its own adoption challenges to overcome (mainly people comfortable enough with Chrome and not caring to try out Edge).
- A browser/webapp today is split into two – frontend and backend (we already knew that). More often than not, these days the backend is based on a Node.js framework. Microsoft wants to be a part of that backend, probably to end up licensing Windows 10 on servers
I am sure there’s an engineer at Google already tasked at reviewing the code of Chakra once it gets a public git repository.
Edge is trying to move the envelope. This will challenge Google further with Chrome – always a good thing.Apple Safari
Safari seems second place at Apple. It is working, but not much is said or done about it.
We hear a lot of rumblings about WebRTC in Safari lately. How will this shape into Safari, iOS and Mac is anyone’s guess. The bigger question is will this be the only significant browser change to be introduced by Apple or part of a larger overhaul?Why is this important?
The web isn’t standing still. It is evolving and changing. Earlier this year, WebAssembly was announced – an effort to speed up the interactive web.
While many believe that apps have won over the web when it comes to development, we need to remember two things:
- There are times when an app won’t do – as Benedict Evans phrases it well in Apps versus to web: “Do people want to put your icon on their home screen?” – and sometimes they just don’t
- Apps are sometimes built using HTML5 – usually because a developer wants a single code base for all platforms or just needs easier access for his service from a browser and mobile apps at the same time
An interesting road ahead of us.
It’s easy, as long as you know where to look for it.
This was published yesterday. Oftentimes, the things I read out there about WebRTC sounds just like this conversation from Dilbert’s life.
WebRTC is elusive. It is located in the cracks between VoIP and the web – a place where most people are just clueless. My own pedigree is VoIP. About 6 years ago, as an “aging” CTO trying to build a cloud service with an API for developers that runs a VoIP service, I was given an important lesson – there’s much to be learned from a 24 year old kid with milk teeth. In a span of a year and a half I got introduced to agile methodologies, internet scale, continuous deployment and a slew of other techniques – none of them was given the term we use today – but they were all there. It helped me later in understanding how and why WebRTC is so transformative.
As we head into 2016, I guess it is time to state a few of the great resources out there for WebRTC – the places I rely on in my own reading about WebRTC.The Bloggers
Out of the people out there that cover WebRTC, there are 3 that I make it a point to read. All of them are good friends of mine:
- Chris Kranky, who is always fun to read
- Disruptive Analysis, by Dean Bubley
- The New Dial Tone, written by Amir Zmora
- WebRTC by Dr Alex is relatively new to the scene and is showing promise for low level WebRTC developers
Most company blogs suck. Big time. They are boring, and usually read like brochures or press releases. There are a few decent corporate blogs covering WebRTC – some of them can be considered mandatory reading.TokBox
TokBox has the best corporate blog all around if what you are looking for is WebRTC related information. Now that they have recruited Philipp Hancke they probably will improve further.
Between their new offerings and features announcements are gems of information in the form of whitepapers of certain verticals and insights on WebRTC from the service they operate. They also run TechToks that get recorded and published on YouTube.callstats.io
The callstats.io blog is another great resource, especially when it comes to covering getstats() related stuff and media quality. Highly recommended.AT&T
I’ve written my own guest post on the AT&T Developers blog once or twice, so I know how they operate. While being a large corporation has a lot of limitations, when they publish content about WebRTC or adjacent technologies – it is worth the time to read.
A testament to that is the recent series of WebRTC UX/UI posts they have commissioned from &yet – mandatory reading for anyone who delves into web apps for WebRTC.Sinch
While Sinch’s blog hasn’t been too interesting when it comes to WebRTC lately, earlier this year they had great content to share. Lately, it tends to be around use cases of their customers – totally interesting, but from a different angle.
I’d register on their blog if I were you to keep posted. I am sure they’ll have interesting articles for us next year as well.WebRTC Digest & Blacc Spot Media
The digest site is all about acquisitions and money raising in the space, while Blacc Spot Media tries to cover the industry and the ecosystem.
At times, there needs to be some further validation to the vendors being written about there (some aren’t really doing WebRTC but are in the real time space), but all in all, one of the better resources out there.webrtcHacks
By far the best place for WebRTC developers to go.
In-depth and timely content.
If you aren’t subscribed – then please do.WebRTC Weekly
If you don’t want to subscribe to too many resources, and are in the need for a single source, then Chris Kranky and me operate the WebRTC Weekly. Subscribe by email to receive one email a week with links to the relevant articles and posts from all over the web related to WebRTC.
There are three reasons why something doesn’t get included in the WebRTC Weekly:
- Trash content, which either isn’t accurate or just too shallow
- Repetitive, of something that was already covered in the weekly (usually at a higher quality)
- We missed it… email us with things you think we should include
Cloud Communication APIs.[If you are new around here, then you should know I’ve been writing about WebRTC lately. You can skim through the WebRTC post series or just read what WebRTC is all about.]
API platforms fascinate me. Especially communication API platforms. You can’t get any bigger than Twilio these days. This year, they’ve announced and launched a slew of new capabilities – task routing, video calling, IP messaging and a lot of enhancements to their existing services.
I’ve been wanting to land an interview with Twilio for quite some time. I was happy when Al Cook, Director of Product Marketing at Twilio, obliged. Here’s what he had to say.
What is Twilio all about?
Twilio is a cloud communications platform. We provide programmable building blocks that developers use to embed communications into their mobile and web apps – from voice, messaging, and video to authentication. So when you are communicating with your Uber driver via text or anonymous phone call, calling Hulu customer support, or shopping via text with the help of your Nordstrom personal shopper, that’s Twilio. Or to give a WebRTC example – when you call a customer support team powered by Zendesk, the agent is talking to you over a WebRTC connection powered by Twilio. We have over 700,000 developers generating over 50 billion API transactions a year. In WebRTC we’ve powered over half a billion minutes of WebRTC to date.
Twilio Video went to public beta today. You’ve been in private beta for a while. How is it going? What have you learned?
That’s right, the private beta started in May and we collaborated with developers to build the right solution, with the right developer experience. Video is in public beta as of now. Now anyone can sign up for immediate access to our WebRTC-powered web and mobile SDKs, and the cloud-based signaling/media services that power them.
During the private beta we onboarded several thousand developers from our base. This group size was critical for gaining useful feedback and insights, while still allowing meaningful interactions.
Interesting. Did you check what users do during the private beta?
During the private beta onboarding, we asked participants to tell us about their use cases. I read every single entry and categorized the use cases. The top categories break out as follows:
- 21% healthcare
- 14% support (in-app enterprise customer support, visual customer support)
- 12% tutoring
- 10% collaboration
- 5% recruiting
- 5% call an expert
- 4% marketplace / sharing economy
- 4% interpretation services (including assistive deaf/blind services)
Two of the big areas we spent considerable time refining during the beta were improving the mobile media stack performance, and building a signaling model that allows us to continue to add new capabilities for multi-party, multi-endpoint IP and carrier communications.
I have to ask. These developers in the private beta – how many of them were existing Twilio developers who just added video versus new ones?
It’s a mix. A lot of folks are with us because they want multiple channels of communication, and so video is a natural extension for them. But we’ve also had a lot of people who were new to Twilio, and excited to have a better alternative than their current video solution.
How is your video offering different from other alternatives that are out there today?
We believe this solution is not available anywhere else. Here’s some insight on the areas where we invested the most time to ensure we were building the right solution for needs that had not been addressed.
- Without this, each communication capability would either have to be built from scratch or individually purchased and pieced together, if possible. And that’s just the beginning. Our SDKs are designed as a platform to add more communication channels over time.
- We designed a conversation model that scales in volume, use case and breadth of different endpoint types. Conversations can be either call-based or room-based; start peer-to-peer and move to network-mixed; and interoperate with SIP endpoints and carrier endpoints. Our signaling model is built to fulfill this vision. Some features are enabled today; others are coming. The important thing is we’ve laid the foundation for one platform that can power all communications needs.
- Our pricing makes it accessible to everyone, and to scale to the very largest deployments. Most video services require per user fees, which are expensive for starting-up and scaling. Twilio video is aimed at infrastructure level pricing where it’s faster and cheaper than building and operating your own service at any scale. And users get the benefit of our ongoing work to deliver high quality and resiliency.
What excites you about working in WebRTC?
To me, the most exciting aspect of WebRTC – and really programmable real-time communications more generally – is that it stands to fundamentally change the way we communicate. Through every iteration of the phone, the basic interaction hasn’t really changed. Historically, there has been little-to-no ability to gain immediate context of why the caller is calling, what they were doing beforehand, and what they may need. Embedding communications into applications allows for a far more meaningful and relevant communication. Imagine calling your car insurance company from your car insurance app following an accident, and instantly the call is routed with the right prioritization based on the GPS of your phone to an agent who speaks your prefered language. The app enables you to instantly share a video feed of the accident scene and collaboratively annotate the video using the app. All this while the agent captures the information in their record system to avoid a separate visit from a damage appraiser.
We believe every single app will have communications built into it. Every. Single. App.
Where do you see WebRTC going in 2-5 years?
WebRTC/ORTC is moving at such a velocity that 5 years out is pretty hard to forecast. But we believe:
- In this timeframe, browser support should be ubiquitous. We’ve seen Microsoft Edge get there already (barring video codec support), and we know Apple is working on it for Safari.
- Ubiquitous doesn’t mean standardized or non-contentious. We expect to continue to see differences in implementation of particular features that the developer will either have to keep track of and deal with directly, or use an SDK such as Twilio Video.
- Media quality requires continuous improvement. We’ll continue to make it better and more resilient to bad networks. However, in this timeframe, there will remain some networks that are not viable for real-time video.
- Mobile in-app usage will be the most important use case for consumers. This means that most consumers won’t be using Google’s latest WebRTC engine off the shelf, but rather a version that has been packaged – and often modified and enhanced – along the way.
- B2C Communications will focus on high-value, contextual interactions. Low-value B2C interactions will be increasingly handled through self-service channels. WebRTC will be one of the core technologies powering the high value segment.
If you had one piece of advice for those thinking of adopting WebRTC, what would it be?
Experiment – and think about how you scale the experiments that find success. It’s relatively simple to get a basic WebRTC call working. But plan for what happens if your new service finds success. Consider how will you scale, maintain and operate your TURN media relay. How will you collect and analyze voice quality diagnostics from all your endpoints. How will you interoperate with SIP networks and PSTN networks.
Given the opportunity, what would you change in WebRTC?
Some improvements have been addressed by ORTC. We’re big fans of these improvements and we look forward to the standards combining.
We would like more control over the media stack in a browser environment, if the browser makers could figure out a secure way to enable this. We spend a considerable amount time testing and measuring voice quality in impaired networks. In fact, we open-sourced the testing tool we use. On the mobile side, we operate the media stack and we do a lot of fine tuning to constantly improve the media quality. This includes taking into account the performance of different networks and hardware configurations. Whether it’s adding codecs to use in particular scenarios, adding Forward Error Correction (FEC) techniques, or other areas we are working on. But when our endpoints call a browser-based endpoint, they have to fall back to the default media stack and it is not possible to layer on additional media enhancements, which is why we’d like more control in the browser environment.
In the more immediate time frame, the subject of handling QoS in WebRTC is tricky, and far from standardized. Plus, QoS behavior, like with much of WebRTC, tends to require significant reverse engineering to establish the exact behavior in different scenarios. We’re happy we can provide this capability on behalf of our customers – but we’d like more control over the experience.
What’s next for Twilio?
We’ve talked about a few of them – interoperability with SIP endpoints and PSTN endpoints for example. Of course we’re also working on SFU functionality for large scale video conferences – that should be no surprise to our customers. But we want to provide this capability in such a way that a developer doesn’t have to choose between either peer-to-peer routing or SFU mixed. The solution should intelligently move from one to another as the call topology requires. We also want a solution that scales beyond any existing solutions. And then, well…that’s enough to keep us busy for now Tsahi.
The interviews are intended to give different viewpoints than my own – you can read more WebRTC interviews.
Your private 911 system.[If you are new around here, then you should know I’ve been writing about WebRTC lately. You can skim through the WebRTC post series or just read what WebRTC is all about.]
I have seen a lot of applications lately that target public safety. Some offer you a “ghost” partner to “walk” with you home, while others focus on the reporting aspects.
SaferMobility targets the authorities as the owners of the system (college campuses, municipalities, business zones, etc) and provides a mobile application to the users. It is reimagining how a 911 service would look like if it was being specified today.
Matthew Mah, CTO of SaferMobility, was kind enough to answer my questions on what role WebRTC plays in their service.
What is SaferMobility all about?
SaferMobility focuses on using the capabilities of modern smartphones for enhancing safety. The public safety system in the United States is built around wired telephones, and it is more difficult for authorities to respond to mobile phones because they are harder to locate than fixed telephones. The modern smartphone has audio, video, location, and text capability that just are not being used efficiently yet.
There are many other safety related apps out there. What differentiates you from the rest of the pack?
Our systems focus on real-time interaction with authorities. Authorities receive enhanced calls with audio, video, location, and text information in real-time without it having to filter through friends or storage systems.
You told me you launched your service using Flash. Why did you migrate to WebRTC?
WebRTC is a huge improvement over Flash in terms of security, support, and capability. Adobe is not really interested in supporting Flash for mobile devices, so capabilities like acoustic echo suppression are not available. This makes a huge difference in communication quality.
What signaling have you decided to integrate on top of WebRTC?
We use a proprietary message system built on websockets.
Backend. What technologies and architecture are you using there?
Our Java application server runs Tomcat with a PostgreSQL database. It handles the signaling and issues commands to a media server for recording capabilities. We currently run on Dialogic’s Extended Media Server (XMS).
Mobile. You decided to port WebRTC to iOS and Android on your own. How was the experience?
Porting was difficult because of compatibility issues between our WebRTC media server with web, iOS, and Android clients. We would get two clients to work with the server, then upgrade the server and have two different clients work.
For stability on the web side, the nwjs project has been very helpful for producing an application that works even while the web browser updates are racing ahead and frequently breaking things.
Where do you see WebRTC going in 2-5 years?
WebRTC will replace stagnant technologies like Flash. The ability to communicate through the browser will also lower the barrier for application development.
If you had one piece of advice for those thinking of adopting WebRTC, what would it be?
Be prepared for things to change quickly because WebRTC is still growing and maturing.
Given the opportunity, what would you change in WebRTC?
Aside from the expected growing pains, I am pleased with WebRTC.
What’s next for SaferMobility?
There’s a huge opportunity to improve public safety, security services, and general communication with modern mobile devices, and SaferMobility will be part of making those improvements.
The interviews are intended to give different viewpoints than my own – you can read more WebRTC interviews.
The post SaferMobility and WebRTC: An Interview With Matthew Mah appeared first on BlogGeek.me.
WebRTC GetUserMedia is more important than the rest of this communication stack.
Who would have believed? With all the magic and distraction that video calling from a browser brings with it, the real treasure trove resides in the basics – WebRTC GetUserMedia.
Simplifying things, WebRTC has 3 distinct areas/APIs to it:
- GetUserMedia, allowing access to camera and microphone inside the browser
- PeerConnection, taking care of all the mess that is a voice/video call
- Data Channel, making it possible to send any arbitrary message across browsers directly
I’ve pointed up in the past how WebRTC GetUserMedia gets used by Mailchimp and WhatsApp. Taking a camera snapshot is nice, but what else can we achieve with this access we’ve been given?TalkLessNow
Chris Kranky had an idea a few weeks ago. Measuring how much you’re yapping in a call as opposed to listening. So he made it happen. On a shoestring budget, some connections and a bit of time and TalkLessNow was born.How it works?
The website is quite spartan. When you go on a phone call (not a WebRTC one), you just press the green Call button on talklessnow.com.
The code on the site “listens” through the machine’s microphone to your call. Whenever it hears enough of a volume – it assumes you’re talking. If the volume is lower than its configured threshold – you’re listening.
Just WebRTC GetUserMedia. No PeerConnection or any other fuss.Will it work?
Here in Israel, I am sure the results won’t be good. We’re used to talking over each other and interrupting. Efficiency at its best. If in a call between Israelis it shows less than 70% of talk time per participant, I’ll crown that session a success.
Seriously though, we should be listening a lot more than we’re talking.Same but different
The now defunct Guitar Tuner works the same way. It doesn’t work anymore because the site is served on HTTP and WebRTC GetUserMedia now requires HTTPS to work with the latest Chrome release (progress, you know).Ziggeo
Here’s another example.
Ziggeo is making use of WebRTC to record videos. They do that by employing WebRTC GetUserMedia, storing the resulting media locally and at the end of the recording sending it to their servers. The sending part doesn’t occur via WebRTC.
There’s an interesting interview with Susan Danziger, CEO of Ziggeo from last week that you should read.Is this Real Time Communications?
It works. It gives business value – and in ways that weren’t really possible up until today.
There’s a lot more to WebRTC than classic VoIP.
The post The Hidden Gems of WebRTC Goodness May Well Lie Within GetUserMedia Itself appeared first on BlogGeek.me.
The future isn’t what it used to be.
I’ve been babbling here a lot about the enterprise video conferencing market and WebRTC’s role in disrupting it. When it first came out, I believed the existing companies are going to be struggling with it. I was mostly ignored by these companies – it is hard to see what’s just around the corner when you’re stuck in the echo chamber of your company and its immediate industry.
When I meet old colleagues of mine from the video conferencing industry and see them working in the same companies, I suggest they leave. Find another company or industry, because the outcome is known – just the timing factor is missing. They dismiss it, probably thinking that I am saying it our of a grudge to the company. I am not.
What happened in November should hit home.
We had two separate news items that in some cosmic way happened in the same week:
- Cisco acquired Acano. For $700M USD. A company with around 350 employees (that’s $2M per employee)
- Polycom announced closing its Israeli office. Moving the operations to India. That’s 200 employees + 80 contractors
Dumbing things down a bit:
- Acano was about building a cloud MCU. Polycom Israel was about building an on-premise MCU
- Acano started life in 2012, making immediate use of WebRTC. Polycom just launched their first MCU to support WebRTC this year (2015)
It isn’t that WebRTC is the reason why Acano succeeded and Polycom Israel has failed. It is that the mindset of these two companies was different. Acano looked into what can be done in this modern age and made use of WebRTC to get there. Polycom looked at how they slowly evolve their product offering. I am sure people in Polycom knew about WebRTC. It probably was on roadmaps and discussions since 2012, never to be given priority, because who needs it? It can’t compete with the high end systems of Polycom. But then the basis of competition changed. What customers care about changed. It isn’t anymore about resolutions and frame rates. It’s about utility and usability – something most video conferencing companies never knew how to handle.
Polycom Israel didn’t have the foresight to make themselves attractive enough to their corporate overlords in San Jose. Probably because they weren’t given the opportunity to do so. The end result? They just weren’t important. Their technology and architecture is now stable and understood enough to move it to countries with lower salaries.
I remember doing a training to developers about WebRTC in 2014. I asked people in the room what they do. There were media engineers and signaling protocols developers. I told them that they are going to be out of work. They saw it as a joke. Some of them are now updating their resume.
What is it that you are doing for a living? What is your company developing? Does it make sense? Do you take the effect WebRTC (and other technologies) have on your job seriously?
The post The First WebRTC Earthquake in Video Conferencing: Acano vs Polycom appeared first on BlogGeek.me.
Asynchronous video meets WebRTC.[If you are new around here, then you should know I’ve been writing about WebRTC lately. You can skim through the WebRTC post series or just read what WebRTC is all about.]
One area where WebRTC is making strides recently is video streaming. Some of the hyped use cases today are those that enable broadcasting in real time, but there’s another interesting approach – one where WebRTC is employed when the video consumption is asynchronous from its creation.
Ziggeo is an API provider in this specific niche. I met with Susan Danziger, CEO of Ziggeo, and asked her to share a bit of what it is they do with WebRTC and how it is being adopted by their customers.
What is Ziggeo all about?
Ziggeo is the leader in asynchronous (recorded) video offering a programmable video recorder/player through our API/native SDKs.
You started by working on an HR interviews platform. What made you pivot towards a video recording API platform instead?
In building our own video recording/playback solution for the platform, we realized what a complicated and time-consuming process building our own solution was. We had to make sure that videos could be recorded and played across all devices and browsers (even as new ones were released) and build a permissions-based security solution that would withstand hackers. We were surprised there were no off-the-shelf solutions available so decided a bigger opportunity would be to release our technology as an API — and then native SDKs (and shortly thereafter closed our B2C platform).
On the same token – you have Flash there. Why did you add WebRTC? Wasn’t Flash enough for your needs?
For the most part our customers hate Flash. And no wonder: browsers that support Flash have an awful user experience in which you need to basically hit 3 different buttons before you can begin recording from your web camera (once to resume the suspended Flash applet and twice to access the camera).
We added WebRTC to avoid Flash whenever possible. That said, for certain browsers, e.g. Safari and Internet Explorer we need to default to Flash as they don’t yet support WebRTC.
How are customers reacting to the introduction of WebRTC to Ziggeo?
Customers love it! In fact, our customers seek us out in part because we’re the only API for asynchronous video recording that supports WebRTC.
Can you share a few ways customers are using Ziggeo?
In addition to recruiting (where candidates introduce themselves on video), we’ve seen Ziggeo used for training (e.g. trainees record video sales pitches for feedback); dating (potential dates exchange video messages); “Ask Me Anything” (both questions and responses on video); e-commerce (products introduced on video and video reviews recorded); advertising (user-generated videos submitted for contests or for use in commercials); and journalism (crowd-sourcing videos for news from around the world). I’m still waiting for someone to create a video version of Wikipedia where pieces of knowledge are recorded on video from around the world — that would be the most amazing use case of all.
A video version of Wikipedia. Have it in Hebrew and I’ll sign up my daughter on it.
You don’t use the Peer Connection APIs at all – Just getUserMedia. Why did you make the decision to record locally and not use the Peer Connection and record on the server?
Folks like to re-record locally so we chose not to use unnecessary resources. We pride ourselves on making our technology as efficient and seamless as possible.
How do you store the file locally and how do you then get it to your data centers?
We use IndexedDB to store the file locally and then push it using chunked http.
Viewing. Over what protocols do you do it, and how do you handle the different codecs and file formats?
Protocols: Http pseudo streaming, HLS, rtmp, rtsp
Formats: we transcode videos to different formats (mp4, webm) and resolutions
Where do you see WebRTC going in 2-5 years?
We imagine there will be full support of WebRTC across all browsers and devices as well as better support for client-side encoding of video data.
Given the opportunity, what would you change in WebRTC?
We’d like to see improved support for consistent resolution settings as well as for encoding
The interviews are intended to give different viewpoints than my own – you can read more WebRTC interviews.
The post Ziggeo and WebRTC: An Interview With Susan Danziger appeared first on BlogGeek.me.