Today more and more enterprise wants to go on Tablets ,Mobiles. Tablets are useful for variety of scenarios such as displaying graphs, richer widgets something for people who needs to work on Analysis. Mobiles on the other hand are very handy and are useful for people on field and who do not need much of these widely used graphs or widgets.
This blog talks about the high level direction that Enterprises can take in order to arm their Sales or Service folks.
STEP 1 : Choose a Mobile Enterprise Application Platform (MEAP ) or DIY (Do IT Yourself)
The first step in the movement towards enterprise mobility is answering some of the questions such as
- Do we need to support on multiple device types such as Tablets and Mobiles?
- Do we need multiple types of apps such as hybrid, native and mobile web apps?
- Do we need to support IOS, Android or Windows platform?
- Do we need to integrate with many backend platforms?
- Do we need to support multiple mobile apps?
- Do we need apps to go to market fast ?
- Do we need to support “Bring Your Own Device” capabilities?
If your answer is YES to many of these questions then you many need to look at Mobile Enterprise Application Platform(MEAP) such as IBM WorkLight(http://www-01.ibm.com/software/mobile-solutions/worklight/). Of course there are many others in market such as Kony(http://www.kony.com/), Rhomobile etc.If not then one can look at developing apps on their own using JQMobile,DOJO mobile .
STEP 2:Hire a Mobile Designer
Please note mobile and tablet experience is hugely different from that of desktop.There are various commands that is present only in the mobile world for example swipe ,touch etc .A mobile designer will be focusing on these kind of user experience.
STEP 3:Choose your middleware
Though some MEAP’s comes with its middleware , it is better to reuse the middleware if one has already have it. An enterprise mobile apps needs data in its own format , care must be taken to cater in its format, so some amount of transformation is needed. Also one needs to connect to various services in standard way all these things can be handled in a middleware such as IBM Websphere middleware.
STEP4: Move towards Web Oriented Architecture
In an Enterprise most of the systems are already built and may be SOA enabled .But is that enough ? , I do not think so .Instead Enterprises needs to relook at SOA and "mobilify" the services.What does that mean ? .
Today SOA is all about system to system integration happening within the Enterprise.SOA was always about sending detailed data , mobile world does not need that kind of data , instead the data should be thin so that it can be optimized on lower bandwidth 3G network.
A typical SOA is always exposed as SOAP or sometimes as REST .SOAP has lot of head weight and not suitable for mobile world. Mobile world needs light weight JSON data .Enterprise needs to cater to Web Oriented Architecture and support these modern data formats and services must be very lightweight.