Mobile enterprise application platform

This article contains wording that promotes the subject in a subjective manner without imparting real information. Please remove or replace such wording and instead of making proclamations about a subject's importance, use facts and attribution to demonstrate that importance. (January 2016) (Learn how and when to remove this template message)

|

A mobile enterprise application platform (MEAP) is a suite of products and services that enable the development of mobile applications. The term was coined in a Gartner Magic Quadrant report in 2008 when they renamed their "multi-channel access gateway market".[1]

## Contents

* 1 Purpose
* 2 Rule of three
* 3 Components and features
* 3.1 Structure
* 3.2 Features and capabilities
* 4 See also
* 5 References

## Purpose

MEAPs address the difficulties of developing mobile software by managing the diversity of devices, networks and user groups at the time of deployment and throughout the mobile computing technology lifecycle. Unlike standalone apps, a MEAP provides a comprehensive, long-term approach to deploying mobility. Cross-platform considerations are one big driver behind using MEAPs. For example, a company can use a MEAP to develop the mobile application once and deploy it to a variety of mobile devices (including smartphones, tablets, notebooks and ruggedized handhelds) with no changes to the underlying business logic.[2]

Platform applications are best for companies that wish to deploy multiple applications on a single infrastructure, scaled to the size of their current mobile field force and available in an online and offline mode.[3] Mobile platforms provide higher-level languages and easy development templates to simplify and speed the mobile application development timeframe, requiring less programming knowledge for mobile business application deployment.

## Rule of three

Gartner observed companies consider the MEAP approach when they need to:

1. Support three or more mobile applications
2. Support three or more mobile operating systems (OS)
3. Integrate with at least three back-end data sources

Gartner promoted using a common mobility platform in this situation.[4]

## Components and features

### Structure

A MEAP is generally composed of two parts: a  mobile middleware server and a mobile client application. A middleware server handles all system integration, security, communications, scalability, cross-platform support, etc. No data is stored in the middleware server—it just manages data from the back-end system to the mobile device and back.

Mobile applications is software that connects to the middleware server and drives both the user interface and the business logic on the device. These applications are often able to transfer seamlessly across the Mobile operating system, as a platform to launch applications upon. Mobile apps can be deployed as "thick" applications—or native apps that are installed on the device—or rendered in the device's browser using technologies such as HTML5 (something that's often called the "thin" approach). Whether a "thick" or "thin" application is deployed depends on application complexity, device support, requirements for user experience, and the need for app availability in the absence of network coverage.

### Features and capabilities

* MEAPs can support more than one type of mobile device and operating system without having to maintain separate sets of code.
* MEAP typically contains a mobile middleware server where integration connectivity, security, app management are supported.
* Most MEAPs use techniques that do not require writing code to extend them. This can use an industry-standard integrated development environment, such as Eclipse.

Some tools have a hybrid mode, which uses JavaScript-based UI design SDK, such as Dojo Toolkit, YUI Library, jQuery Mobile, Sencha Touch. And a new JavaScript-based Device featured APIs encapsulation (GeoLoc, Connective, AccMeter, Camera, G sensor, Events, File system, etc.) is plugged into IDE as well, such as PhoneGap (Apache Cordova), Appcelerator. That means a custom APP can use most of the mobile device features without any of 4GL coding or native coding, and make it once developed, deployed anywhere.

* MEAPs evolve the principle of defining the mobile business support mobile workflow and embedded functionalities by moving beyond 4GL tools towards using the graphical environment and dedicated script language.[5]
* Integrate with multiple server data sources for leverage SOA services from backend systems.
* Leverage development skill and tools one already knows and expertise one already has. More details are in the Mobile application development section.
* Centrally manage mobile applications. The management of the actual devices that is more tailored for B2E scenario and it is typically done with the mobile device management (MDM). As well, some enable bring your own device features by integrating with MDM.
* Enhance existing business platforms by making them accessible to users anywhere, at any time.
* MEAPs Can be run on the cloud[6]

A 2016 marketing report predicted a $189 billion market by 2020.[7][8]

## See also

* Cross-platform software
* Field service management
* Application server
* Low-code development platforms
* Mobile application development
* Multi-channel app development
* Mobile backend as a service
* how to create an app for iPhone or Android

## References

1. ↑ "We've renamed the multichannel access gateway market to the mobile enterprise application platform market, reflecting its maturation, Apple's entry, and the move of mobile tools and platforms to the application development mainstream." Michael J. King, William Clark, "Magic Quadrant for Mobile Enterprise Application", Gartner Note G00162969, 18 December 2008. The following year Gartner added the "mobile consumer application platform" category in another magic quadrant report .
2. ↑ Michael Brandenburg, Technical Editor. "Mobile enterprise application platforms: A primer". Searchmobilecomputing.techtarget.com. http://searchmobilecomputing.techtarget.com/tutorial/Mobile-enterprise-application-platforms-A-primer. Retrieved 2013-05-08.
3. ↑ "Archived copy". Archived from the original on 30 March 2012. https://web.archive.org/web/20120330123247/http://storage.slalom.com/assets/documents/wp-meap-pov.pdf. Retrieved 2011-08-08.
4. ↑ Gartner RAS Core Research Note G00211688, Michael J. King, William Clark, 20 April 2011
5. ↑ "MSP, Mobile Service Platform". http://i-rose.si/mobilna-storitvena-platforma-msp/. Retrieved 26 December 2013.
6. ↑ "Many-device-to-many-platform Mobile App Integration is No Longer a Challenge". Configure.IT. http://www.configure.it/blog/many-device-to-many-platform-mobile-app-integration-is-no-longer-challenge/. Retrieved 2014-11-20.
7. ↑ "Mobile app market to grow 270% to $189 billion by 2020". 2 November 2016. https://venturebeat.com/2016/11/02/mobile-app-market-to-grow-270-to-189-billion-by-2020-with-games-accounting-for-55/.
8. ↑ "Mobile Apps: Redefining the Hospitality Industry" (in en-us). https://ibuildapp.com/redefining-the-hospitality-industry/.

0.00

(0 votes)

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Software:Mobile_enterprise_application_platform&oldid=3897440"