5 ms·

I think (based on zero insider knowledge) that's a UI decision. Cluttering up an app most people use to search for Ed Sheeran or w/e with data attributes like

I think (based on zero insider knowledge) that's a UI decision. Cluttering up an app most people use to search for Ed Sheeran or w/e with data attributes like 'conductor', 'orchestra', 'composer', etc. — all of which are meaningless to 'most people' — makes the app less usable for most people (including myself, when I'm not listening to classical). The 0.5% of people who actually want these features can just download this app.

whywhywhywhy 4y ago
Still doesn’t seem like something that needs to exist. They literally could just have a classical section with these features in the base Music.app. Calling it now this app will be quietly discontinued by 2025. Doesn’t justify the engineering overhead for a different meta data grouping/filtering. None of this sounds anywhere near as complicated as people are making it out to be.
- Veen 4y ago
  > None of this sounds anywhere near as complicated as people are making it out to be If that's true, why does every mainstream music app do such a terrible job with classical musical?
  - whywhywhywhy 4y ago
    That doesn’t mean it needs to be an entirely separate executable. You can just have a different filter view and search control.
    - Veen 4y ago
      It's a rebranded version of an app Apple acquired. Presumably they thought that was a more elegant solution than shoehorning classical into an interface designed for pop music.
- throwanem 4y ago
  It's not just metadata. Search is very different as well, because you're looking for different things in different ways. Display is different too, for the same reason. So is the entire concept of what constitutes a work, which breaks shuffle, just for a start. I've been growing and maintaining a collection of classical music for ten years now, which means I've been trying for ten years to solve this problem with tools designed for the same use case as Apple Music. If it were as easy as you claim, then by now I would have solved it at least well enough that taking a physical CD off a physical rack and putting it in a physical player never felt like the more convenient option. If the app's discontinued in a couple of years, it won't be because it never made sense to build, especially given that I'm sure they're reusing most of both the frontend and backend for Apple Music as it exists today. It'll be because they're addressing one of the world's pickiest audiences, and not succeeding in getting enough right enough of the time - on that score I wish them the best of luck; on every other, I don't think I need to, not least because they might well succeed in selling me an Apple Music subscription with this.
  - goolz 4y ago
    Sure but could you not just write a different search controller to handle the needs of a more specific search? I have written many search controllers with, Meilisearch for example, that could handle myriad constraints and parameters. What makes this so hard that you need to abstract it out to a completely new app? I am just struggling to find a need to have a separate app, I guess UI/UX perhaps but I still echo the same fear as the parent commenter. I am sure Apple has the money to support it, and while I love classical music, I am not downloading another app just to consume it.
    - throwanem 4y ago
      Sure. A different search controller, which needs a different query view to handle the different fields it filters on, which needs a different result view to surface the different parts of metadata that only apply to this use case...you end up adding significant feature work to the app so that it can use the new search logic you "just" added to the backend, and you have still only solved one narrow aspect of this surprisingly different use case. As I said before, I've spent a decade trying to solve this problem with the same kinds of approaches you're advocating here - that is, using tooling built for general music. That I haven't succeeded doesn't necessarily mean much, but how likely do you think it is that Apple's product and engineering teams didn't try the same before deciding they needed to ship a whole new app about it?
- pwinnski 4y ago
  Going out on a limb here, but I think you probably don't spend a lot of time listening to classical music. The reaction of nearly everyone who does is cautious optimism, because we know this is a very hard problem that companies and products consistently get wrong. Possible because they think something like "none of this sounds anywhere near as complicated as people are making it out to be."

whywhywhywhy 4y ago

Still doesn’t seem like something that needs to exist. They literally could just have a classical section with these features in the base Music.app. Calling it now this app will be quietly discontinued by 2025. Doesn’t justify the engineering overhead for a different meta data grouping/filtering. None of this sounds anywhere near as complicated as people are making it out to be.

Veen 4y ago
> None of this sounds anywhere near as complicated as people are making it out to be If that's true, why does every mainstream music app do such a terrible job with classical musical?
- whywhywhywhy 4y ago
  That doesn’t mean it needs to be an entirely separate executable. You can just have a different filter view and search control.
  - Veen 4y ago
    It's a rebranded version of an app Apple acquired. Presumably they thought that was a more elegant solution than shoehorning classical into an interface designed for pop music.
throwanem 4y ago
It's not just metadata. Search is very different as well, because you're looking for different things in different ways. Display is different too, for the same reason. So is the entire concept of what constitutes a work, which breaks shuffle, just for a start. I've been growing and maintaining a collection of classical music for ten years now, which means I've been trying for ten years to solve this problem with tools designed for the same use case as Apple Music. If it were as easy as you claim, then by now I would have solved it at least well enough that taking a physical CD off a physical rack and putting it in a physical player never felt like the more convenient option. If the app's discontinued in a couple of years, it won't be because it never made sense to build, especially given that I'm sure they're reusing most of both the frontend and backend for Apple Music as it exists today. It'll be because they're addressing one of the world's pickiest audiences, and not succeeding in getting enough right enough of the time - on that score I wish them the best of luck; on every other, I don't think I need to, not least because they might well succeed in selling me an Apple Music subscription with this.
- goolz 4y ago
  Sure but could you not just write a different search controller to handle the needs of a more specific search? I have written many search controllers with, Meilisearch for example, that could handle myriad constraints and parameters. What makes this so hard that you need to abstract it out to a completely new app? I am just struggling to find a need to have a separate app, I guess UI/UX perhaps but I still echo the same fear as the parent commenter. I am sure Apple has the money to support it, and while I love classical music, I am not downloading another app just to consume it.
  - throwanem 4y ago
    Sure. A different search controller, which needs a different query view to handle the different fields it filters on, which needs a different result view to surface the different parts of metadata that only apply to this use case...you end up adding significant feature work to the app so that it can use the new search logic you "just" added to the backend, and you have still only solved one narrow aspect of this surprisingly different use case. As I said before, I've spent a decade trying to solve this problem with the same kinds of approaches you're advocating here - that is, using tooling built for general music. That I haven't succeeded doesn't necessarily mean much, but how likely do you think it is that Apple's product and engineering teams didn't try the same before deciding they needed to ship a whole new app about it?
pwinnski 4y ago
Going out on a limb here, but I think you probably don't spend a lot of time listening to classical music. The reaction of nearly everyone who does is cautious optimism, because we know this is a very hard problem that companies and products consistently get wrong. Possible because they think something like "none of this sounds anywhere near as complicated as people are making it out to be."