A mobile enterprise application platform (MEAP) is a comprehensive suite
of products and services that enable 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".
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 solution’s 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 smart phones, tablets,
notebooks and ruggedized handhelds) with no changes to the underlying business
logic.
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. 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
The Rule of Three refers to a concept developed by analyst firm Gartner,
whereby companies are encouraged to consider the MEAP approach to mobility when
they need their mobile solutions to:
+ Support three or more mobile
applications
+ Support three or more mobile
operating systems (OS)
+ Integrate with at least three
back-end data sources
According to Gartner, using a common mobility platform, like a MEAP,
brings considerable savings and strategic advantages in this situation.
Structure
Components
and Features
A MEAP solution is generally composed of two parts: a mobile middleware
server and a mobile client application. A middleware server is the solution
component that 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. Most MEAPs also come with a mobile configuration/development toolset that
allows companies to create and adjust the mobile solutions.
Mobile applications are software that connect 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.
Writing a custom app extension
is very easy with most MEAP solutions because they use 4GL techniques that do
not require writing code. This toolset comes in the shape of plug-in for an
industry standard IDE, such as Eclipse.
Currently, some new toolsets
have been introduced into MEAP solution for 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(Cordova), Appcelerator. That means a custom
APP can use most of mobile device features without any of 4GL coding or native
coding, and make it once developed, deployed anywhere.
Integrate with multiple server
data sources for leverage SOA services from backend systems.
Leverage development skill and
tools you already know and expertise you already have. 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 MDM
Enhance existing business
platforms by making them accessible to users anywhere, at any time.
MEAPs Can be run on the cloud