Yes, I was thinking specifically of client-side caching. I would like my mobile apps to aggressively cache forward in the play list so that I always have<p>a) the complete current song, and ideally
b) the complete next song<p>Except in game over insufficient bandwidth full stop scenarios, natch.<p>I would imagine the most user-friendly version of this would be to start playback using as soon as there is a conventional &quot;sufficient buffer,&quot; but to be much more aggressive about sucking every possible byte to maintain the above caching...<p>Personally I would solve the &#x27;very long delay before play&#x27; problem by defaulting to the 80% case of playing one of N songs from the last used playlist&#x2F;station, _as cached locally from last play_. (Maybe not simply the most recently played, maybe the highest ranked, least skipped, whatever...)<p>That wouldn&#x27;t help with people who are flipping stations, but my road trip case would be sudden bliss... no more constant drop-outs.<p>Disclosure: part of my problem is no doubt sticking with Sprint because I don&#x27;t want to lose unlimited (sic) data. :P