App Extension as In-App Purchase?

Being visible and useableg from other apps is part of the point of an app extension. The problem being solved by an audio unit extension is entirely "I have audio processing code in my app, I want another app to be able to use it."

Because if you just want to generate or modify sounds inside your own app, that code is a heck of a lot simpler and less work than creating an extension with its mandatory user interface requirements.

But, as far as I understand you don't have an option to hide audio extensions until the corresponding iAP has been purchased. Instead you have to deal with using your extension's interface to tell the user that they need to do whatever to unlock.

Edit: It does seem like the first half of your post answers your own questions, though.

Will your apps have a login, or just same content IAPs?

Thanks, this helps a bit! 🙂

From my understanding, IAPs needn't be on the system, but downloaded separately upon purchasing. This is how I thought the App Extension (.appex file) would be delivered in such a setup. Such that it wouldn't be exposed to the system (hence "hidden") until purchased. Does that make my intentions a bit more clear? I'm just not sure if downloading and installing separate binaries (as opposed to mere content), and adding them to the system is possible.

Not sure how I answer the first part myself in the post. The mentioned companies who do this isn't through the App Store, but their own applications.

I think you've missed the part in the review guidelines where apps are forbidden to download executable code. See 2.5.2 under Software Requirements.

That means that an app which contains extensions will contain all of them in its application bundle. You can use iAP to restrict the functionality of the extensions, you can't use it to download and install new code.

Indeed, that I have! I'll have to figure out another way then. Restricting access to them might do the trick.

Thank you.