Jump to content

Mobile application management

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Codename Noreste (talk | contribs) at 04:00, 12 October 2023 (Reverted edits by Shahriar3795 (talk): using Wikipedia for advertising/promotion (HG) (3.4.12)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Mobile application management (MAM) describes the software and services responsible for provisioning and controlling access to internally developed and commercially available mobile apps used in business settings, on both company-provided and 'bring your own' mobile operating systems as used on smartphones and tablet computers.[1]

Mobile application management provides granular controls at the application level which enable system administrators to manage and secure application or 'app' data.[2] MAM differs from mobile device management (MDM), which focuses on controlling the entire device, and requires that users enroll or register their device, and install a service agent.[2][3]

While some enterprise mobility management (EMM) suites include a MAM function, their capabilities may be limited in comparison to stand-alone MAM solutions, because EMM suites require a device management profile in order to enable app management capabilities.[4]

History

Enterprise mobile application management has been driven by the widespread adoption and use of mobile applications in business settings. In 2010, the International Data Corporation (IDC) reported that smartphone use in the workplace will double between 2009 and 2014.[5]

The 'bring your own device' (BYOD) phenomenon is a factor behind mobile application management,[1] with personal PC, smartphone, and tablet use in business settings, vs. business-owned devices, rising from 31 per cent in 2010 to 41 per cent in 2011.[6] When an employee brings a personal device into an enterprise setting, mobile application management enables the corporate information technology (IT) staff to download required applications, control access to business data, and remove locally cached business data from the device if it is lost or stolen, or when its owner no longer works with the company.[7][8]

Use of mobile devices in the workplace is also being driven from above.[weasel words] According to Forrester Research, businesses now see mobile as an opportunity to drive innovation across a wide range of business processes.[9] Forrester issued a forecast in August 2011 predicting that the "mobile management services market" would reach $6.6 billion by 2015 – a 69 per cent increase over a previous forecast issued six months earlier.[9]

Citing the plethora of mobile devices in the enterprise – and a growing demand for mobile apps from employees, line-of-business decision-makers, and customers – the report states that organizations are broadening their "mobility strategy" beyond mobile device management to "managing a growing number of mobile applications".[9]The advent of Internet of Things (IoT) has been changing lives for the better. It is not limited to homes but, has a pivotal role connecting teams, devices and decisions. With more connected devices, there is a boost in data generation, data analysis and reporting.

App wrapping

App wrapping was initially a favoured method of applying policy to applications as part of mobile application management solutions.

App wrapping sets up a dynamic library, and adds to an existing binary that controls certain aspects of an application. For instance, at start-up, you can change an app so that it requires authentication using a local passkey. Or you could intercept a communication so that it would be forced to use your company's virtual private network (VPN), or prevent that communication from reaching a particular application that holds sensitive data.[1]

Normally, application wrapping is performed using a SDK from an application or EMM seller that permits an engineer or administrator to convey an API that empowers the board arrangements to be set up. For instance, an application wrapping API would permit an administrator to control who can download a portable application and whether corporate information got to by that application can be reordered. Application wrapping can be applied during interior advancement of programming or sometime later to off-the-rack programming buys essentially by adding executable code through the SDK. [10]

Quite possibly the most broadly utilized portable application stages, Microsoft's Office 365, likewise gives its own extraordinary arrangement of issues respect to the board. Before, Office 365 didn't permit application the executives by means of outsider EMM supports; that usefulness was accessible just through its InTune cloud-based administration. [11]

Increasingly, the likes of Apple and Samsung are overcoming the issue of app wrapping. Aside from the fact that app wrapping is a legal grey zone, and may not meet its actual aims, it is not possible to adapt the entire operating system to deal with numerous wrapped apps. In general, wrapped apps available in the app stores have also not proven to be successful due to their inability to perform without MDM.

System features

An end-to-end mobile application management solution provides the ability to: control the provisioning, updating, and removal of mobile applications via an enterprise app store, monitor application performance and usage, and remotely wipe data from managed applications. Core features of mobile application management systems include:

See also

References

  1. ^ a b c "The science of app wrapping". www.NetworkWorld.com. Network World. 7 May 2013. Archived from the original on 1 July 2013. Retrieved 8 May 2013.
  2. ^ a b Steele, Colin (12 August 2013). "Mobile device management vs. mobile application management". SearchMobileComputing.TechTarget.com. TechTarget – SearchMobile Computing. Retrieved 23 October 2020. Mobile device management and mobile application management do different things but also have some overlap. Knowing their differences is important.
  3. ^ Faas, Ryan (27 March 2012). "BYOD failure - five big reasons why employees don't want to use their iPhones, iPads at work". www.CultOfMac.com. Cult of Mac. Retrieved 23 October 2020.
  4. ^ Silva, Chris; Wong, Jason (30 June 2014). Use the Mobile App mix to choose an enterprise app store strategy. Gartner. p. 6. Retrieved 18 November 2015. {{cite book}}: |website= ignored (help)
  5. ^ "Unisys consumerization of IT benchmark study – summary survey results" (PDF). blogs.Unisys.com. Unisys Corporation. 10 August 2010. Archived from the original (PDF) on 23 July 2016. Retrieved 13 July 2022.
  6. ^ "Beyond the PC: survey on personal technology". The Economist. London, England. 8 October 2011. p. 11.
  7. ^ "Gruman, Galen, 'Mobile Edge'". www.InfoWorld.com. InfoWorld. 26 April 2011. Archived from the original on 13 August 2014. Retrieved 17 October 2011.
  8. ^ "Why business needs mobile application management solution?". CloudSmallBusinessService.com. Small Business Software Reviews, Services Insight and Resources. 5 October 2017. Retrieved 23 October 2020.
  9. ^ a b c McCarthy, John C., and Pelino, Michele, 'Mobile Management takes a 180-degree turn', Forrester Research, 11 August 2011
  10. ^ computerworld.com/article/3209907/app-wrapping-the-key-to-more-secure-mobile-app-management.html
  11. ^ computerworld.com/article/3209907/app-wrapping-the-key-to-more-secure-mobile-app-management.html
Retrieved from "https://en.wikipedia.org/w/index.php?title=Mobile_application_management&oldid=1179742857"