[jlgtx]

@Learux, haha.  Maybe.  It's still early days but I'm seriously impressed with how responsive @Zubersoft is....the COMPLETE and utter opposite of the forScore dev who simply ignores every communication.  Hopefully I'll be done with forScore if I can manage to migrate over 15 years of work to MobileSheets instead.

We've been using MS on Android since 2015, with multiple "common use" tablets for our church music program. I can get 11.6" RCA Android tablets for <$100, which makes it all feasible. Personally, I was using either forScore (since 2014) or OnSong (2019) on my iPad, and I made multiple approaches over the years to their devs, and others, to see if they would work with Mike to create bi-directional setlist compatibility, to make my weekly planning easier (I'm just selfish like that). Back in 2016, I actually told the OnSong guys that they should approach Mike about turning MobileSheets into "OnSong for Android." Nobody listened, nobody cared. So I was overjoyed when Mike released MS for iPad, and I've been encouraging everyone I know to make the switch. Now he's adding the ability to import forScore setlists, which is just beautiful. MS is the Swiss army knife of sheet music apps, and absolutely deserves to be the king of that hill.

To the current question...one of the advantages of the way MS handles files (e.g. audio files get copied into the MS file structure just like PDFs and ChordPro files) is full cross-platform compatibility between Android, iPadOS, macOS, and Windows. Adding "Apple-specific" features like being able to add links from a score in MS to songs in Apple Music might sound like an attractive idea, but what happens when you export that score to MS on Android? If that breaks the audio link, then the cross-platform advantage is lost. I would argue against adding a feature like this. Mike is just one guy, and he keeps costs down for his customers -- which is something else that sets MS apart from its competitors -- so IMHO it behooves us to think in terms of maximizing the impact of his programming time.