Overcast: Replace features users don’t use
Published
In his 2019 update, Overcast creator Marco Arment explains replacing Twitter recommendations with suggestions based on podcast subscriptions, adjusting clip-sharing limits, and delivering platform work incrementally. This is a historical product case study, not a description of the app today.
What to take into your own app
Measure the useful action
Arment reported that 10% of active users connected Twitter, while 0.2% of new podcast subscriptions came through its recommendations. He replaced that integration with recommendations based on subscription patterns.
Revisit the first limit
Overcast’s sharing limit grew from 60 to 90 seconds because the shorter clips could cut off a thought. The change followed practical use rather than the original guess.
Sequence work around capacity
Technical debt and operating-system changes slowed planned releases. Arment described shipping platform work incrementally while continuing improvements to the existing app.
Read the evidence carefully
The usage figures and assessment of the replacement are Arment’s own account. The essay supplies no raw analytics or controlled comparison establishing an improvement.
A small experiment to try
RankBlob exercise: pick one feature with a clear intended outcome. Compare how many people can access it, try it, and complete that outcome. Read a few support conversations for context. Decide whether to improve, replace, or retire it, then record the outcome you will watch after the change. Low usage alone is not a reason to remove an essential accessibility or safety feature.
The original source
Good ideas get better together.
Enjoying the read? Meet indie app builders, compare notes, and share what you’re working on.