How can Rollout allow you to push code-level updates to live iOS apps and be fully compliant with Apple’s guidelines? Glad you asked.
Our lawyers asked me to let you know that this isn’t legal advice, but you don’t need a law degree to understand the wording in Apple’s official guidelines.
Apple’s guidelines explicitly permit you to push executable code directly to your app, bypassing the App Store, under these two conditions:
- The code does not provide, unlock or enable additional features or functionality
Rollout is simply the first and only solution that provides the ability to push code-level updates to native Objective-C and Swift apps.
The second condition, no new features or functionality, is really up to you. Rollout isn’t intended to push new features or functionality. It is meant to tweak or fix them, avoiding the minor releases needed to fix bugs, add logging or tracking, update messages, force users to upgrade, etc. For new features or functionality you need to release through the app store.
FYI, Rollout’s SDK is installed on over 50 million iOS devices and there’s never been an app rejected because it uses Rollout. I’m just saying that because it’s good to know that thousands of other developers are using Rollout, so you’re not alone.
Of course, you should check the official guidelines yourself, so here is the document:
The relevant sections are here:
3.3.3 […] an Application may not provide, unlock or enable additional features or functionality through distribution mechanisms other than the App Store […]