New to Mobile Application Development ? Learn about MEAP


Published on

Learn about Mobile application types, Operating Systems and the enterprise's need for Mobility. Look at an example product and learn where a MEAP solution fits into the Mobile solution.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

New to Mobile Application Development ? Learn about MEAP

  1. 1. Mobility and MEAP Overview
  2. 2. Mobility defined The ability of an enterprise to connect, communicate and transact with suppliers, partners, employees, assets, products, and customers from any location through diverse mobile technologies like handsets, PDAs, handhelds, RFID, telematics, GPS, NFC based systems Mobility enables greater convenience, productivity/ efficiency and reach…
  3. 3. The business needs of our clients  Consumer Needs- Greater convenience  Transact Anywhere (eg Mobile payments, Stock trading)  Engage service anywhere (eg. Location services, Emergency services, Basic customer service)  Mobile Marketing (eg.Promotions, Loyalty Programs )  Enterprise Needs- Greater productivity, Greater efficiency  Mobile office (eg. Workflow alerts and approvals, clocking time)  Sales/ field force enablement ( eg Sale call planning & client interaction, Stock taking)  Asset tracking (eg. containers, vehicles)  Improved Supply Chain & Logistics (eg. quicker replenishment, warehouse retrievals)  Needs of New Market Segments- Greater reach  Rural Marketing and Financial Inclusion  Youth and Children  Segments that cannot read, do not have access to/cant use PC
  4. 4. The mobile way Traditional web applications Browser based Accessed through PC / Mobile browsers Platform independent HTML / JSP Traditional web applications Browser based Accessed through PC / Mobile browsers Platform independent HTML / JSP Mobile applications Run on Mobile devices Platform dependent HTML5 / Native API Mobile applications Run on Mobile devices Platform dependent HTML5 / Native API We need this transition to happen smoothly
  5. 5. 5 Platforms for multi-vendor devices The following software platforms will run on hardware platforms from a number of different manufacturers: Java ME Symbian Android Windows Mobile Qt (framework) BREW Palm OS Palm webOS Flash Lite Microbrowser
  6. 6. 6 Platforms for single vendor devices BlackBerry iOS (Apple) Overall, a large number of platforms
  7. 7. Application development problem Variety of Mobile OSes Lack of a common accepted standard Frequent newer OS versions New set of skills required
  8. 8. BuildBuild Run & Connect Run & Connect ManageManage SecureSecure Extend & Create Extend & Create Mobile application development models 8 Hybrid Application iPhone, Android, Windows, etc. Hybrid Application iPhone, Android, Windows, etc. Code: HTML, JavaScript, CSS Debug: Browser (all devices), iPhone Emulator, Android Emulator, etc. App Development Environment (Eclipse) App Development Environment (Eclipse) Web/Hybrid HTML HTML Native Hybrid Device Bridge & MAP APIs Native iPhone ApplicationiPhone Application Apple XCode Apple XCode Native Native MAP APIs Android Dev Tools (ADT) (Eclipse) Android Dev Tools (ADT) (Eclipse) Android ApplicationAndroid Application Native Native MAP APIs Code: Objective-C Debug: iPhone Emulator Code: Java or C Debug: Android emulator Allows HTML UIs to connect to device and MAP APIs Etc. Mix Native and Hybrid code in a single application Allows HTML UIs to connect to device and MAP APIs Native MAP APIs
  9. 9. Traditional Mobile Application development models  Native Application – Uses platform specific native APIs  Web Application – Developed as a web application and accessed via mobile web browser Native Web Application Merit Demerit Merit Demerit Full access to local device services No consistency in programming mode from different vendors Easy reuse of existing web assets No native device services Rich UI because of the of native controls and advanced graphics Fixed function, little flexibility to dynamically adapt, re- skin the application Dynamic delivery of content and services Inconsistency in mobile web browsers Enhanced User experience because of advanced controls Update cycle can be painful Easy to reconfigure and update the application No offline model Service composition not as easy as web applications Performance constraints Distribution of application updated cumbersome
  10. 10. • Mobile Phones • Tablets • Web Gadgets Mobile WebMobile Web WML -> HTML5 TabletsTablets Support for many OSsSupport for many OSs 10 The New Mobile Application development model The MEAP Solution
  11. 11. What is a MEAP Mobile Enterprise Application Platform Web Services Databases 11
  12. 12. MEAP Components Software Studio  Software development and application libraries, usually based on Eclipse  Tools for debugging, testing and deployment Application Server  Installed MEAP software on the server for communication with mobile apps  Integrates with back-end applications and data services Mobile Application  Native application on the device  Web based  Hybrid 12
  13. 13. A method to design and run an application once, from a single code base, and deploy it to many mobile web browsers Compatibility with browsers supporting not just HTML5 but older markup languages as well: HTML / XHTML / JavaScript / Basic channels. HTML5 supports the mobile web on the following OSs, covering over 9,000 devices : • iOS (iPhone and IPad) • Android (mobile phone and tablets) • BlackBerry (mobile phone and tablets) • Palm/WebOS • Symbian/MeeGo/Maemo/Qt HTML 5 Cross platform solution
  14. 14. IBM Worklight? 14 Worklight is an open, complete and advanced mobile application platform for HTML5, hybrid and native apps.
  15. 15. Worklight Server Unified notifications, runtime skinning, version management, security, integration and delivery Worklight Console A web-based console for real-time analytics and control of your mobile apps and infrastructure Worklight Studio The most complete, extensible environment with maximum code reuse and per-device optimization Worklight Overview 15 Worklight Runtime Components Extensive libraries and client APIs that expose and interface with native device functionality←
  16. 16. Integrating Best-in-class Tools Worklight is compatible with prominent HTML5 libraries and tools: 16
  17. 17. Mobile Device Management / BYOD Testing Security Business model Version control Push Notifications Other Mobile Channel Challenges
  18. 18. 18 Connect with me @ArvindMobile