by chris_overseas on 9/30/2014, 1:58:48 PM
by lnanek2 on 9/30/2014, 12:49:06 PM
Can't actually think of a case where I would want or need this. Even my Chrome tabs followed me around is kind of annoying lately, since I lookup different things different places without much interest in them elsewhere. E.g. I'm not going to read HN on my phone.
by LazerBear on 9/30/2014, 1:49:57 PM
I think this is fantastic, but I couldn't find API docs / tutorial anywhere on your site. Demonstrating use cases is important, but I don't think it's enough to get developers to download / register.
by coreymgilmore on 9/30/2014, 2:46:44 PM
Reminds me (in a way) of Chrome Racer. (http://www.chrome.com/racer). Could this be using WebRTC for the fast device-device communication?
by shrig94 on 9/30/2014, 4:18:19 PM
It reminds me a lot of this awesome, open source, swiping library developed at the MIT Media Lab: https://github.com/Swyp/swyp
by zillwc on 9/30/2014, 1:27:59 PM
I couldn't get this to work between a S5 & Nexus5. What are the requirements? Same wifi? NFC or Bluetooth enabled? How does it know what sides the devices are on?
by sktrdie on 9/30/2014, 12:33:05 PM
I can't see the use case for wanting to send some information between devices this way. Perhaps PONG or other types of video games?
by andreasklinger on 9/30/2014, 1:04:01 PM
Love this. Opens up a lot of very native interactions. Eg. snipping a document to the larger tablet.
This reminds me of Blinkendroid https://code.google.com/p/blinkendroid/ which was the first time I'd seen multiple devices interact with each other like this. Sadly that project never managed to get much traction despite how much potential it had.