Haha, I’m always happy to talk git! Thanks for your post.
I can definitely understand that concern, especially given press articles of late
But as I’ve pointed out elsewhere, we are clearly investing heavily in local media (two big recent examples are the new video player on iOS/tvOS and the cross-platform music player) and will continue to do so. It’s the core of our product, and has been from the start. We’ve also dabbled in online content from the start (first with plugins, and now with our cloud-hosted architecture). So to me it’s more of an evolution.
Taking TIDAL as an example, as I mentioned above, I see this as being an amazing marriage of local + online content. I literally use it every day to discover new music, and I would argue that it’s an elegant way to expand one’s musical universe:
- It tells me when new albums are released by artists in my library
- It recommends artists related to artists in my library which I don’t have
- It shows me albums I’m missing by artists in my library
- It will “augment” artist radio by pulling in some TIDAL content
- It offers a Discovery radio with artists I might like but which don’t exist in my library
- It gives you music videos for artists in your library.
So I can understand why you might not like TIDAL, or want to subscribe, or want it near your music collection, I respect that. But if you are the kind of person (like myself) who maintained a Spotify sub just to find new music, or were constantly trying to expand your own library, it’s a godsend. Not only am one of the developers, I’m also a heavy user! [obscure reference to some men’s baldness thing]
And again: it’s purely optional! If you don’t want it, don’t subscribe.
One of our main focuses for the year is stability. We have a lot of apps, doing a lot of things, and we absolutely want to make things work better.
You, sir, have a glass which is clearly half empty. The benefit of the cloud architecture for online media that we’ve built is that there is very little cloud work to integrate new sources of content, and clients basically get it all for free (because it’s the same API).
Seriously, stop reading so much into that article. The reporter saw the current UI, which is type-focused. We didn’t have edits on what was published. There’s no conspiracy here.
Yep, that’s pretty much the most accurate thing I’ve read about where our thoughts are.
Yes, jump all over me. I will happily make a public Hangout where you can just yell at me live. Want to do it sooner? Happy to spend the time.
We allow disabling all online sources, and we’ll do that for any new ones. I’m not entirely sure what you mean about “on our servers” as the account setting for it is in the cloud and “global”.
Online content, such as TIDAL, is “linked” from server, the traffic doesn’t flow through the server as that would be a bad experience for streaming video from cloud to server and then out again, e.g. Even when you make a universal playlist which incorporates content from shared servers and online content, the content which is “foreign” is linked, not proxied. Make sense?
That’s a harder one. We’re working through the design elements now, and working on a mock PoC for some initial testing (it’s hard to know how something will work just from pure static design). (Yes, there will be more details forthcoming here in the forums!) Then we need to fan out and implement in multiple clients. Figure it will take one to two “cycles” (we operate internally on 6-week cycles), so you can form a rough idea of how long it might take…but blah blah yadda subject to change.
The changes are clearly more of a top-level reorganization, so that makes it easier than a “rewrite”, clearly…
Thanks for writing 