<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Web playback API and casting in Spotify for Developers</title>
    <link>https://community.spotify.com/t5/Spotify-for-Developers/Web-playback-API-and-casting/m-p/5054354#M1353</link>
    <description>&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;I understand that we would require written permission from Spotify for a commercial use for the playback API but I was just wondering what the impact could potentially be if we also will be baking cast functionality into the page too? Will there be any performance/licensing issues related to this?&lt;/P&gt;</description>
    <pubDate>Fri, 16 Oct 2020 08:42:45 GMT</pubDate>
    <dc:creator>cal_phntm</dc:creator>
    <dc:date>2020-10-16T08:42:45Z</dc:date>
    <item>
      <title>Web playback API and casting</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Web-playback-API-and-casting/m-p/5054354#M1353</link>
      <description>&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;I understand that we would require written permission from Spotify for a commercial use for the playback API but I was just wondering what the impact could potentially be if we also will be baking cast functionality into the page too? Will there be any performance/licensing issues related to this?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Oct 2020 08:42:45 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Web-playback-API-and-casting/m-p/5054354#M1353</guid>
      <dc:creator>cal_phntm</dc:creator>
      <dc:date>2020-10-16T08:42:45Z</dc:date>
    </item>
  </channel>
</rss>

