Took a look at the code. It's built with Backbone.js!
Yup! The previous version used JMVC but it was a poor fit. Backbone does juuuust enough to help you out then gets out of your way. Means you have to write a lot of your own architecture but that's pretty much my favorite thing to do ever (and I hated JMVC) so I gladly did so. The site is way faster now, despite having more stuff going on, just because half the codebase is no longer trying to hack around the parts of…
The New Grooveshark
31–40 of 92 posts
Re: The New Grooveshark
#32Too bad they can't get their iOS app through the apple approval process. It would be a serious contender to Spotify.
I am pretty sure that they can't get the approval from Apple because they cannot prove that they have the rights to publish the content.
Re: The New Grooveshark
#33I went to grooveshark.com and looked at the page for a few seconds. When I went to close the tab, a JavaScript popup asked me if I was sure that I wanted to "navigate away". Why, oh why does Grooveshark think that was useful, necessary, or a good way to treat a user?
I haven't had any complaints about it and personally find it useful. Especially as it lets me quickly "close all right tabs" without stopping to think if I'm about to break what I'm listening to. However, these are podcasts and maybe people are less fussed about a random song stopping halfway through.
Re: The New Grooveshark
#34I've never used this site before, so I can't comment on how it used to work. This interface is not at all intuitive though. - click a play button on a song - music starts playing - click a different play button - nothing happens - click pause - music stops - click a different play button - nothing happens - click play - first song continues playing Steps to get a second song to actually play after you've got a first…
Edit*
I see what is happening. There are a couple of paths users can take based on if they click or drag items, and I just so happened to take the smoothest one.
Re: The New Grooveshark
#35Re: The New Grooveshark
#36I've never used this site before, so I can't comment on how it used to work. This interface is not at all intuitive though. - click a play button on a song - music starts playing - click a different play button - nothing happens - click pause - music stops - click a different play button - nothing happens - click play - first song continues playing Steps to get a second song to actually play after you've got a first…
http://cl.ly/image/390409163d2D Song playing is in orange, you can see the play button on the second song when you hover it.
Did the queue not open up for you after hitting play on the first song? Normally it should, unless you've manually closed the queue previously, but if this was your first visit that shouldn't be the case. When the queue is open, it should be pretty visually apparent what clicking the play button did. Also, most places that will add instead of play immediately should have an icon change (play+) http://cl.ly/image/1R3n1I1S0y0i
There may be a few places that either are not updating their icon or should be playing immediately but have the wrong classname and are getting caught in the 'play next' process. Bugs happen, I'll make sure it's on the list of things to check.
Re: The New Grooveshark
#37Earlier quoted context omitted.
Yup! The previous version used JMVC but it was a poor fit. Backbone does juuuust enough to help you out then gets out of your way. Means you have to write a lot of your own architecture but that's pretty much my favorite thing to do ever (and I hated JMVC) so I gladly did so. The site is way faster now, despite having more stuff going on, just because half the codebase is no longer trying to hack around the parts of…
Did you ever look into using something like LayoutManager or Marionette?
Re: The New Grooveshark
#38Too bad they can't get their iOS app through the apple approval process. It would be a serious contender to Spotify.
Weren't they also yanked from the Google Play store?
Re: The New Grooveshark
#39And still not available in Germany anymore thanks to GEMA. I use Spotify now.
Re: The New Grooveshark
#40One gotcha, however. Selecting a video to play while a song is already playing produces a broken UX for me - the video appeared in a modal box, but was truncated by the queue and play bars at the bottom of the screen. There was no obvious way to view the whole video since the controls at the bottom were hidden.