The Infosys Labs research blog tracks trends in technology with a focus on applied research in Information and Communication Technology (ICT)

« Enterprise Gamification - "Design" matters! | Main | Messaging: An Integral Part of a Mobile Application »

CRM/ERP Mobile Capabilities or MADP ?

Over the last couple of decades, the enterprise IT infrastructure has made multiple strides. From the punched cards, hierarchical databases to the complex ERP / CRM systems of today it has improved by leaps and bounds. It offers majority of the enterprise functionality ranging from planning, procurement to Human resource management, finance management, inventory management and so on.

Evolution of mobility as a channel has added a huge set of opportunity to the functionality available in ERP / CRM systems. Till a few years back, it was pre dominantly a web based and a desktop / laptop based application with majority of the functionality available online. Wireless Technology as a channel has added a lot more complexity to already complex ERP / CRM systems. Below are the typical questions that any ERP/CRM product company faces while providing functionality on the mobile channel 

  1. What functionality will make sense on mobile platform?
  2. What are the devices to support?
  3. How to keep the support up-to-date for ever changing mobile devices and be future proof?
  4. How to cater to the data required from sources outside of ERP / CRM?
  5. How to handle Mobile Device Management?
  6. How to handle offline and synchronization capabilities?

The basic strength of any ERP / CRM solution is in handling a business process seamlessly. It provides all the data, validations and safeguards related to any particular function like HR, finance, procurement etc. Mobility as a channel for ERP / CRM is an emerging one right now and has not become mainstream as a desktop / laptop based web application. So it has been observed that the mobile offering which is provided out of the box by any CRM / ERP provider has strong points like integration with backend being readily available, output on selected devices readily available. However because of the inherent nature of the offering it has some constraints also as follows

  1. The offering is tightly integrated with ERP / CRM at the backend. It is not flexible to integrate  with back ends apart from ERP / CRM itself
  2. It typically targets only specific devices / handsets. So the device diversity which is a hallmark of the mobile world is a challenge to handle
  3. Many times the offering is available only on one channel. E.g. browser channel. If one has to extend it to the other channels like native or hybrid, that capability is either not present or one has to spend a lot of effort for extension
  4. The offline and synchronization capabilities are limited
  5. For extending the capability on SMS / Push / USSD channels, there is a custom development required

The usage of a Mobile application Development platform (MADP) can address majority of the issues mentioned above at the same time providing simplicity in development.  It provides one with faster and smarter way of building mobile applications for not just the ERP / CRM application, but any consumer or enterprise application.

Finally the choice of a particular approach for developing mobile applications based on CRM / ERP is really driven by the business need of the mobile application, the target user segments and devices, type of channels one wants to utilize, time to market and many more. One has to evaluate the options available keeping in view the long term view and comprehensive mobility needs of an organization.


Well put! There is diversity on the enterprise apps side and there is diversity on the consumption side. Most MADPs address enterprise integration more comprehensively than the mobile UX and workflow. Infosys mConnect has been built to handle both and comprehensively so. Suggest a look!

Mandar, nice article, well written, it highlights the different options for Enterprise Mobility Solutions. With most of the Enterprise Solution Vendors like SAP, Oracle, Safeforce, others, having their own mobility solutions, we also have other mobility middleware like Infosys mConnect, Antenna, Kony, Others and independant (non-middleware) development options like HTML5/CSS3/JS, Native app development, Enterprises have to really evaluate their options and conclude on the right approach, based on their short term and long term mobility needs and requirements.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on