Beloved Mac developers and long time bloggers, Brent Simmons and Manton Reece have launched JSON Feed. The take away for developers is as follows:
For most developers, JSON is far easier to read and write than XML. Developers may groan at picking up an XML parser, but decoding JSON is often just a single line of code.
So why should anyone care about this with respect to podcasts when Apple controls the ecosystem? Although its early days for the spec, our opinion is that innovation in a space with an established, albeit old spec is a healthy thing.
RSS is and continues to be a workable transportation method for podcast data, but even RSS–which has been around since 1999–needs enhancement. That’s why open source initiatives like syndicated.media exist to take podcast functionality and RSS to the next level (we’re closely watching this).
What impact does it have?
Does this mean that JSON Feed will make any significant impact? That remains to be seen, but we’re pleased to see people move the needle forward.
Co-creator, Manton Reece wrote about how JSON Feed relates to podcast functionality:
JSON Feed includes an attachments array, which is similar to the enclosure element in RSS that enabled podcasting. We love podcasting and included an example podcast feed in the JSON Feed specification.
How FeedPress supports JSON Feed
Experimental JSON support is live on FeedPress. JSON Feed is generated every time the XML feed is refreshed and is not a replication from the source, it’s a creation. The JSON feed validates and it handles podcasts on RSS and Atom.
There is nothing FeedPress customers need to do in order to get JSON compatible feeds. Simply append the
?format=json parameter to the end of your RSS feed.
Here’s an example URL: https://podcast.hologramradio.org/master?format=json
FeedPress customers are encouraged to test this with compatible RSS readers and Podcast apps. We’d love to hear your feedback.
[Tweet “FeedPress adds JSON Feed Support”]
Update: As of May 31, 2017, the feed_url paramter has been added. As per JSON Feed spec documentation, it’s highly recommended: