What we need from Apple to make standalone Apple Watch podcast apps

[MBCook]

A little over a week ago I found out that watchOS 4 would show you the now playing screen by default when listening to something and couldn’t wait to install it.

It’s fantastic to be able to easily look at my watch to change the volume or skip track or go forward or backward in a podcast.

But then Overcast came up. And just like Marco said I ended up on installing it on my watch because I lost the ability to change the volume. The now playing widget still let me change the volume and I can use the little buttons to skip forward and backward 30 seconds.

But now I can’t choose which podcast I’m listening to from the watch. I can’t put the app on my watch because it actively brakes a useful feature.

All because Apple won’t provide a simple API the people have been asking for for two years now? It’s sort of made sense in the original watchOS I guess but once we got the ability to run apps on the watch and access the digital crown seems like an obvious step that volume control should’ve been provided.

Please, Apple?

[zippergz]

I actually was thrilled when I realized that turning the Digital Crown didn’t adjust the volume in overcast on the watch. With the stock now playing widget, I found myself far more often accidentally adjusting the volume than doing it on purpose.

[mike-cardwell]

We keep hitting these barriers with proprietary software and locked down hardware. Hopefully the guys behind https://puri.sm/shop/librem-5/ will be a massive success and then turn around and do a smart-watch version.

[cbhl]

The entire time I was reading this piece, I couldn't help but think, "I wouldn't be surprised if Apple explicitly omitted that feature from the API to keep battery life reasonable on the Apple Watch."

Syncing progress for a podcast once every minute is excessive. Rather than polling, the app should update progress on the boundary transition (when starting the podcast app, when playback pauses, when bluetooth headphones disconnect, just before and after going to next/previous podcast).

[simplyluke]

Agreed on battery but it raises a question of UX vs battery life. I'd rather have a very useful watch for 6 hours than a mediocre one for 18 (less on the newer LTE models apparently). Audio is in many ways what should be the killer app for the watch. The watch should make it so I can go on a run and leave my phone at home, but omitting features like this make it a lot more difficult to fill that role.

The lifetime of a $350+++ Fitbit/notification screen is limited. Apple needs to improve the software side quickly - the hardware has come a long way from the first version.

Things like omitting error handling are just poor software design though.

[abalone]

He actually did ask for boundary transition events.[1] But he asked for polling too. Not sure why. You should be able to track progress from state change events alone, no?

[1] "Minimum fix: During WKAudioFilePlayer playback, wake the host app... on state-change events, such as pausing, seeking, and reaching the end of a file."

[tzahola]

Actually this is how the “now playing info center” on iOS works too: https://developer.apple.com/documentation/mediaplayer/mpnowp...

You’re supposed to set the metadata when your track starts and don’t touch it unless playback have finished or the user pauses it. The system updates the progress bar based on the duration and the playback rate you’ve set in the now playing info.

[rhinoceraptor]

The battery life (at least on my 7 month old series 2) is already much better than I need it to be. I’m a bit of an obsessive charger, but I almost never get it down past 40% by night time, even if I do a 2 hour bike ride workout with it.

[chime]

That's exactly what I thought too. Apple generally prefers to limit features in order to provide adequate performance/usability. The moment hardware gets advanced enough to handle the features without issues, they build them in.

[DavidAdams]

This article is a great example of how the Apple Watch has failed to reach its potential almost entirely because of indifferent software product design on Apple's part. I'm sure that ever Watch owner and developer can come up with a few other examples of things that the apple watch ought to be able to do but can't. When I bought my Apple Watch, I had assumed that I'd be able to use it to view and control the podcasts I'm listening to on my attached iPhone, which is even more fundamental than what's described in this blog post. But nope, not in any meaningful or useful way.

That being said, the Apple watch is still pretty good at pretty much one thing: when my phone beeps with a notification from one of many sources (SMS, eBay, Invision Trello, Messenger, etc) I need only glance at my watch. It's also a decent exercise tracker.

But it could be so much more. Sadly, I think Apple has probably missed it's best chance to recruit top developers, so it's likely it will be relegated to fancy text reader and step counter forever.

[speg]

How about viewing the monthly calendar more than a month in advance? I haven’t updated yet so I don’t know if they’ve fixed that.

[Spooky23]

Try using apps like Workflow, Homekit and others. There’s lots of Tim wresting highs to do with the watch. Podcasts are a dusty corner of the portfolio and barely get attention. I’m sure they’ll gobble the function into Apple Music.

