21–30 of 51 posts
Isn't this just a bookmark for http://play.spotify.com/ ?
https://apps.facebook.com/get-spotify/?fb_source=notificatio...
Once you do that, then play.spotify.com will work. I believe it's still in beta and some weird bugs showed up for me about a week ago, but it's still sufficient.
Note that it is still US only though, if you are based in a different country it will just forward you to the Spotify homepage. On a different note, does anybody know why they started with native clients instead of one web client? I can think of some advantages of native clients (P2P streaming as the have it, better OS integration etc.) but when compared to the big disadvantage of having to maintain two codebases (Wi…
It's about your users, not your developers. Of course it costs more to provide a better product, which was the original reasoning behind providing native desktop applications.
What they're doing now has more to do with politics and skillsets amongst traditionally web-focused engineering management and teams, than it does with actually creating a great product. Spotify has a ridiculously hard time hiring outside their management's core competency of web-focused development, including both for mobile and desktop. That has more to do with their management than the job market, though.
As an aside, I can't say I understand why web developers find it so impossible to migrate to mobile/desktop. Time and time again we work with organizations who have built a large server-side web-focused team and somehow simply cannot manage to support the mobile/desktop. What kinds of engineers are they hiring that they can't learn a new platform?
Note that it is still US only though, if you are based in a different country it will just forward you to the Spotify homepage. On a different note, does anybody know why they started with native clients instead of one web client? I can think of some advantages of native clients (P2P streaming as the have it, better OS integration etc.) but when compared to the big disadvantage of having to maintain two codebases (Wi…
The webplayer seems to take more memory in total and offer a still significantly worse UI than the desktop counterpart. I'm not impressed yet, and I know that better web experiences can be delivered. However, now that I see this webplayer and recognize a few similarities with the desktop player, I can see why many of the horrifically terrible changes to the native player happened recently. They were getting rid of na…
I can confirm this, and have heard that this was politically driven by their web-focused engineering management and teams.
Netflix did the same thing, for the same reasons. People built up web fiefdoms and had the political clout to put their job security ahead of user experience.
Good to see another groundbreaking Spotify "innovation." I remember Grooveshark getting into the chrome web store almost two years ago.
Note that it is still US only though, if you are based in a different country it will just forward you to the Spotify homepage. On a different note, does anybody know why they started with native clients instead of one web client? I can think of some advantages of native clients (P2P streaming as the have it, better OS integration etc.) but when compared to the big disadvantage of having to maintain two codebases (Wi…
They were leveraging p2p streaming to reduce their costs.
Note that it is still US only though, if you are based in a different country it will just forward you to the Spotify homepage. On a different note, does anybody know why they started with native clients instead of one web client? I can think of some advantages of native clients (P2P streaming as the have it, better OS integration etc.) but when compared to the big disadvantage of having to maintain two codebases (Wi…
> ... but when compared to the big disadvantage of having to maintain two codebases ... It's about your users, not your developers. Of course it costs more to provide a better product, which was the original reasoning behind providing native desktop applications. What they're doing now has more to do with politics and skillsets amongst traditionally web-focused engineering management and teams, than it does with actu…
Speaking as a web developer, I can tell you that I am perfectly able to transition to making desktop apps, I just have no incentive to. There are fewer and fewer desktop apps out there, so it's not a great use of my time to learn those skills.
Back to the Spotify player, the web client makes far more sense than a desktop one to me. All the music is stored in the cloud, so why do I have to download a desktop client on every machine I use to access it? It seems horribly backward to me.
Note that it is still US only though, if you are based in a different country it will just forward you to the Spotify homepage. On a different note, does anybody know why they started with native clients instead of one web client? I can think of some advantages of native clients (P2P streaming as the have it, better OS integration etc.) but when compared to the big disadvantage of having to maintain two codebases (Wi…
Earlier quoted context omitted.
> ... but when compared to the big disadvantage of having to maintain two codebases ... It's about your users, not your developers. Of course it costs more to provide a better product, which was the original reasoning behind providing native desktop applications. What they're doing now has more to do with politics and skillsets amongst traditionally web-focused engineering management and teams, than it does with actu…
What kinds of engineers are they hiring that they can't learn a new platform? Speaking as a web developer, I can tell you that I am perfectly able to transition to making desktop apps, I just have no incentive to. There are fewer and fewer desktop apps out there, so it's not a great use of my time to learn those skills. Back to the Spotify player, the web client makes far more sense than a desktop one to me. All the…
Funny that you speak of it as a dead market, when A) The skill cross-over between desktop and mobile is direct, B) There's a huge amount of unfulfilled demand for mobile developers, and C) There's an enormously underserved desktop market (see also: Spotify, Netflix, HBO Go).
> Back to the Spotify player, the web client makes far more sense than a desktop one to me. All the music is stored in the cloud, so why do I have to download a desktop client on every machine I use to access it? It seems horribly backward to me.
Running a full fledged browser, with the resulting poor application UX, for a lightweight task as music streaming, seems horribly backwards to me.
All I want when music is streaming is a miniplayer, not a web browser. It should work with the play/pause/skip buttons on my keyboard/headphones, support airplay streaming, be able to integrate with my music library, and otherwise fit in nicely to my desktop/mobile experience.
If I worked for Spotify, Hulu, Netflix, or HBO (Go) (which I wouldn't, because they're myopically web-focused), I'd be beating the war drums to provide better, more engaging user experiences via native applications for not just mobile, but desktop too.
Unfortunately, it winds up being a catch 22. They build technological monocultures (web-focused), can't hire for alternative platforms, contract out the mobile development, and then the web developers use their political positioning to try to turn everything into a bad shell around a web rendering view. The users lose.
Earlier quoted context omitted.
What kinds of engineers are they hiring that they can't learn a new platform? Speaking as a web developer, I can tell you that I am perfectly able to transition to making desktop apps, I just have no incentive to. There are fewer and fewer desktop apps out there, so it's not a great use of my time to learn those skills. Back to the Spotify player, the web client makes far more sense than a desktop one to me. All the…
> Speaking as a web developer, I can tell you that I am perfectly able to transition to making desktop apps, I just have no incentive to. There are fewer and fewer desktop apps out there, so it's not a great use of my time to learn those skills. Funny that you speak of it as a dead market, when A) The skill cross-over between desktop and mobile is direct, B) There's a huge amount of unfulfilled demand for mobile deve…
Running a full fledged browser, with the resulting poor application UX, for a lightweight task as music streaming, seems horribly backwards to me.
But that isn't why I'm running it. I have a web browser open every minute I'm using my computer, so it's already there. The browser is a multitasking application itself, so using it for music streaming fits in great. I haven't used the Spotify web player, but Rdio has been web-based from the start, and has been great.
Earlier quoted context omitted.
> Speaking as a web developer, I can tell you that I am perfectly able to transition to making desktop apps, I just have no incentive to. There are fewer and fewer desktop apps out there, so it's not a great use of my time to learn those skills. Funny that you speak of it as a dead market, when A) The skill cross-over between desktop and mobile is direct, B) There's a huge amount of unfulfilled demand for mobile deve…
Perhaps a better way to look at it is this- when I have a great job doing web development and see job listings all over the place for other rewarding web roles, where is my incentive to do desktop development- even if it's close to the (much more booming) mobile app space? The web is in no danger of dying or getting less popular any time too soon. Running a full fledged browser, with the resulting poor application UX…
Because it would provide a better product for your users, which is the whole point.
It also shouldn't be hard to do. A senior engineer that can't easily jump on new technology stacks is not a senior engineer.
> But that isn't why I'm running it. I have a web browser open every minute I'm using my computer, so it's already there. The browser is a multitasking application itself, so using it for music streaming fits in great. I haven't used the Spotify web player, but Rdio has been web-based from the start, and has been great.
An arbitrarily resizable browser window/tab that looks like every other browser window on my desktop, which can't share state between multiple windows, and can't interact with my desktop in any meaningful way, doesn't use native components, goes wonky if I reload, and goes away if I have to restart my browser.
That doesn't make sense. This makes sense: http://www.pandabarapp.com/