+1! Thank you for the thought out response! Seriously - your company should share it more broadly. You have a rare perspective on HTML5's audio story. Most folks have only focused on video.
I'm curious where 3rd party services come in in slightly more detail - I'd always assumed what I saw on grooveshark was a 100% client-server app. I'm assuming they're something like pulling from an album art service or a similarly ornamental interface that wasn't even worth carrying over to the mobile experience.
What's "flaky" mean? Do you mean that using it sometimes resulted in failure to deliver audio to a user with a compatible user-agent? If so, that sucks. Which browsers, any ideas what's wrong with it? If not - could you clarify?
I may strongly disagree with Grooveshark as a company, but that doesn't mean you aren't one of the only legitimate players with experience in delivering audio on the web. I am curious to hear more.
I'm curious where 3rd party services come in in slightly more detail - I'd always assumed what I saw on grooveshark was a 100% client-server app. I'm assuming they're something like pulling from an album art service or a similarly ornamental interface that wasn't even worth carrying over to the mobile experience.
What's "flaky" mean? Do you mean that using it sometimes resulted in failure to deliver audio to a user with a compatible user-agent? If so, that sucks. Which browsers, any ideas what's wrong with it? If not - could you clarify?
I may strongly disagree with Grooveshark as a company, but that doesn't mean you aren't one of the only legitimate players with experience in delivering audio on the web. I am curious to hear more.