I get what Marco is talking about here, but Overcast is already so complex it can barely play a podcast without crashing if interrupted. I don’t need that drama on my watch, where complex stuff either doesn’t work or sucks battery.

[atomical]

Average podcast is over 30 minutes, right? That means you would need to pull out your phone every 30 minutes to select the next podcast. Is that a big deal to you?

[eddieroger]

I don't think Apple needs to be told where their APIs are lacking for podcasting, as evident through the absence of standalone playback in their own Podcasts app, let alone an app at all. Either Apple can't figure out how to take the podcast experience and make it a good one on the Watch, or more likely (I think), the way it would need to work would make the Watch experience bad. I imagine they've got the "just play" experience for music heavily optimized, but the callbacks Marco mentions probably do terrible things to the Watch's battery and processor. Either way, this is a known desired thing, and if it could be done in a reasonable way, I'm sure they would have - they did put the 'pod' in podcast, after all.

[floatingatoll]

Apple has, in recent years, made explicit overtures to the developer community. They’ve welcomed feedback, requests, and concerns. They’ve acted on some of them. It’s absolutely appropriate to write a piece like this. Clearly summarizing a perceived need driven by a clear set of user stories permits Apple to evaluate viewpoints that may not be familiar.

[madeofpalk]

> as evident through the absence of standalone playback in their own Podcasts app, let alone an app at all

This is moot. If Apple wanted were to put their podcast app on Apple Watch they would just use internal APIs that third parties can't use, like the default music app.

[skygazer]

I would suggest it's probably a matter of time, rather than any judgement of infeasibility. Apple uses an iterative 80/20 rule approach to functionality. Podcasts didn't make the cut, because more people listen to music, and they hadn't even finished LTE streaming of Apple Music yet, and generally they service their internal apps/services first, before enabling competing third parties.

[mikerg87]

Podcasting on the phone lost the ability to rate/review podcasts. I suspect that they have simply prioritized talent to something else and this will languish for a while. If enough people squawk the plan that will make this great will get executed

[simonh]

That’s hard to accept given how utterly rubbish the Apple podcast app was for many years. It took them ages to get it right.

[synicalx]

I liked this piece right off the bat, not because the content is relevant to me but because it took responsibility and initiative, unlike many similar such articles I see on here.

The key is in the title "What we need from Apple TO MAKE standalone Apple Watch podcast apps", rather than "Why Apple needs to make a standalone Watch podcast app".

[askafriend]

This is an excellent point and I completely agree. I loved the way the Marco took initiative to propose actual viable technical solutions rather than just vague complaining like so many articles do.

[kwerk]

I’ve considered setting up a cron job to change select podcasts in iTunes to music so they sync with the watch. No position sync or fast forward but enough for a run.

Having spent 24 hours with the cellular watch and taken two runs without the iPhone, this is now a near necessity.

[discordance]

It's pretty sad that such a useful and obvious UX needs to be hacked up

[pragone]

That would be awesome if you wanted to share it!

[joshfarrant]

This is the single thing preventing me from buying an Apple Watch. I use Overcast to listen to podcasts on iOS and usually listen while running. As soon as Apple make these APIs available and Marco is able to create a watch app I'll be straight down the Apple Store to give Apple my £429.

[enraged_camel]

For me it's the battery. Having to charge a watch every 24-48 hours is a complete non-starter, regardless of its functionality. I don't want to carry more cables or charging stations with me wherever I go. It's the single-most point of stress, especially when I travel.

If the battery lasted 7-10 days, it would be perfect. That's about how long my business trips take, so I could charge it to full beforehand and not worry about it at all during the trip.

[Analemma_]

The Apple Watch might be selling well, but it's definitely not getting the kind of 3rd-party app support Apple probably wanted to see (me and everyone I know who has one likes it, but only uses notifications and fitness tracking).

With that in mind, it's crazy to me that Apple isn't beating down Marco's door to give him his requests. In the limited time that standalone Watch playback was in Overcast, even in its crappy implementation I used the hell out of it. Audio is one of the few home-run use cases for Watch apps, whereas in most other cases it's so much simpler and easier to just use your phone. Why wasn't that the first API implemented and the one polished to a shine? I hope they're not trying to make Apple Music the only available option.

[djrogers]

