Glad you asked.
My 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 three conditions:
- The code is run by Apple’s built-in WebKit framework
- The code does not provide, unlock or enable additional features or functionality
- The user doesn’t see the update is happening
A proof that React Native is not more Native than Capacitor 😆
Capgo is simply the first affordable solution that provides the ability to push code-level updates to native Capacitor apps. The second condition, no new features or functionality, is really up to you.
Capgo 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. For your information, Ionic AppFlow (the alternative for big corporate) is installed on over 50 million iOS devices and there’s never been an app rejected because it uses it.
I’m just saying that because it’s good to know that thousands of other developers are using live updates, so you’re not alone.
Apple and Google have their set of own rules on how to update apps.
Check my next article for more information on how to install Capgo to bypass review.