![]() ![]() "EMM platforms will still be the connector or trigger point for creating and managing the policies around the apps, but the execution will be done via the operating system as opposed special code injected into the app," Hochmuth said.įor example, the ability to wipe an app from a mobile device or turn off copy and paste will still be controlled through an EMM console - not through the application itself. Management policies for iOS or Android, however, are still configured via an EMM platform, according to Phil Hochmuth, program director for IDC's Enterprise Mobility team. Recent versions of iOS, for example, allow app-level controls such as data loss prevention and secure access without requiring app wrapping code or software development kits. "This is always a moving target."Ī complicating factor is the current trend toward native control of apps through mobile OSes, such as Apple's iOS and Android. Native frameworks are very powerful, but SDKs can fill the gap between the security use cases of the enterprise and the current capabilities of those native OS frameworks," he said. "With all that being said, the AppConfig Community does not completely replace EMM-specific SDKs and wrappers. " AppConfig Community is focused on the developer, so as more and more developers start building modern apps on Windows 10 and beyond, we will develop and promote best practices for the platform," Razavian said. The groups plans to expand to Windows, as well. In doing so, we're collectively accelerating mobile deployments for the enterprise," Razavian said.Ī year after launching, the AppConfig Community membership has grown from 60 to 90 independent software vendors, from four to 19 EMM providers, from 160 to more than 1,400 individual developers and from one to two operating systems (iOS at launch and Android since May 2016). "Our joint mission is simple: to make enterprise app configuration and security less complicated for developers by expanding the use of OS-native standards. Last year, VMware joined forces with several EMM vendors to launch the AppConfig Community, an industry consortium working toward standardization. ![]() ![]() The disadvantage with that approach is two-fold, according to Joseph Razavian, senior manager for technology alliances in end-user computing at VMware.įirst, a vendor like Box will have to make several iterations of its application to support the various SDKs, or app-wrapping engines, in use secondly, users can get confused as to which app they need to download - for example, Box for VMware AirWatch or Box for MobileIron, Razavian said. While some EMM vendors such as Apperian, claim to be able to add app wrapping to virtually any software, "typically, app developers have to expose code through an API and make it wrappable that way," said Phil Hockmuth, program director for enterprise mobility research at IDC. Most app-wrapping capabilities are available natively on EMM software from vendors such as VMware's AirWatch, Box or MobileIron. For example, an app-wrapping API would allow an admin to control who can download a mobile app and whether corporate data accessed by that app can be copied and pasted.Īpp wrapping can be applied during internal development of software or after the fact to off-the-shelf software purchases simply by adding executable code via the SDK. Typically, app wrapping is performed through the use of an SDK from an app or EMM vendor that allows a developer or admin to deploy an API that enables management policies to be set up. Of those businesses, about 60% have deployed some level of mobile application management and its app-wrapping technology subset, the survey showed. Today, about 44% of mid-size to large businesses have rolled out EMM software, according to a survey of 500 IT users by market researcher IDC. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |