There's runcasts now, but another important thing missing is on device variable speed playback.
Unfortunately the devices don't currently have speed control APIs available on-device. To implement variable speed playback Runcasts has to perform a transformation on the server and send the modified MP3 down to the watch.
Yeah thats too bad rconradharris. Perhaps too much processing power or maybe lower priority feature?
Could be both but if I had to guess it's probably more the lower priority feature aspect.
To implement it, though, they'd first have to solve some latent issues in their media decoding pipeline, especially around time-skew during playback. One of the reasons Runcasts can't implement podcast chapter support is because the timestamps given out by the media player APIs don't reflect where the MP3 actually is in playback. And the error compounds over time so for a long podcast the discrepancy could be 30min or more.
Thanks for the insight. Playback position isn't a trivial problem since files can be CBR or VBR, sample rates, etc. The variable speed would just complicate that.