Thanks but this app is an always running process that monitors for launching apps and then force kills it if it is itunes or apple music. I could do the same thing with a simple bash script.
So basically it is a hack/automation of me manually closing apple music every time. It isn't a real fix to the underlying user experience bug. I shouldn't have to resort to hacks to work around a bug that has been present since at least Big Sur if not earlier.
There are two issues UX here, the autolaunching of some music player and the selection of music player of choice if autolaunching is the preferred behaviour. There is also a potential bug which is whether or not it is intended/expected behaviour that a music player should launch when a bluetooth headset connects. In this case the bluetooth headset was already connected to macOS the difference is the device becoming available again for other apps at the end of a conference call. So this to me feels closer to a bug than just a bad UX choice (or lack of choice).
macOS/osx used to have to have a setting that was something along the lines of "should I auto-launch movie/quicktime when DVD is inserted". You could easily say...no thanks...just because I insert a DVD doesn't mean I want to play it.
Maybe this only affects a small number of mac users or nobody at apple uses the very uncommon Bose QC__ bluetooth headsets for conference calls.
