Tag: developers

Nearly two months after my Apple Watch Series 3 review, my main complaint still stands: it remains prohibitively difficult to play back podcasts from the device.

The native iOS Podcasts app has no equivalent on the Watch, and the “big player” third-party clients don’t support transferring podcast episodes to the wearable device. Overcast removed this feature in the run-up to watchOS 4, citing critical APIs that Apple had removed.

There are several smaller podcast clients that try to work around WatchKit’s hamstrung audio APIs. I’ve tried both Watchcast and Watch Player. The latter app has made some strides recently by allowing direct podcast browsing and downloading on the Watch itself, but the entire process is very clunky. It’s a bad sign when an app’s first-launch experience includes a twelve-page tutorial packed with caveats and disclaimers. During a recent test, I was able to successfully download an episode, but actually listening to the show proved impossible; I would tap the play button, but nothing would happen.

Users shouldn’t blame third-party developers for the Watch’s podcast unfriendliness. The real question here? In the two-and-a-half years since the Watch first launched, why hasn’t Apple prioritized podcasts? Here are some possible explanations:

• The Apple Watch is too resource-constrained to support podcast playback. It’s true; the original, “Series 0” Apple Watch was severely limited in both speed and battery life. But that’s no longer the case with the Series 3. In six weeks of daily Watch use, including frequent workouts, my battery hasn’t dipped below 50%—let alone dwindled anywhere near a complete discharge. And given how snappily the new model launches apps, it seems unlikely that CPU speed remains a concern.
• Podcasts aren’t popular enough. Once upon a time, podcasts were a niche medium, beloved by nerds but foreign to everyday users. That’s not the case now. Podcast audiences continue to grow, and runaway hits like Serial prove the format’s broad appeal.
• A related guess: Apple is simply engineering-constrained, and podcasts were low on the punch list. We’ve heard rumors that Apple shuffles engineers between projects to hit its deadlines. And many projects’ engineering teams are surprisingly small. Given these limited skilled resources, it seems possible (even likely?) that Apple simply hasn’t gotten around to building a legit podcast app (and/or serviceable public APIs) yet.

Whatever Apple’s reasoning, I hope the Watch’s podcast situation gets remedied soon. I’m tired of strapping on an iPhone fanny pack every time I go running. ■