[GH-ISSUE #457] Podcast Support #256

Closed
opened 2026-03-02 23:46:00 +03:00 by kerem · 6 comments
Owner

Originally created by @fwastring on GitHub (May 28, 2024).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/457

Is your feature already implemented in the latest master?
No

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
I would like to have podcast support available in the app. When I search for podcasts, I don't get any of the results I'm expecting. Possibly another pane with podcast results only. I haven't dabbled with Spotifys Podcast API so I'm not sure how the implementation would be done.

Originally created by @fwastring on GitHub (May 28, 2024). Original GitHub issue: https://github.com/aome510/spotify-player/issues/457 **Is your feature already implemented in the latest `master`?** No **Is your feature request related to a problem? Please describe.** No **Describe the solution you'd like** I would like to have podcast support available in the app. When I search for podcasts, I don't get any of the results I'm expecting. Possibly another pane with podcast results only. I haven't dabbled with Spotifys Podcast API so I'm not sure how the implementation would be done.
kerem 2026-03-02 23:46:00 +03:00
Author
Owner

@vannotz commented on GitHub (May 30, 2024):

It seems to kinda already support it? If I'm playing a podcast on my phone, then open spotify-player on the desktop and just hit "space" without actually choosing a song, the podcast I was listing to will start playing but nothing will show on playback. So I guess it technically already has that functionality, just no search.

<!-- gh-comment-id:2138664840 --> @vannotz commented on GitHub (May 30, 2024): It seems to kinda already support it? If I'm playing a podcast on my phone, then open spotify-player on the desktop and just hit "space" without actually choosing a song, the podcast I was listing to will start playing but nothing will show on playback. So I guess it technically already has that functionality, just no search.
Author
Owner

@fwastring commented on GitHub (May 30, 2024):

I've seen that too! I was referring to functionality where you could search for, browse and play podcasts. But playback if started from another device seems supported!

<!-- gh-comment-id:2138815078 --> @fwastring commented on GitHub (May 30, 2024): I've seen that too! I was referring to functionality where you could search for, browse and play podcasts. But playback if started from another device seems supported!
Author
Owner

@aome510 commented on GitHub (May 31, 2024):

Related:

Podcast is not my priority since I never use it personally. PRs are highly welcome though!

<!-- gh-comment-id:2141161735 --> @aome510 commented on GitHub (May 31, 2024): Related: - https://github.com/aome510/spotify-player/issues/423 - https://github.com/aome510/spotify-player/issues/359 Podcast is not my priority since I never use it personally. PRs are highly welcome though!
Author
Owner

@fwastring commented on GitHub (Jun 4, 2024):

Do you have any tips for how I would implement it? Do you think it would be a lot of work? @aome510

<!-- gh-comment-id:2147844640 --> @fwastring commented on GitHub (Jun 4, 2024): Do you have any tips for how I would implement it? Do you think it would be a lot of work? @aome510
Author
Owner

@thenbe commented on GitHub (Jun 8, 2024):

Do you have any tips

@fwastring From a UX perspective, I feel like podcasts and podcast_episodes should be top-level entities. For instance if a user searches for foo:

They should see results from these types:

tracks
albums
artists
playlists
+podcasts
+podcast_episodes

Actions (context menu)

A podcast can have similar actions* to an artist. Some modifications would be required:

-GoToArtistRadio
-CopyArtistLink
+CopyPodcastLink
Follow

A podcast_episode can have similar actions* to a track. Some modifications would be required:

-GoToArtist
-GoToAlbum
-GoToTrackRadio
+GoToPodcast
CopyTrackLink
AddToPlaylist
AddToQueue
-AddToLikedTracks

* By actions, I'm referring to the menu you can invoke by pressing g a when hovering over a list item (e.g. in the search results).

Pages

The podcast detail page can be simple. It can contain a single list of podcast_episodes (similar in layout to the album detail page).

I don't see the need for podcast_episode detail page. Similar to how a track does not currently have it's own page.

<!-- gh-comment-id:2156052760 --> @thenbe commented on GitHub (Jun 8, 2024): > Do you have any tips @fwastring From a UX perspective, I feel like `podcasts` and `podcast_episodes` should be top-level entities. For instance if a user searches for `foo`: They should see results from these types: ```diff tracks albums artists playlists +podcasts +podcast_episodes ``` ## Actions (context menu) A `podcast` can have similar actions\* to an `artist`. Some modifications would be required: ```diff -GoToArtistRadio -CopyArtistLink +CopyPodcastLink Follow ``` A `podcast_episode` can have similar actions\* to a `track`. Some modifications would be required: ```diff -GoToArtist -GoToAlbum -GoToTrackRadio +GoToPodcast CopyTrackLink AddToPlaylist AddToQueue -AddToLikedTracks ``` \* By actions, I'm referring to the menu you can invoke by pressing `g a` when hovering over a list item (e.g. in the search results). ## Pages The `podcast` detail page can be simple. It can contain a single list of `podcast_episodes` (similar in layout to the `album` detail page). I don't see the need for `podcast_episode` detail page. Similar to how a `track` does not currently have it's own page.
Author
Owner

@aome510 commented on GitHub (Jun 8, 2024):

Thanks @thenbe for the suggestions!

Do you have any tips for how I would implement it? Do you think it would be a lot of work? @aome510

Sorry I missed the message. It should be relatively straightforward to add support for podcast as you can follow the already established patterns in the codebase. This is not a "good first issue" in a way that the implementation will need to touch many places in the codebase, which might require a certain level of familiarity.

<!-- gh-comment-id:2156072797 --> @aome510 commented on GitHub (Jun 8, 2024): Thanks @thenbe for the suggestions! > Do you have any tips for how I would implement it? Do you think it would be a lot of work? @aome510 Sorry I missed the message. It should be relatively straightforward to add support for podcast as you can follow the already established patterns in the codebase. This is not a "good first issue" in a way that the implementation will need to touch many places in the codebase, which might require a certain level of familiarity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-player#256
No description provided.