News for hackers. Stuff that matters.
Re:The Sorry State of Peer-to-Peer iOS-to-Android connectivity by zurn on Sunday April 27, 2014 @03:48PM (#7656510)
WebRTC works pretty well on Android.

But apparently Apple has kept it out of iOS Safari and doesn't allow other browsers to implement it?

Re:The Sorry State of Peer-to-Peer iOS-to-Android connectivity by foo2312 on Sunday April 27, 2014 @07:24PM (#7657413)
As far as I am aware, Apple does not seem to have a policy preventing this type of work. There was a fairly well-publicized release of an experimental codebase from Ericsson:

http://labs.ericsson.com/apps/bowser,

which has since been retired (although as far as I know, not due to any conflict with Apple):

http://labs.ericsson.com/blog/retiring-bowser.

Re:The Sorry State of Peer-to-Peer iOS-to-Android connectivity by higherpurpose on Sunday April 27, 2014 @04:06PM (#7656607)
Apple needs to allow serious browser competition on iOS. But of course they won't until more developers and users start asking them for it.
Re:The Sorry State of Peer-to-Peer iOS-to-Android connectivity by derwildemomo on Sunday April 27, 2014 @03:59PM (#7656569)
Forgot about that one, thank you. Another one on the list, unfortunately.
Re:The Sorry State of Peer-to-Peer iOS-to-Android connectivity by jmspring on Sunday April 27, 2014 @06:24PM (#7657222)
WebRTC does not currently exist on the desktop Safari either. I'm sure if a 3rd party wanted to implement WebRTC in a browser for iOS, they are probably welcome to do so.
Re:The Sorry State of Peer-to-Peer iOS-to-Android connectivity by nl on Sunday April 27, 2014 @09:51PM (#7657839)
That's a different layer - it runs on top of an already established network. This is about establishing some kind of connection.

WebRTC also requires a central server for discovery (typically overy HTTP I think?). It maybe possible to replace that with Bluetooth LE, but then the WebRTC connections to each other will need to run over an TCP network.