Monday, March 25, 2013

Why Mobile Middleware or 'Mobile Platform"


We are all over the map with Mobile:We engage in discussion with regard to differentiating with frameworks like appcelerator, open frameworks - HTML5, Jquery, Sencha and then discuss the Apple ecosystem and how Sencha and other mobile application development frameworks such as a Xamarin Mono and Unity etc have found a way to by pass xcode requirements. We discuss the merits of native vs. hybrid vs. Mobile Web, moving the discussion to security and scalability, cross platform tooling, cross compilation, democratization of mobile application development and device diversity. --- It is a mess and we tend to lose time and effectiveness of understanding our client's enterprise requirements.
 
The market of cross-platform tools is booming in 2012.  There are over 100 vendors selling tools that range from JavaScript frameworks and app factories to runtimes. All of these seeking to capture developer mindshare, experience and expectations, we notable one's are  Adobe (Flex), Appcelerator (Titanium), AppMobi, Bedrock (Metismo), Ansca (Corona), DragonRad, Kony, Marmalade, MoSync, Netbiscuits, Alcatel Lucent (OpenPlug), PhoneGap, RhoMobile, RunRev (LiveCode), Sencha Touch / jQTouch, Strobe/Sproutcore, Unity, Unreal, Worklight and Xamarin (MonoTouch/Droid).
 
             
Why Mobile Middleware or 'Mobile Platform" : Building upon earlier posts, I think since we are in enterprise space and will eventually have to address the enterprise integration challenges for mobile applications, I think it is vital we center this as a part of our discussion. Some Arguments I have used are as follows:
  1. We want a completely agnostic message to our clients that you can do "native" , hybrid, or mobile web because the real value is in the platform, administration, up-keep, security, adapters, and integration layer we provide better than anyone else. - Integration
  2. Mobile Middleware provides a layer of indirection, which allows for the back end services to be shifted without affecting the end point. - Flexibility
  3. Ability to surgically enable and disable  Application specific to a platform, administratively provide platform specific messages  - Control.
  4. Mobile Middleware also arms the enterprise to adapt and fit into to current Enterprise Security platform ( authentication, authorization and security policy enforcement etc) - Security
  5. Mobile Middleware also  provides an avenue to exploit existing services ( SOA Model) and since these services were design for Web Application, Mobile middleware allows for filtering and altering the content, prior to sending the response back to end use. - Flexibility, control and reuse and Optimization of existing enterprise services.
  6. Mobile Specific Services - Unified push notification, SMS and devices specific notifications etc, provide an avenue to address these via platform.
and more….