Would be nice if paying users could access actual streams, although that would probably violate the drm or something.
"Audio stream" to burn to a CD or a tape cassette? Yeah, that's not gonna be supported.
I wonder if you could spoof the system time provided to Spotify too and have it "play" the music faster than real time.
Their current SDKs are only for iOS and android. They do also have a Web player but the DRM for that requires playback through a Web browser i.e. You cannot write a simple CLI app that plays Spotify music.
I'm going to see if there's a Github link or maybe reverse engineer the API and make it into a desktop app (mainly for Media key controls and Desktop integration to be honest).
not op btw
With the API integration it seems pretty straight-forward to make one, so there's got to be a strategic reason they don't want to?
Maybe they want to encourage people to use native apps wherever possible, since they have more advantage over Chromebooks there?
In the broader context and rough terms, it's against Apple's interests that web apps in general take off over native apps. In theory, there's no reason web apps shouldn't be as capable as native apps for 90% of workflows (playing music being well in that 90%).
If web apps, at large, take off:
1. The App Store loses relevance, and so Apple loses influence over developers, distribution, and 30% piece of the cake.
2. Apple loses platform lock-in, since web apps run everywhere. It'd be a no-brainer for companies to have one team developing for the web, instead of one for the web and one or two for mobile.
I don't doubt if Apple wanted they could form a team with enough expertise to build solid web apps and make their services gain marketshare, but the experience would either have to be subpar vs native (like iCloud.com is IMO) or solid enough that they would unwittingly prove web apps are equally capable to native apps, and so create demand for more web apps, more progress in that space, and stray away from an advantageous position for them.
1. Primary reason: it is a job someone needs to do, and it isn’t high on the priority list at all due to many possible factors.
2. Secondary reason: as a side effect of (1), it encourages the use of their native apps, which they might want for whatever reasons as well.
Now I'm thinking about turning it into a desktop app coz its a pain to keep a tab open for playing music.
I was too late for rdio, but from what I hear it sounds like the music service I really want :/
That was one of my main reasons for switching to Rdio when it was out, and while I really liked Rdio for its UI, it definitely had enough bugs/delays in song starting that I ended up moving (reluctantly) back to Spotify until Apple Music was released. Now, with that handled along with cloud uploads of my local media (I buy a lot off of bandcamp), it feels like a much more whole offering. I wish social and discovery features were up to Spotify's levels, but I personally have moved away from those for various reasons anyway, so it's not as much of an issue for me as it is for users who really utilize those features.
> it just lists all of the songs that I have saved from an artist, ignoring the album information
AM definitely has Spotify beat here. Click an artist, see their albums, choose an album to listen to. All in one view. It seems so natural ... I wonder if this is because I learned to curate my music on iTunes, and it is just a habit?
But for music discovery, open development practices (this is the biggest reason I switched from AM to Spotify - knowing that no matter what kind of thing I want to hack together, Raspberry Pi connected to BT speaker connected to projector, I would be able connect Spotify to it somehow), and social music experience, I think Spotify has AM beat.
Maybe I am missing something, but it seems like the flow you describe is exactly how it works in Spotify. Here is an artist page with the album list prominently featured: https://i.imgur.com/wNAjoCa.png
For example, in Spotify they just list all the tracks
In Apple Music, they list the albums, year, artwork, etc.
I definitely prefer Apple's for browsing my current music.
I have a few projects too that involve the hybrid of the REST API and the libraries, it is definitely not ideal (should all be through REST API IMO). I guess Spotify could do it all over the REST API (including playback, Spotify connect, etc.), and then the client would only need to pull in a library that handles content decryption because the API can't send back decrypted audio streams (copyright/pirating). DRM is likely the biggest reason why they haven't done this yet (thoughts?), but the previous solution sounds plausible.
https://github.com/librespot-org/librespot has been a very good replacement for libspotify, and is pretty actively developed. Spotify can of course break this at any minute but it seems unlikely that this would happen.
I stopped developing it because soundcloud's UI started to really match my design and feature set.
- my search is faster (just a long startup time)
- it will actually shuffle all your songs and not just the last 20-ish
Edit: Changed link.
PS: For those of you who use Apple music and are into Indie / Alternative music, here's a 2018 mixtape I made recently.
Edit: Added playlist
Edit: Musish github repo: https://github.com/Musish/Musish
How did one person make a client that is 100x faster and more stable than Apple's?
1. It’s not 100x (or even 2x) faster or significantly more stable than Apple Music
2. It’s always easier to make a nice app when starting from scratch versus trying to fix existing older software to be nice
3. Apple did a good job with their APIs