| > "As far as we know, we are one of the first services built purely on WebRTC to launch a dedicated iOS app" Hookflash [0] is a dedicated WebRTC iOS app that has been around since 2012 or so, and has a badass signaling layer with OpenPeer [1]... it also provides a SDK for building this kind of services in just a couple of hours. But then you also have OpenTok [2], that has been offering a similar iOS SDK with native WebRTC stack since late 2012 / early 2013, Mashme.tv [3] also in 2013, EasyRTC in mid 2013 [4], and hundreds of similar apps and solutions that are popping up like mushrooms (AddLive, etc...) and also use WebRTC in iOS.. What I'm trying to say is that WebRTC on iOS is already a quite crowded space, and the first services were deployed years ago (late 2012)... It would be more interesting to know what have you used in the signaling plane (websockets? pusher/pubnub? old sip?) how you have solved things like NAT traversal (TURN, ICE, Hole Punching, etc), or which solution you use for MCU... [0] http://hookflash.com/ [1] http://openpeer.org/ [2] http://tokbox.com/opentok/ [3] http://www.mashme.tv/ [4] https://www.youtube.com/watch?v=4DzVqnP02zY |