❌

Normal view

Indie Podcast Apps Not Growing

28 August 2026 at 19:47

Dustin Bluck:

Independent podcast apps are not growing as a category. This is not a particular secret, but perhaps you haven’t seen it stated explicitly. It’s the sort of thing that has to be inferred, but there’s plenty of available data if you look for it. While the podcasting sector has seen growth, this has occurred almost entirely on platforms like YouTube, and the independent podcast app userbase has mostly just stood still.

[…]

I’m sure somewhere out there a 21-year-old just downloaded Castro or Pocket Casts for the first time and thinks RSS feeds are awesome (if you are this person, please email me). But every number I can see indicates the userbase is both static and aging. Every new customer I talk to has used some combination of Apple Podcasts, Overcast, Pocket Casts, or Castro for at least the last 5 years if not the last 10.

[…]

Perhaps there are healthy businesses that get very few new users but instead gracefully age with the ones they have. Ferrari maybe? Buddy, smartphone apps are not one of those businesses.

[…]

I would rather work on flashy features to capture new users, but, reality being what it is, I have to think about things in terms of both the health of the ecosystem and what will actually help retain existing podcast app users.

Nick Heer:

Anil Dash wrote, in 2014, that the simple phrase wherever you get your podcasts is a “radical statement”:

[…] Because what it represents is the triumph of exactly the kind of technology that’s supposed to be impossible: open, empowering tech that’s not owned by any one company, that can’t be controlled by any one company, and that allows people to have ownership over their work and their relationship with their audience.

Video podcasting changes that. In its simplest form, it is just a YouTube channel, which means it is siloed and controlled by Google. Spotify also supports video but only in its app.

Ilya Birman:

So Marco described a problem. What if someone manually asks to download an episode when they already have three downloaded? You can’t just immediately delete it to keep things tidy. So what do you do? Marco added a special hidden “episode downloaded manually” flag to the database, so those episodes would not count towards the limit.

This is one more example of how even the most seemingly trivial features require thinking through and accounting for different cases that may not be obvious at first glance. Every user interface designer and product designer should collect and absorb examples like this.

[…]

Finally, Marco’s wife Tiff suggests a solution to all the problems: just don’t let users download more episodes, she said, and show them a message, roughly: “Your episode limit is three, but this would be the fourth, denied”.

Marco liked the solution. I didn’t. Sure, it solves Marco’s problems, but not the user’s.

Marcin Wichary:

Birman presents this as “Let me click,” but I wanted to offer two alternative/​complementary principles that helped me before:

  • Let me do things in any order. Here’s Google Home app, where I can change the temperature and the time for holding – but if I change the time first, it frustratingly resets when I subsequently change the temperature. It forces one specific order in an interface that suggests any order is okay[…]
  • The current action has the most momentum. The user is right there, active, tapping on things, wanting to get stuff done. If Overcast indeed throws a “your episode limit is three” message, then it forces the user to remember how to get to the settings and change it. The momentum is lost. The decisions of past me should not be as important as the decisions of present me.

Marco Arment:

FWIW, the entire strict-limit feature is gone in the pending update (awaiting App Store review). EVERYONE hated it.

Now I’m just displaying the added-manually status in the UI and allowing it to be toggled manually in the “…” menu.

Marco Arment:

I’ve needed to evolve my expectations for what my role in Overcast is.

After building up a large, passionate userbase over a very long time, it’s not really entirely mine anymore. I can’t just do whatever I want with it.

And the growth era of open/RSS/indie/whatever podcast apps is over. The business is now about serving and retaining my existing customers for as long as possible.

So I can add things here and there, very carefully, but I can’t really change anything significant.

Previously:

Castro’s Customer Support Lessons

6 July 2026 at 19:45

Dustin Bluck (archive link, Hacker News):

I had an idea when I bought Castro that human support based around actual user experience was an easy differentiator. I’ve rarely gotten useful answers from support from services I use. I thought if I used my own product every day, read every email and answered it thoughtfully, people would appreciate this, and it would build some degree of loyalty and appreciation.

[…]

However, what I found is this whole thing didn’t work as I thought it would. Sure sometimes we were able to wow customers, particularly when we responded right away with an exact fix for them. But the vast majority of our honest, thoughtful answers were deeply unsatisfactory to users, and it often annoyed them more than anything else.

[…]

Customers email us with confusion about how podcasts work, how the App Store works, how their Mac works, and any number of tangential issues. What tends to happen is the same users do this over and over, and once they find out we answer, the requests get more frequent and more burdensome.

[…]

To the user, any response aside from “Okay, we’re going to build that right now” is meh-to-negative. Various honest responses, such as “I thought about this or tried it in the past and it unfortunately didn’t work very well” are not going to knock their socks off. These just don’t do much in terms of loyalty and rapport.

[…]

Avoiding explanations and specifics tends to get a neutral response and doesn’t suck anyone in or waste too much time. In other words, the best approach for us is what most companies do. Because building loyalty or rapport at the moment something isn’t working and the user is frustrated hasn’t worked. The real positive experience comes when you actually improve the product, so that’s where we’re spending our time.

I have definitely seen all these categories of customer interactions, but I don’t agree with the conclusion. Yes, in the end you want to be improving the product, but I don’t think that’s fully separable from interacting with customers as humans. I’ve found spending time on customer support incredibly valuable for making my products better. Even a lone report of an issue can often lead to a fix and learning something important that has wider implications. It’s also enjoyable and motivational to hear about real people making use of what I’ve built or to turn around someone who started with a negative view. And it seems to help with marketing, too.

I also see a correlation with the apps that I use—the better ones tend to also have good support. That said, I use a podcast app that famously doesn’t offer support. There are different situations, and there’s more than one way to a good product and a successful business.

I do think there’s an art to all this. Not everything can be measured, and there’s more to it than just committing to answering e-mails thoughtfully. You need to set boundaries and steer the interactions to make them productive, efficient, and satisfying for both sides. I’m still learning.

Previously:

Update (2026-07-07): Jeff Johnson:

This is what you get from the free with IAP business model: most of your support emails are from freeloaders!

My apps are upfront paid, thus most of my support emails are from customers. I don’t get overloaded with emails, and paid customers are more incentivized to solve issues with you, because they’ve invested money into the app.

Vitor:

I find myself agreeing with you that customer support is valuable and we should do it. But over the years I have also realised that, in a way, being good at support is punishing. I’ll explain[…]

❌