So none of this functionality would work for mobile browsers? Or can you at least receive messages somehow?
After some googling I found OpenWebRTC which says "WebRTC standard would transcend the pure browser environment and that native apps, implementing the same protocols and API's, would become an important part of the WebRTC ecosystem". But I thought the beauty of this would be transcending the need for native apps.
WebRTC works on android and will be supported by iOS 11, due to be released later in 2017.
> But I thought the beauty of this would be transcending the need for native apps.
Right now the only implementations of webrtc are web browsers so if you want to use webrtc on a server you have to run a browser environment like electron.
Right now the only implementations of webrtc are web browsers so if you want to use webrtc on a server you have to run a browser environment like electron.
Wait, that's not right, is it? There is a native implementation for iOS for example (demoed in this app: https://github.com/ISBX/apprtc-ios)
You're right. What I said didn't make sense. I was just trying to communicate that although webrtc is sold as a peer-to-peer technology that can avoid the use of intermediate servers, there are compelling use cases for client/server communication using webrtc and that requires a server-side webrtc implementation.
There are two webrtc implementations that I know of google's native implementation from chromium and openwebrtc. That project uses google's.
After some googling I found OpenWebRTC which says "WebRTC standard would transcend the pure browser environment and that native apps, implementing the same protocols and API's, would become an important part of the WebRTC ecosystem". But I thought the beauty of this would be transcending the need for native apps.