Skip to main content

Why I do not want to use another iOS podcast client than Castro

Castro is still pretty fresh in the iOS App Store (currently version 1.0.6, first release came in late 2013) but has already beaten the competitors in my opinion. Here is why:
  • Castro is winning by simplicity. Focusing on features and using using the fresh iOS 7 design.
  • Great simple feed search engine (worked perfect for my favorite German podcasts).
  • Push notification works.
  • It is stable.
  • Once again, I like the simple intuitive design. 
Other settled podcast player in iOS market help Castro to succeed by not fixing their issues. I am coming from Instacast and this is why I think it does not fit anymore:
  • When I open Instacast by sliding push messages on my lock screen it crashes nearly up to 50%.
  • Up Next Feature does not work for me. Lists are useless, everything works just through Up Next.
  • Sync feature with its OS X app is a mess, similar to Apple’s Podcast app.
This is why Apple’s Podcast app does not work either:
  • Sync with other iOS and OS X devices is a mess.
  • Push notification is not existing (Is it? I have never seen any).
  • Navigation is too complicated. 
By using Castro I completely discarded thinking about syncing podcasts on several devices, I am using Airplay devices like AppleTV or AirServer.

My ideas to improve Castro:

  • Add an option for continuously playing all my podcast episodes, instead of stopping after each one.
  • Add support for password protected feeds.
  • Start playing an episode immediately by opening the episode. I do not want to tap play after opening it. 
  • Integrate Airplay button in the lower control bar. 

Update:

  • Add missing sharing options to share your current podcast episode on Twitter.
  • Double Tap to play episodes immediately instead of opening it.

Popular posts from this blog

How to get started with Windows Server AppFabric easily

In my opinion it is really hard to get started with Windows Server AppFabric. There is good material, but it is shuffled around in different sources. A good intro can you find here: this all-in-one intro by Scott Hanslmann  this caching intro by Wade Wegener  Additional helpful resources are Microsoft's Introduction Part 1 and Microsoft's Introduction Part 2 by Jon Flanders  Pluralsight's Hosting Fundamentals   Pluralsight's Caching Introduction   Microsoft's Caching Documentation   Good books are Microsoft Windows Server AppFabric Cookbook   and Pro Windows Server: AppFabric Please also watch out for software updates, currently there is CU 4 . To keep yourself updated subscribe to Distributed Services News Feed . Updated my list on 11.03.2014 with one more Download the Windows Server AppFabric Samples

How to fix Windows Server AppFabric Dashboard on Windows Server 2012 / Windows 8

Windows Server AppFabric is a great enhancement for IIS and its caching capabilities are great for .NET applications. But currently there is a very annoying bug regarding its monitoring UI, so called “Dashboard”. Especially for me as a non WF guy (I am actually just working with WCF) it was really hard to figure it out. Hence, many thanks to Gianluca from Distributed Services at Microsoft! Windows Server AppFabric Dashboard does not work on Windows Server 2012 / Windows 8. You will receive this error message "Unable to cast object of type 'System.Management.Automation.PSCustomObject' to type 'Microsoft.ApplicationServer.Management.Data.GroupByInfo'." This error will cause that you cannot see any request statistics neither WF nor for WCF: The reason is, I quote Microsoft here: "[...] the root cause is a powershell script embedded in AF code that returns different results when ran on Windows 2012. This script is about statistics for Idle & per...

Clean up AppFabric Dashboard Part 2: Duplicate collection entry in Web.config

In Part one I have already described how to remove phantom apps here on more supplement. These phantom apps could also remain in the AppFabric Monitoring db: Just delete no longer needed entries in this table. Duplicate collection entry When you receive this kind of issue, like "[...] Cannot add duplicate collection entry [...]" you have defined the a configuration section twice in two different Web.config files in different places in your file system. Clear One easy solution is to use a clear statement . Searching for the inherited element There is a post in Microsoft's documentation which is explaining how to do it. Visual Studio in debug mode When you are working with Visual Studio in debug mode, which means you are just pressing F5 to run it on your local IIS instead of publishing it to a web server, you should keep in mind that e.g. your obj folder might contain more copies of your Web.config file. This could lead into this duplicate collectio...