Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore addition of Custom URL Scheme for Bowser #41

Closed
rondomondo opened this issue Apr 27, 2015 · 1 comment
Closed

Explore addition of Custom URL Scheme for Bowser #41

rondomondo opened this issue Apr 27, 2015 · 1 comment

Comments

@rondomondo
Copy link

Enhancement: Custom URL Scheme for Bowser

Candidates:

bowser:// or webrtc:// or ...

I wanted to float the idea of adding a custom scheme for bowser into the App config.

For recap:
A custom scheme would allow an app to be opened by the user clicking on a URL that contains the registered scheme.

Example

<a href="bowser://room/join?ABCD1234">Chat to Dave now</a>

  • this would open bowser, kick off the client chat session and try to join room named 'ABCD1234'

or perhaps,

<a href="webrtc://room/join?ABCD1234">Chat to Dave now</a>

<a href="fb://">Open FB App on your iPhone</a>

There are a bunch of examples on the web and some examples from the big players like facebook, pinterest etc., here Custom URL Schemes (iOS): Pintrest, Google+, Instagram, tumblr

A Comprehensive Guide to URL Schemes

I am thinking that from an adoption or pervasive acceptance perspective, that building in the ability to share, create and prompt users to engage in WebRTC session offers by having something as simple as clicking on a link in demos would be useful. Especially as the avenues we have to distribute HTML embedded links is available via all the usual suspects as SMS, iMessage, IM type apps etc.

@rondomondo
Copy link
Author

Just noticed that this has been done since I last looked at issues. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant