Mobile enterprise application platform
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
A mobile enterprise application platform (MEAP) is a type of mobile application development platform (MADP) that includes a suite of products, frameworks, services, and toolkits to assist in the development of mobile applications.[1] MEAP platforms enable organisations or businesses to develop, test, and deploy applications through the use of standardization and protocols.
An organisation may either build its own Integrated Development Environment (IDE), a software engineering toolkit that offers such features, or it may purchase or fork a MEAP/MADPs from a third party. A MEAP/MADP ideally includes tools for testing, debugging, and maintaining existing applications, as well as API calls for back-end databases and "middleware" for linting, parsing, and compiling.[2]
The term's origin is attributed to a Gartner Magic Quadrant report in 2008 and was formerly referred to as the "multichannel access gateway market."[3]
Purpose and function
[edit]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 life cycle. Unlike standalone apps, MEAP apps provide a comprehensive, long-term approach to both developers and end-users.
Cross-platform utilities are a significant factor behind using MEAPs. MEAPs can be used to develop a mobile application, deploy it to various mobile devices with different operating systems, and maintain it through continuous testing. Examples include smartphones running Android or iOS, tablets, notebooks, and some modified handheld game consoles. MEAPs ideally allow for cross-platform services simultaneously without changing the underlying machine or business logic. The target audience of these platforms is companies wishing to rapidly develop multiple applications on an infrastructure. This infrastructure can be available on-premises (offline), in the cloud (online) or a mixture of the two.[4][2]
Mobile platforms provide templates for development through the use of high-level languages to accelerate development and maintenance cycles.[5]
Rule of Three
[edit]Gartner observed that companies consider the MEAP approach when they need to:
- Support three or more mobile applications
- Support three or more mobile operating systems (OS)
- Integrate with at least three back-end data sources
Gartner advocated using a common mobility platform in this situation.[6]
Components and features
[edit]Structure
[edit]A cloud-infrastructure 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, and more. No data is stored in the middleware server—it manages data from the back-end system to the mobile device and back.
Mobile client applications are software that connect to platform or middleware servers and drive both the user interface and the back-end logic on a device. Such applications are able to transfer across mobile operating systems as a tool upon which to launch applications. Mobile apps are typically deployed as "thick" applications or as "native apps" that are installed on the device. They may also be rendered as "thin" applications using browser technologies such as HTML5. The choice between these approaches depends on the complexity, device support, requirements for user experience, and the need for app availability in the absence of network coverage.[7]
Features and capabilities
[edit] |
MEAPs offer robust support for multiple types of mobile devices and operating systems enabling cross-platform functionality without requiring separate sets of code. At the core of most MEAPs is a mobile middleware server that facilitates integration connectivity, security, and app management. This middleware allows organisations to streamline their mobile application operations effectively.
Many MEAPs employ techniques that minimise or eliminate the need for extensive coding. These platforms often provide industrial-standard integrated development environments (IDEs) like Eclipse, which simplify app development. Some tools also support hybrid modes, utilising JavaScript-based UI design SDKs such as Dojo Toolkit, YUI Library, jQuery Mobile, or Sencha Touch. By integrating with frameworks like Apache Cordova (formerly PhoneGap) or Appcelerator, these tools encapsulate various device-specific APIs—such as Geo Location, Connectivity, Accelerometer, Camera, and File system - within the IDE. This capability allows developers to build and deploy custom applications that leverage mobile device features without requiring native or 4GL coding.
MEAPs advance mobile business support to "mobile workflow" by evolving from traditional 4GL tools to more sophisticated graphical environments and dedicated scripting languages.[8] They integrate seamlessly with multiple server data sources, enabling businesses to leverage Service-Oriented Architecture (SOA) services from backend systems. Additionally, these platforms leverage pre-existing development skills, tools, and expertise, providing significant value for organisations already invested in specific technologies. More details are in the mobile application development section.
Centralised management is another hallmark of MEAPs, particularly in business-to-employee (B2E) scenarios. While the management of mobile devices is typically handled through mobile device management (MDM) systems, MEAPs focus on centrally managing mobile applications. Some platforms even enhance device functionality by integrating with native features. These capabilities, combined with the ability to enhance existing business platforms and make them accessible anywhere, at any time, underscore MEAPs' value in enterprise environments.
Many MEAPs are cloud-enabled[9], offering flexibility for deployment and scalability. They also provide low-code or no-code tools, simplifying app development further, and include advanced features like remote device management and offline capabilities. However, despite their strengths, MEAPs may have limitations, such as vendor lock-in and restrictions on customisation, which organisations should consider when adopting these platforms.
See also
[edit]- Cross-platform software
- Field service management
- Application server
- Low-code development platforms
- Mobile application development
- Multi-channel app development
References
[edit]- ^ Steele, Colin. "What is mobile application development platform (MADP)? | Definition from TechTarget". TechTarget. Retrieved 23 December 2024.
- ^ a b Brandenburg, Michael. "Mobile enterprise application platforms: A primer". Searchmobilecomputing.techtarget.com. Retrieved 8 May 2013.
- ^ "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 Archived 12 July 2012 at the Wayback Machine.
- ^ "Archived copy" (PDF). Archived from the original (PDF) on 30 March 2012. Retrieved 8 August 2011.
{{cite web}}: CS1 maint: archived copy as title (link) - ^ "Mobile & Web Development Company - Surf". December 2023.
- ^ Gartner RAS Core Research Note G00211688, Michael J. King, William Clark, 20 April 2011
- ^ Frick, Tim (12 March 2011). "Going Mobile: Thick or Thin Client?". Mightybytes. Retrieved 27 November 2024.
- ^ "MSP, Mobile Service Platform". i-Rose, Ltd. Retrieved 26 December 2013.
- ^ "Many-device-to-many-platform Mobile App Integration is No Longer a Challenge". Configure.IT Blog. Configure.IT. 17 November 2014. Retrieved 20 November 2014.