4. App developers can and do make real-time changes to an approved app without adding new code and without requiring users to download a new update from the App Store. There are a number of names and methods for this process including feature flag, hot patch, bug flag, hotfix, feature toggle and server based update, but each describes the same process. For the purpose of this discussion, I will refer to the process generally as a “hotfix”, which is how the process is typically referred to within Epic.
5. Hotfixes work by coding the app to check for new content that is available on the developer’s server or new instructions on what to make accessible in the app. Hotfixes are commonplace, including for apps designed to run on Apple’s mobile devices.
6. Many apps run a check for hotfixes as part of their normal startup process.
7. A developer can use hotfixes to make accessible content or features in an app that are in the code but are not initially available to users. The content or feature is accessible only after the app checks the developer’s server and is “notified” by the server to display the new content or feature. For example, game developers often include new characters, new items, or new levels in the code submitted to Apple, which are not initially available to users but become accessible at a later date, once the app is “notified” by the game developer’s server that it should make these features accessible.