Same, I'm not committing any resources to these apis until they are more widely supported. Then again, I'm probably not the target audience at this point.
You would not. MS and Google however (partially) do with their products, and that covers quite a wide range of users who will switch browser because something did not work.
Fortunately (or ironically) Apple slow adaption of new APIs and their restrictions on iOS browsers will make this effort incomplete. Or at least would force google not to push these as they want but with some cross references.
That's of course if I am not missing a point here.
Project Fugu DevRel here (https://twitter.com/tomayac)! The way to approach this is with progressive enhancement wherever possible. See https://web.dev/svgcode/ for an example where I try to make this concrete. Well noting that if your app depends on hardware APIs like WebHID, this approach obviously won’t work. What you can always do, though, is let other browser vendors know how and why you want them to support Fugu APIs.
Rather they should only do what you let them. It's nonsensical that mobile OSes don't let you fake certain permissions being enabled (for example having a location spoofing option).
