{"id":38774,"date":"2023-03-15T14:32:33","date_gmt":"2023-03-15T18:32:33","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=38774"},"modified":"2023-03-15T14:32:33","modified_gmt":"2023-03-15T18:32:33","slug":"why-a-separate-app-for-classical-music","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2023\/03\/15\/why-a-separate-app-for-classical-music\/","title":{"rendered":"Why a Separate App for Classical Music"},"content":{"rendered":"

Jessie Char<\/a> (via Nick Heer<\/a>):<\/p>\n

\n

Now here’s The Nutcracker. The composer is in the album title, the performer and conductor are listed as the artists, each track has a byline for the conductor, and while all 17 tracks are unique you can’t see the bit that sets them apart. And the play preview displays even less.<\/p>\n

In fact when you tap to full screen the song it still doesn’t display the full title, you have to wait a few seconds for it to start scrolling.<\/p>\n<\/blockquote>\n

And it doesn’t show it at all in CarPlay. Will that get Apple Music Classical, too?<\/p>\n\n

\n

The year refers to the year this particular version was was recorded, not the year the piece was composed. Year of composition AND year of recording are both important.<\/p>\n

The “artist” tag is also really tricky, and often this’ll be tagged with composer, ensemble, soloist (if relevant), and conductor. It’s a lot of names, and these often get clipped or some just don’t get added to the mix.<\/p>\n

[…]<\/p>\n

Take Apple News vs iBooks- they’re both reading apps, so why is it necessary to have two separate apps? Because they’re extremely different reading and writing experiences and it doesn’t make sense to lump them into a one-size-fits-all approach.<\/p><\/blockquote>\n\n\n

Previously:<\/p>\n