• Resolved encaf1

    (@encaf1)


    I’ve found that I can modify the subscription plugin with a simple change to allow a subscription button that will work with non-iTunes podcasts.

    The essence of the change is to simply use a “podcast://” URL scheme name.

    Not sure if this is the right place for feature requests, but this simple addition would be a great help for shows that don’t bother with the iTunes store, but who still want to appear on the IOS app.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Shawn

    (@shawnogordo)

    I will pass this on to the Blubrry dev team. Thanks for the feedback!

    Plugin Author Angelo Mandato

    (@amandato)

    Hello @encaf1,

    Thanks for the suggestion! We are aware of the podcast:// URL schema protocol, it has been around since as early as 2005. Let me explain why we did not include it. There are four problems…

    Non-device support: If you do not have an application on your device that recognizes the podcast protocol, then the user will receive an error. All of the other subscribe URLs will go to a web page with a convenient message stating as such. This is a UX problem.

    Lack of support from apps: Last time we looked only a small handful of applications supported it. None of the top 10 apps in our statistics were on the list. The top 10 apps either support the Apple podcasts/Subscribe on Android URLS and/or they provide their own subscribe URLs.

    No standard protocol: This is the biggest problem today, it is assumed that podcast:// is actually https://. Today websites should be https. It is true the app developer who supports podcast could try both http and https, or maybe everyone should start assuming it should be https, but it is a complication that the protocol itself cannot address. One solution is to also include the port number, e.g podcast://exmaple.com:443/feed/

    podcast:// is not in a standard RFC: If you are not aware, RFC stands for request for comments, the IETF organization is responsible for publishing the RFCs, it is a standard that all protocols related to the Internet use, it is a set or procedures for standardizing a protocol for applications to use. Until this is done, the first 3 problems are left to each developer to decide what is the correct way to handle podcast:// protocol.

    We will add this as a feature TODO, but because there is no official standard we may have to offer it as an option for advance users.

    Thread Starter encaf1

    (@encaf1)

    Fair points, all, and I totally agree. I’d much rather use standards, but since nothing has emerged and there is a significant install base already, we do what we must in the meantime.

    There isn’t a way to use your subscribe plugin for IOS devices unless it is in iTunes. So, a significant part of the market is inaccessible. The podcast:// schema has indeed been around for a long time (as has pcast://, itunes://, itpc:// etc), and while it’s not a standard, it actually *works*.

    Podcasting has, unfortunately, been underrepresented in standards organizations and much of its history is one of large companies (e.g. Apple) usurping it and all but claiming to control it, yet refusing to actually do anything to promote any sort of standards or advancement. (This has been a pain for me for a while.. ?? )

    You include mechanisms to use the iTunes store, Google Podcasts and an Android scheme — none of which are particularly “standard”. I think including an IOS hook — especially when it is as simple as it is, a very few lines — seems in keeping with currently practices.

    Thanks for your support! I truly appreciate the Powerpress plugin and all your efforts.

    Plugin Author Angelo Mandato

    (@amandato)

    Hello @encaf1,

    Android app development allows for intent filters, that has allowed for the use of custom domain names and applications being able to handle intention clicks to those domains, a.g. subscribeonandroid.com. Apple does not have the same concept which is why the podcast:// would be helpful for iOS devices. I wish Apple allowed more interaction with the browser and other applications. The way around that as you noted is to use an unknown schema in the URLs, then the iOS browser will let another application on the device handle it since the browser itself cannot.

    We added this to the feature TODO list but since this could be used by the visitor of the website to click and be left stranded for those without a supported app on their device, we have to be careful that only users who understand this use it.

    Your appreciation is greatly appreciated!!!
    Angelo

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘IOS Podcast specific subscribe button for non-iTunes podcasts’ is closed to new replies.