Keep in mind that if you have an out-of-OS scanner, like the Physical Web is. You can find things like BLE beacons sending URLs or mDNS URLs and just open the browser when the user picks one. There is a very big line drawn between scanning for URLS and building that into the 'web platform' which tends to think of things through the DOM model and not so much as a UX that ends up dropping you into the browser. Scott Scott Jenson | Chrome UX | scottj@google.com | +1 650 265-7174 On Mon, Oct 24, 2016 at 11:20 AM, Benjamin Francis <bfrancis@mozilla.com> wrote: > > On 24 October 2016 at 19:15, Benjamin Francis <bfrancis@mozilla.com> > wrote: > >> On 24 October 2016 at 18:12, Jason Proctor <jason@mono.hm> wrote: >> >>> i don't think any of the Android browsers support mDNS (and it's high >>> time .local was a standard, IMHO!) but the NsdManager class makes API level >>> integration straightforward. works for me. >>> >>> (btw i think there is an Android kernel issue which prevents mDNS >>> multicasts from being received locally, which is quite annoying. affected >>> me on FirefoxOS (which uses the Android kernel) also.) >>> >> >> Yeah, this is weird because I understood that Chromecast switched from >> using DIAL to mDNS for discovery some time ago and I thought they'd now >> built the functionality of the Chromecast plugin directly into Chrome. So >> somehow Chromecast functionality is using mDNS but it isn't available >> globally at the OS or browser level. >> >> (I don't think Firefox yet supports it at the browser level either, it >> relies on OS support). >> >> > There's also this API for Chrome Apps/Extensions > https://developer.chrome.com/apps/mdns but general support on Chrome for > Android is not there https://bugs.chromium.org/p/ > chromium/issues/detail?id=405925 > >
Received on Tuesday, 25 October 2016 00:28:33 UTC