Benefits for the Application User

From a user’s perspective, a Majic-based mobile applications running on a smart device look and behave like any other application, with no Majic-specific training required to operate the application. Additionally, the requirement to periodically update the application is no longer the user’s concern, removing any administrative burden.

Benefits for the Application Provider

Centralised Control
Typically, with native applications, the decision to upgrade to the latest version is in the hands of the end user. In the enterprise this can be addressed by the deployment of MDM, but in a BYOD environment where MDM is not deployed, the Majic Platform can provide the centralised control needed to ensure that users always interact with the latest version of the application.

Simple Network Integration
Both the MajicServer and Majic-based applications communicate over networks using HTTPS. Additionally, the MajicServer can integrate with other network services such as SSO, LDAP and Active Directory.

Better Performance Over Poor Networks
Due to Majic’s composable nature, the delivery of application capabilities to the user means those components can be delivered piecemeal to the user’s device, enabling application features to be delivered over networks as poor as GPRS. Additionally, being a native application running locally on a user’s device, the application can process and store data on-device and then simply wait for network conditions to improve before sending that data to its destination.

Native On-Device Performance
Being a native application, Majic-based application can fully take advantage of devices built into (or attached to) the smartphone or tablet, such as NFC readers, cameras and fingerprint sensors.

Benefits for the Application Developer

True Mobile DevOps
Continuous integration or continuous deployment – commonly referred to as ‘DevOps’ – is a methodology by which the disparate worlds of development and integration are brought together into one smooth process. Tools built to support this process enable application software to be rigorously tested before deployment, thereby assuring software quality.

However, for mobile applications the deployment ‘last mile’ is by and large still very much dependent upon each iteration of a given mobile app being uploaded to a mobile app store or MDM (Mobile Device Management) portal, and the end user making a conscious decision to install/update/uninstall said application. There are no guarantees that all users of the application will do this, unless forced to by some technical means.

The Majic platform provides an elegant solution to this problem by embodying mobile DevOps. The search-based, dynamic container/component application model inherent in Majic closes the logistics gap of the deployment by enabling business logic to be added, updated or removed from a Majic-powered application – over the air and in real time, while the application is still running.

This model of continuous deployment (“mobile DevOps” or “AppOps”) enables Majic-powered mobile applications to transparently evolve – even after going into production, including post-deployment. Business logic can be updated immediately, while in the eventuality of static code in the container (the on-device ‘framework’ of the app) needing an update, this can be applied either directly from the MajicServer itself or by more traditional means, such as the respective mobile app stores.