Audio Unit container app usefulness
I'm looking for some input from users of AU's on iOS about the usefulness of the containing app for the AU's.
I've released a couple of AU's for iOS through the app store and when I started developing them, I decided that I didn't want to do the thing of making it so the containing app for the AU presented the AU as an application that was available through the mic, or IAA or Audiobus. My reasoning was that these are really best used as AU's and that having them available through IAA or Audiobus would more-or-less degrade the namespace for those features in hosts. Basically, I thought it would be confusing for the names of the AU's to show up three different ways when only one of them is actually useful.
So, I decided to make the containing app the manual for the AU. To be honest, I was kinda surprised when this worked and the AU's were accepted on the App store. Well, there is a significant bug in the UI code for my LRC5 AU, and when I released what I hope is a fix the app was rejected because it doesn't provide any functionality. (If anyone wants to try the AU with the bug hopefully fixed, the link to the public beta is https://testflight.apple.com/join/PyNtum5r .)
I've communicated a bit with the review team and it seems that they don't consider the AU to be part of the functionality of the app, so I'm going to have to change the container app. My current plan is to make the AU available in the app to a mic (or interface) but not include IAA or Audiobus connectivity.
So, my question is, am I wrong about the thought of not having the AU work as an app with mic, Audiobus, and IAA connectivity? Do you find these features useful even from a small AU? Do you ever even open the app for an AU? Would there be something else that you'd like to see as a feature in an AU containing app?
Thanks for any input you have,