For example, perhaps the auxiliary application runs a local HTTP server with a REST API. The MAS application simply makes HTTP requests to the auxiliary application such as `POST /applescript/doStuff`.
For example, perhaps the auxiliary application runs a local HTTP server with a REST API. The MAS application simply makes HTTP requests to the auxiliary application such as `POST /applescript/doStuff`.
I was talking with apple support and they basically said that if we even offered some extra component to get rid of the spinning gear we would most likely be banned.
https://itunes.apple.com/us/app/boom-2-best-audio-enhancemen...
Note their reference in the description to an 'optional component' that enables system-wide effects.
Citation of the specific term needed. It isn’t against any of them and plenty of apps do it (Things, Boom or Monity come to mind). Apple requires that the app is functional without extra downloads and the app itself must not download the extra executables. But it’s OK to use them for extended functionality (Things: system-wide popup; Monity: extra sensors) as long as you only point the user to where to download the extra helper and they do it themselves (see e.g. http://www.monityapp.com/helper/ for one such helper download page, linked from in app).