3 ms·
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, Meil
by 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 agoSure. 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?