Talk:Mobile application management

"Mobile Application Management (MAM) describes software and services that accelerate and simplify the creation of internally developed or “in-house” enterprise mobile applications. It also describes the deployment and management of in-house and commercially available mobile apps used in business settings on both company-provided and “bring your own” smartphones and tablet computers."

The very first sentence in this article is completely wrong. Mobile Application Management is not about the creation of enterprise mobile apps. It's about everything that happens after an application is created, from deployment to security to support. Developing mobile app is called Mobile Application Development.


 * I can kind of understand how the term MAM could be used in the context of development, but I'm unaware of it being used widely in this context. It's primary use is as you stated. SimonBramfitt (talk) 16:21, 2 January 2013 (UTC)
 * One more thing, the analyst cited as source for MAM as development tool now speaks about MAM in the context of application deployment. SimonBramfitt (talk) 16:21, 2 January 2013 (UTC)

"When an employee brings a personal device into an enterprise setting, MAM enables the corporate IT staff to provision the device, download appropriate applications, control access to back-end data, and “wipe” the device if it is lost, or when its owner no longer works with the company."

This statement is inaccurate. Mobile Application Management (MAM) does not enable corporate IT staff to provision device. That's what Mobile Device Management (MDM) is for. Same for wiping the device if it is lost. This article is getting MAM and MDM all mixed up.


 * MAM does allow apps to be provisioned to the device, and it allows managed app data to be removed (wiped) from the device. What it doesn't do is allow total control of the device, its firmware, access to unmanaged apps and data associated with unmanaged apps. SimonBramfitt (talk) 16:21, 2 January 2013 (UTC)

The whole sections of "Applications" and "The Mobility Invasion and BYOD" do not make any sense. This article is about Mobile Application Management. Why is there a list of mobile applications on the article? The assertion that email, calendar and contact database are being supplemented by line of business applications such as CRM, inventory management, etc... is crazy. You mean people don't use email and calendar on mobile device anymore? The Mobility Invasion and BYOD section is a cut-and-paste of various analyst "opinions" and is taken out of context. If the section is intended to explain why there is MAM or the background of MAM, it is doing a terrible job.

As it stands, this article is a piece of junk. Sorry. — Preceding unsigned comment added by 99.187.238.190 (talk • contribs) 09:30, 2 December 2012‎


 * You're right it's rubbish. I'm fixing it.


 * Constructive criticism welcomed --SimonBramfitt (talk) 01:24, 6 January 2013 (UTC)

evolution of mam
Firstly it is clear this this article is much improved over what it was before. Congrats!

Secondly, I wonder what the justification of this sentence is: "On the other hand, iOS 7 or Samsung KNOX include features that make app wrapping no longer a necessity." If this is true what is the purpose of MAM now? Kenanwang (talk) 22:46, 18 July 2013 (UTC)

From the web site of Samsung : "To protect enterprise apps and data from being compromised by third-party apps, Samsung KNOX provides an app wrapping service.". So I do not understand the sentence "Samsung KNOX include features that make app wrapping no longer a necessity", as Knox is based on app wrapping. 14:49, 10 October 2013 (UTC)193.49.124.107 (talk)

External links modified (February 2018)
Hello fellow Wikipedians,

I have just modified one external link on Mobile application management. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20130701173859/http://www.networkworld.com/news/tech/2013/050713-app-wrapping-269503.html to http://www.networkworld.com/news/tech/2013/050713-app-wrapping-269503.html

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 04:43, 3 February 2018 (UTC)