Podcasts are (generally, Spotify excluded) on an open standard. They're just RSS feeds. So, the content can be aggregated by anyone. So it's primarily the UI that will be different between different podcast players.
Sure but the hosting of that content isn't something a front end can solve.
Podcasts are already hosted by a variety of independent services. Google doesn't host any podcasts, at least as far as I am aware. In this case it really is a frontend-only problem.
The RSS feed points to the already hosted files. A lot of people host podcasts on services like libsyn or podbean. I don't think you can really host podcasts on Google; maybe hacked together on drive or something.
Google isn't hosting the podcasts.
Most of them are hosted by a service offered by Spotify.
Podcasts are (generally, Spotify excluded) on an open standard. They're just RSS feeds. So, the content can be aggregated by anyone. So it's primarily the UI that will be different between different podcast players.
Sure but the hosting of that content isn't something a front end can solve.
Podcasts are already hosted by a variety of independent services. Google doesn't host any podcasts, at least as far as I am aware. In this case it really is a frontend-only problem.
The RSS feed points to the already hosted files. A lot of people host podcasts on services like libsyn or podbean. I don't think you can really host podcasts on Google; maybe hacked together on drive or something.
Google isn't hosting the podcasts.
Most of them are hosted by a service offered by Spotify.