4 ms·

> No, all major operating systems support scheme handlers. No, you know that rarely works out in practice and is not what I meant. Take this example: https://

> No, all major operating systems support scheme handlers. No, you know that rarely works out in practice and is not what I meant. Take this example: https://news.ycombinator.com/reply?id=32814887&goto=threads%3Fid%3Dboomlinde%2332814887 https://news.ycombinator.com/reply?id=32814887&goto=threads%... Or: https://old.reddit.com/r/Gloomhaven/top/?t=month https://old.reddit.com/r/Gloomhaven/top/?t=month But can we do something like this? file://Users/Me/Pictures/?filter=cats&sort=new Or this? pixelmator.app/lastdocument/thumbnail

jeroenhd 4y ago
If you control the application/backend then I don't see why you would need HTTP(S) URLs to get the right content. Android actually allows registering HTTP(S) URLs with certain domains and wildcards (https://developer.android.com/training/app-links https://developer.android.com/training/app-links). Not a big fan of this "validate a token through Google to skip the app choice dialogue" approach but luckily Firefox always prompts before opening a registered app link anyway. iOS supports a similar feature. It's up to browsers on other platforms to implement their own support if this is something one would want to add to the browser.
boomlinde 4y ago
> No, you know that rarely works out in practice and is not what I meant. No, as far as I know it works very well in practice and thus I don't know what you mean. Take this example. Steam has registered as a handler for the steam scheme on my PC. Any other app can open e.g. steam://store/655480 to link to a game in Steam. It's up to the scheme handler how the URI works. Steam supports a bunch of different actions and forms of deep linking via the steam scheme. Here's what Slack supports via its scheme handler, for example: https://api.slack.com/reference/deep-linking#client https://api.slack.com/reference/deep-linking#client It's exactly what you're asking for, so I have no idea what compelled you to immediately dismiss what I was saying.

jeroenhd 4y ago

If you control the application/backend then I don't see why you would need HTTP(S) URLs to get the right content. Android actually allows registering HTTP(S) URLs with certain domains and wildcards (https://developer.android.com/training/app-links https://developer.android.com/training/app-links). Not a big fan of this "validate a token through Google to skip the app choice dialogue" approach but luckily Firefox always prompts before opening a registered app link anyway. iOS supports a similar feature. It's up to browsers on other platforms to implement their own support if this is something one would want to add to the browser.

boomlinde 4y ago

> No, you know that rarely works out in practice and is not what I meant. No, as far as I know it works very well in practice and thus I don't know what you mean. Take this example. Steam has registered as a handler for the steam scheme on my PC. Any other app can open e.g. steam://store/655480 to link to a game in Steam. It's up to the scheme handler how the URI works. Steam supports a bunch of different actions and forms of deep linking via the steam scheme. Here's what Slack supports via its scheme handler, for example: https://api.slack.com/reference/deep-linking#client https://api.slack.com/reference/deep-linking#client It's exactly what you're asking for, so I have no idea what compelled you to immediately dismiss what I was saying.