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