[FEATURE] Apple Music / iTunes as Metadata Source

[HVR88]

Feature Request

Just a quick note to vote for adding Apple Music as a metadata source in a similar fashion as is supported by Deezer and Discogs.

There are two way (tiers) of basic access.

1. Free via iTunes API and endpoints (20 queries per minute max I believe)
2. $99 Developer account Music API and endpoints - requires developer auth token

Additionally there are bulk data and enterprise options which I didn't investigate in detail.

In my experience, and at least for my musical tastes and collection, Apple Music seems more robust than Deezer or even Tidal for artist selection and release availability.

I'd be fine with this implementation even if it required the user to enter their own developer ID/tokens if it wasn't going to be baked into the code. My reg. may be lapsed right now, but I normally have an active developer account and keys/tokens..

Priority Level

Would improve my experience (medium priority)

Visual Designs or Mockups

No response

Are you willing to contribute to this feature?

I might contribute, but I'd need guidance

Technical Details (Optional)

No response

Prerequisites

• I have searched existing issues to ensure this is not a duplicate

[TypNull]

I'll consider adding Apple Music as a metadata source, though I have some reservations. I'm not personally familiar with the Apple ecosystem and unsure about the requirements, like whether an Apple account, device, or other dependencies are needed beyond API credentials.

The $99/year developer account cost also seems like a barrier that most users wouldn't want to pay for this feature, and I'm uncertain whether the benefit justifies the implementation effort at this time.

For now, I won't prioritize this feature in the coming quarter, but I'm definitely open to PR's if someone wants to tackle the implementation. If you or another would like to work on this, I'm happy to provide guidance and review the code.

[HVR88]

The iTunes API requires "none of the above" but carries the 20 query limit I mentioned.

The Music API, would normally require the developer to be registered, so a once-per-year $99 registration fee (for you). If I decide to register as a developer again going forward, which I'll figure out in the next month or so, you're welcome to publish under my ID and credentials. I haven't looked into the practise of signing open-source code, as everything I've previously signed and released has been pre-compiled MacOS binary.

[TypNull]

That's very nice of you. However, I would need to make sure this also complies with their terms of service. Additionally, you would have to trust me with the safety of your app credentials.

I will consider it regardless of whether you provide the ID or not. But I mostly thought right now it's good enough as a foundation for others plugins to build on top of as I don't necessarily have to provide all service myself. But as you said the data is quite good quality, I consider it.