Re: [w3ctag/design-reviews] MiniApp URI Scheme (#478)

(NOTE: Not a full review)

The explainer only contains a what (in terms of solution), and lacks a why or what (in terms of problem) - could you take a look at our [explainers explainer](https://github.com/w3ctag/w3ctag.github.io/blob/master/explainers.md) and revise?

Possibly blunt but curious question - it seems the "dereferencing" process ends up with a standard HTTP(s) URL. Wouldn't using that as is make it more accessible to end-users? This would trip unless you have a runtime (which would be also presumably, be a browser) - it feels like this tripwire mechanism's main motivation is to make the user install the runtime (in which case, what does this runtime provide that the current browser does not?), which I'm not sure is something that I personally would agree with.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/478#issuecomment-592287007