8 Part IV n Development on top of an existing app with the same bundle identifi er, all the application and user data contained within the sandbox will remain untouched. If the user removes the app fi rst, before installing the updated version, then all data will be lost. It’s important to communicate this clearly to your users. While this can be done through custom code, there are a variety of thirdparty vendors that provide both the logic in the pre-built app catalog template as well as a software development kit (SDK) that can be embedded within custom in-house apps to automatically detect and manage updates. For example, Apperian’s app catalog, as shown in Figure 19-2, provides easy access to updates within its template app catalog as well as an SDK for the update capability to be easily included in custom apps. Figure 19-2: Managing application updates is the responsibility of each enterprise, so you can either build that capability internally or use a third-party solution. Using a Third-Party Solution In addition to the option of building an app catalog yourself, there is also the option of using a solution from a third-party vendor. There are a number of vendors with enterprise app catalog products. Most of those vendors offer the app catalog as part of an overall mobile device management (MDM) product, but there are also stand-alone products. The MDM vendors will be discussed Copyrighted Material. Not for Redistibution. Copyright © 2011, John Wiley and Sons.