> even in its crappy implementation I used the hell out of it.

Then based on Marco's own stats, you were one of about 0.1% of users...

That said, now that the watch is free* from the tether of my iPhone, I'd love to listen to podcasts on it on a run while leaving my phone behind.

[1] https://marco.org/2017/08/10/removed-send-to-watch [2] relatively

[uptown]

Ironic that progress sync is listed as the deal-breaker. That's the one thing which doesn't seem to work properly between my laptop and my iPhone with Apple's Podcasts app and iTunes on the desktop.

[_ZeD_]

offtopic, but on the page there is a note with:

    There’s one elaborate exception that we discussed 
    in Under The Radar #98: workout apps, which are
    allowed to run in the background and play audio.
    So this all becomes possible if you combine a
    standalone podcast player with a workout app, and
    only allow podcast playback while a workout is
    active that was started from that app.
    But this forces the combination of two completely
    different app types, and users would find the
    workout-during-playback requirement confusing,
    inexplicable, and limiting.

    Requiring podcast apps to also be workout apps is a
    user- and developer-hostile hack that Apple
    probably doesn’t intend.

whaaat? what kind of OS has this business rules so embedded?

[izzard]

Somewhat off topic but somewhat related, I have tried a whole bunch of different smart watches and activity trackers, and my current favorite is made by Skagen.

Specifically, the "Signatur Connected Leather Hybrid Smartwatch". It looks like an analog watch, but it has smart watch functions and connects to your phone with bluetooth.

Favorite things about it: It has an analog subdial that shows progress towards your daily step goal. It has three 'real' analog buttons that you can connect to just about any function on your phone. I have one button mapped to start/stop any music that is playing. Another button moves the hour and minute hands to point to the date. The third button sets off the ringer on my phone.

And the battery is a normal watch battery, which should last between 6 months and a year. Check it out, I think it hits the right balance between minimal analog watch and smart functions.

[brlewis]

Why not just listen to the podcast only on the watch, since you always have it with you? What's the use case for switching to some other device once the podcast is on your watch?

[yoz-y]

When you have your phone with you it is still a better device for podcasts:

- You have access to show notes and have a full fledged browser to follow the links - You have way more battery life. I listen to about 4 hours of audio content during a day, I suppose I'd have to recharge the watch more often - Exploration of episodes and general library management is better on a bigger screen

[falcolas]

Using external speakers (or headphones), battery life, and disk storage are three I can think of off hand.

Some podcasts are exceptionally long (10's of hours - think the out-of-copyright version of audiobooks), and those consume a lot of battery life (for both playback and transfer) and disk space.

[ksec]

My guess is that Apple takes battery life over everything else. You can tell that Apple has kept a consistent Talk Time/ 4G usage time over the years with iPhone. And some of these consideration means Podcast on Apple watch a little harder to get right.

And I am wondering, how much would people paid for longer battery life on Apple watch? We do have the tech, solid state battery, it is simply too expensive if it is used in the size of smartphone, because solid state battery prices scale exponentially with size. But what about Smart watches?

Are user willing to paid extra $200 for LTE + Solid State Battery?

[detaro]

I thought these were still prototype-stage? Do you maybe have I link where I can learn more?

[drewg123]

Can somebody please, please, please make a podcast app for Android Wear? One that I can use without my phone, so I can go for a run/hike/walk with just my watch and headphones?

Even Google Play Music doesn't sync podcasts to wear. Sigh.

I periodically search the play store for AW enabled podcast apps, but the best I've found are apps that put playback controls for the phone on the watchface. Sigh.

[jjtheblunt]

Who is "we"?

[austenallred]

They’ve sold 32 million of them by some estimates, including 12 million in 2016. No iPhone, but we’re it any other company than Apple it would be an enormous, company-making win.

[whipoodle]

This thing still ain't fully baked.

[0xbear]

Do people still listen to podcasts? I lasted 3 months, and then moved to Audible.

[dreamcompiler]

I don't listen to them nearly as much as I used to, mostly because podcasts are so ad-laden these days. Listening to a two-minute ad for Ziprecruiter for every 7 minutes of content gets old fast.

[KGIII]

By 'brand name?' No. I still listen to people talk in pre-recorded episodic content, just not on an iPod, iPad, or iPhone. Sometimes they are videos, sometimes they are just voice. Usually, it is on a Linux device.