You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when spotify button is clicked, it opens the open.spotify.com link in browser.
First it gets opened in browser, and then you can open it in desktop app via website. This increases number of steps for those having official spotify desktop app.
The desktop app can handle spotify:// URI links. Is there a way that spotify button provides a spotify:// URI instead of open.spotify.com. So, upon clicking Spotify in Mousai, it would directly open in spotify desktop app instead of web browser.
The text was updated successfully, but these errors were encountered:
If the spotify app is installed, then open the spotify: uri else open the open.spotify.com link directly. If spotify app is available or not can not be checked inside a flatpak sandbox, maybe just add a preference option to open spotify links in desktop app.
This is harder to fix than I thought without going to the preferences route, since there is no easy or non-hacky way for a Flatpak app to get other installed apps.
This is harder to fix than I thought without going to the preferences route, since there is no easy or non-hacky way for a Flatpak app to get other installed apps.
Junction somehow gets around it, although I'm not sure how they do it. I think one definitely needs to build the app with the --talk-name=org.freedesktop.Flatpak permission.
Currently when spotify button is clicked, it opens the open.spotify.com link in browser.
First it gets opened in browser, and then you can open it in desktop app via website. This increases number of steps for those having official spotify desktop app.
The desktop app can handle spotify:// URI links. Is there a way that spotify button provides a spotify:// URI instead of open.spotify.com. So, upon clicking Spotify in Mousai, it would directly open in spotify desktop app instead of web browser.
The text was updated successfully, but these errors were encountered: