Grooveshark launches HTML5 web app, you just need a better browser to use it | webOS Nation
 
 

Grooveshark launches HTML5 web app, you just need a better browser to use it 14

by Derek Kessler Thu, 06 Sep 2012 11:55 pm EDT

Grooveshark launches HTML5 web app, you just need a better browser to use it

If you've been a webOS user for a while, you might remember the big to-do it was when Grooveshark came to our nascent platform back in early 2010. They had a nice little app that streamed their subscription service music easily and cleanly, something we came to appreciate. In recent months, however, the Grooveshark app for webOS stopped being able to load anything from their service, despite having been updated to take advantage of larger screens like that on the TouchPad.

Alas, the webOS Grooveshark app had fallen by the wayside as so many other webOS apps from groups with bigger iOS and Android fish to fry. So what's a webOS user to do? Go to the internet, dear reader. Grooveshark this week launched a new web-based HTML5 player for their service that promises to provide the full Grooveshark experience without wasting your time with an app. That's right, Grooveshark 100% in your browser. They've whipped up both mobile and tablet interfaces that show up when you point your browser to html5.grooveshark.com

If you send your TouchPad or webOS smartphone's browser to that URL, the HTML5 version of Grooveshark does in fact load, and in spite of a few formatting errors on the smartphone side, everything from searching to browsing to adding songs to your play queue seems to work as intended. At least, that's until you try to actually play something, that is. Turns out it's webOS that's at fault here, as everything up to webOS 3.0.5 is running an out-of-date version of WebKit lacking support for handy things like HTML5 audio. Thus web-based apps like the new Grooveshark, which should be proving to be our salvation in a post-abandonware world, are instead proving the other aspect of webOS abandonware: we're just plain out of date.

If it's any consolation, testing we've seen with the Isis browser and Open webOS's QtWebKit core seem to bear out that the new open source version of webOS hits many more marks on the HTML5 checklist, presumably including those audio bits needed for HTML5 Grooveshark to work as intended. At least HTML5 Pandora works.
 

Source: Grooveshark

Category:

14 Comments

I hope with Open webOS and/or woce they get around to improving the browser. It needs so many new features added and more standards base support.

I must disagree with the main premise here -- as someone who has authored a complete html5 music player for webOS, webOS versions back to 1.4.5 are perfectly capable of supporting real html5 audio. This likely means that grooveshark is doing something incorrectly, or relying on something that is not necessary for the implementation.

It stands to reason that if Pandora can do HTML5 audio, then Grooveshark should be able to as well.

I also find it odd that anyone can claim Grooveshark is doing it wrong when clearly it works and satisfies their business needs for every other platform out there just fine that can handle what most of these newer HTML5 applications springing up happen to demand. In order to satisfy evermore complex business requirements, licensing terms with the labels, and to forge and adopt newer best practices going forward, sacrifices have to be made, and that includes leaving behind browsers that simply can't keep up as the rest of the mobile and desktop space keeps evolving with changing standards from HTML5 itself to ECMA and more advanced CSS3 than the version of Webkit webOS uses can handle.
 
I don't know, perhaps asking Grooveshark directly a bit more about the "Why?" rather than immediately proclaiming they don't know what they're doing--without a shred of evidence to back it up--is likely the correct answer here? Just a thought.

You are accusing Eric of "immediately proclaiming" that Grooveshark doesn't know what they are doing, when he simply commented that he has experience writing an app that uses html5 audio on webOS and that Grooveshark was probably doing something non-standard. You are the one jumping down his throat claiming that he doesn't know what he is talking about, thinking that throwing out buzzwords will make you sound smart.

Another thing to note is that when this HTML5 client was in beta, it was working for playing songs on webOS devices until about 2 weeks ago. So, obviously something was changed.

I never said they don't know what they are doing - I was disagreeing with the article's premise that webOS does not support HTML5 audio. While it does not support all the features of the full spec, it does support enough to get playback working.

XO works using HTML audio, the built in music app works using HTML audio, Pandora works using HTML audio, and the vast majority, if not all of, the music apps in webOS use HTML audio.

If it doesn't work, then they are relying on something -else- that isn't supported, or they are doing something incorrectly, -or- they have made it somehow dependent upon a feature of the current HTML5 audio standard that is not present in webOS. (or maybe they just have a whitelist of things that it works on, and if you're not on that list, you don't get it)

I must disagree with the main premise here -- as someone who has authored a complete html5 music player for webOS, webOS versions back to 1.4.5 are perfectly capable of supporting real html5 audio. This likely means that grooveshark is doing something incorrectly, or relying on something that is not necessary for the implementation.

Is it a specific feature of HTML5 audio that webOS is lacking? Because the Grooveshark app used HTML5 audio for streaming music.

It works on iPad and Android. webOS is doing something wrong.

The Grooveshark desktop site still works great on my touchpad.

whenever i remove the Tweak app, i could hear the music play in html.grooveshark.com. Not sure why but " release to load more songs" is not working....

Although it was great to have a grooveshark app (even when it was pulled from Android and Apple markets), it was never "clean and easy" as you've described. I found it to be rather frustrating and non-intuitive. I agree with eBlade - there is something else going on because numerous other "HTML5" music sites work just fine, including Rhapsody.

Ironically , webOS is based on HTML5 technologies

Thanks for posting about this. Grooveshark is a big deal for me and I appreciate it when related news is reported...which is not often, IMO.

Sad to see that, if I need need to reactivate my Pre, I'll have no Grooveshark options. This makes me glad I have been moving to iOS more and more,

Damned sad, as an old-school Palm fan.