IBM Presentation for Mobile Developer Summit India

Uploaded on

Presentation by IBM delivered at the Mobile Developer Summit in Bangalore, October 10, 2012 by Mehul Mehta

Presentation by IBM delivered at the Mobile Developer Summit in Bangalore, October 10, 2012 by Mehul Mehta

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    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

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Everyone wants an “app for that” – asolution to accelerate mobile appdevelopment and deliveryMehul MehtaRational, IBM Software Labs
  • 2. The Mobile Shift is what happens when people adopt and use mobile devices of their choice to engage with brands, employers, information, and each other.Source: Forrester Research, Inc., June 2012 “Build Great Mobile Apps That Drive Engagement”
  • 3. • Location becomes irrelevant.• Customers expect to get their stuff anywhere.• Multi-channel is the new normal.• App intensity explodes.© 2012 Forrester Research, Inc. Reproduction Prohibited
  • 4. Need proof?• 60% of Facebook updates are from mobile devices.• 60% of transactions are from mobile devices.• 70% of Pandora radio is delivered to mobile devices.• Think about what you do on your smartphone or tablet – and why. © 2012 Forrester Research, Inc. Reproduction Prohibited
  • 5. Mobile is the NEXT dominant phase of computing Mobile is different: Mobile/Wireless/Cloud • Transformational business models • Faster lifecycles • More iterative Client/Server Web/Desktop Host/Mainframe IBM will play a significant part in this new era of mobile computing.
  • 6. IBM’s strategy addresses full range of mobile enterprise needsExtend & Transform Build & ConnectExtend existing business Build mobile applicationscapabilities to mobile devices Connect to, and runTransform the business by backend systems in supportcreating new opportunities of mobile Manage & Secure Manage mobile devices, services and applications Secure my mobile business
  • 7. A deeper look at Build & Connect capabilitiesExtend & Transform Build & Connect Build mobile applications Connect to, and run backend systems in support of mobile Key Capabilities • Mobile web, hybrid and native app development • Enterprise data, service, and application integration • Complete development project lifecycle management Manage & Secure
  • 8. Addressing top mobile development pain points Delivering high quality apps that engage users Developing for multiple mobile platforms and meet business objectivesHighly fragmented set of platforms, Poor quality can negativelydevices, languages, and tools impact brand imageincreases cost and complexity of Bad ratings and commentsdevelopment and test can cause other users toChoosing not to support one or more avoid trying an appplatforms reduces the reach of anapplication Integrating with enterprise systems Meeting accelerated time to market requirementsRecreating instead of leveraging Hand-off errors and delaysexisting business logic increases between teams slows progressmaintenance costs and risk of and responsiveness toinconsistent behavior features and fixesLack of ready back-end services Misalignment of stakeholdersslows front-end development results in late rework andand increases potential for last increased cycle timesminute integration issues
  • 9. Challenge 1: Fragmentation and developing for multiple mobileplatforms • Several major platforms with their own – Tools – Languages, APIs, and programming models – App stores – Ecosystems • Fragmentation within platforms, including – Physical device differences – Version incompatibilities – Vendor customizations • And this market is moving very fast – new things are introduced all the time
  • 10. Developing for multiple mobile platformsIBM Worklight Open, cost-effective, cross-platform mobile app development App development using App delivery in variety of Compatible with prominent native and/or familiar web forms: HTML5 libraries and tools: technologies: • Mobile Web app • HTML5 • Hybrid app • Native • CSS3 • JavaScript
  • 11. IBM Worklight mobile platform overview Worklight Studio The most complete, extensible development environment with maximum code reuse and per-device optimization Worklight Server Mobile middleware offering unified push notifications, version management, security and integration Worklight Runtime Components Extensive libraries and client APIs that expose and interface ← with native device functionality and the Worklight Server Worklight Console A web-based console for real-time analytics and control of your mobile apps and infrastructure
  • 12. Security Features Protecting data on the Enforcing security device updates Secure Encrypted Offline App Compatibility Remote challenge- offline cache authentication authenticity with jailbreak disable Direct update response on testing detection libs startup SSL with Mobile Auth Data Proven Device server Code platform as a integration protection platform provisioning identity protection trust factor framework realms security verification Streamlining Providing robust Application Corporate security authentication and Security processes authorization
  • 13. Mobile development is more than just coding ... Analysis Phase Build Phase Deploy Phase Line Development Operations/ of Business Team Manufacturing Team Design Implement Run Analyze Manage Test Monitor Optimize Governance and Best PracticesCoding is just one component of the mobile application development lifecycle
  • 14. Challenge 2: Design and functional quality are both critical tosuccess• Customers demand good user experience• Customer facing (B2C) applications – ‘Face of the Business’ – Engage customer personally and drive loyalty – User experience is key to brand perception• Employee facing (B2E) applications – Increase worker productivity – Speed decision making and action – Poor user experience compromises investment
  • 15. Focus on user experience first to achieve outside-in design Collaborate as a team using comments and annotations Get feedback from non- technical stakeholders
  • 16. Web App Testing Challenge – Last 6 YearsMarket 6 years 2005-2011 Browsers Product Version Product Release timeline 20 20 20 20 20 05 11 07 06 08 6 years v
  • 17. Mobile App Testing Challenge – 1 Year Product Version Product Version Product Version Product Version Product Version Product Version Product Version Product VersionMarket 1 year 2011 V2.3 V2.3.3 V3 V2.3.4 V3.1 V2.3.5 V3.2 V2.3.7 V2.3.6 Android V4 Product Version Product Release timeline Ja De Ju M Se n ar c n p v 1 year - 2011
  • 18. Testing the end-to-end mobile solution Client Tier Devices Middle Tier Server Back-end Data & Services Testing involves much more than just the mobile front-end
  • 19. Challenge 3: Integrating with existing systems• Mobile applications need to connect to enterprise back-end IBM CONFIDENTIAL data and services• Existing programs and services may need to be modified for the mobile app• Multiple skills will be involved, responsible for different parts of the mobile application
  • 20. Rational IDEs with IBM WorklightDesign, code, build, test, and deploy mobile apps that run on a wide variety ofmobile platforms; extend existing back-end services and data to mobile apps Integrated multi-platform development environments Construct, debug, and test mobile Refactor and extend existing logic on UIs enterprise platforms (System z, Power) as mobile-consumable services IBM Worklight 5.0 is now included in the following IDEs (for development purposes only): Rational Developer for zEnterprise v8.5 Rational Application Developer v8.5 Rational Developer for Power Systems v8.5 Rational Software Architect v8.5
  • 21. Challenge 4: Meeting tight time-to-market requirementsMobile is pushing traditional delivery approaches to the breaking point Mobile Apps Desktop AppsTime-to- Weeks to Months Months to YearsmarketFrequency Once every several 12-18 month cyclesof updates weeks
  • 22. Mobile software development is a team sport Software development involves a team of people with diverse skills using different tools – Design, development, test, operations, etc. Tools can make or break collaboration – Fragmented tools create silos – Integrated tools break down barriers Effective development depends on … – Defined goals – Transparency of progress and quality trends – Aligning teams across the entire application development lifecycle
  • 23. Factors affecting project velocity Test Test Script Planning Creation Project Vision App Design Functional System Deployment Bus. objectives UI Design Testing Testing Code Build construction Unit Testing 1st 2nd Gap GapDesign Develop Test DeployThere are 2 key gaps affecting project velocity:• Gap 1: Early in project definition – Results in rework due to miscommunication of app specification – Slows progress due to hand-off errors and confusion between team members• Gap 2: Later in project delivery – Lack of automated deployment and validation – Mismatches between app requirements and available production infrastructure
  • 24. Example Value of Integration - Mobile and ALM Mobile devices & emulators Studio Team Concert Client DeveloperRTC build engine and Worklight mobile build SCM Team Build utility provide a controlled repository build environment for of apps mobile apps – both native and hybrid executables, sources logfiles Builder RIM App stores Android iOS SDK SDK SDK Mobile build server farm
  • 25. Worklight Application Center 25
  • 26. IBM delivers a scalable and incrementally deployable mobilesolution Delivering high quality apps that engage users Developing for multiple mobile platforms and meet business objectivesCross-platform mobile web and Linkage and traceability acrosshybrid app development, test, and all phases of developmentbuild UI sketching and storyboardingManage plans, tasks, code, builds Test plan optimization andfrom a common development management and integrationworkbench with mobile “Device-clouds”Agile planning Portfolio management Integrating with enterprise systems Meeting accelerated time to market requirementsIntegrate Worklight Studio with the Automate and manageRational IDEs to create a continuous, end-to-end build andcomprehensive IDE for all parts of deployment process with RTCthe app (UI, mid tier, back-end) Deploy to private dev/test appExtend enterprise assets as Reduce cycle times by aligningmobile-consumable services and dev and operations teamsconnect via Worklight adapters
  • 27. Legal Disclaimer • © IBM Corporation 2011. All Rights Reserved. • The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. • References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. • If the text contains performance statistics or references to benchmarks, insert the following language; otherwise delete: Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the users job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. • If the text includes any customer examples, please confirm we have prior written approval from such customer and insert the following language; otherwise delete: All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. • Please review text for proper trademark attribution of IBM products. At first use, each product name must be the full name and include appropriate trademark symbols (e.g., IBM Lotus® Sametime® Unyte™). Subsequent references can drop “IBM” but should include the proper branding (e.g., Lotus Sametime Gateway, or WebSphere Application Server). Please refer to for guidance on which trademarks require the ® or ™ symbol. Do not use abbreviations for IBM product names in your presentation. All product names must be used as adjectives rather than nouns. Please list all of the trademarks that you use in your presentation as follows; delete any not included in your presentation. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both. • If you reference Adobe® in the text, please mark the first use and include the following; otherwise delete: Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. • If you reference Java™ in the text, please mark the first use and include the following; otherwise delete: Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. • If you reference Microsoft® and/or Windows® in the text, please mark the first use and include the following, as applicable; otherwise delete: Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. • If you reference Intel® and/or any of the following Intel products in the text, please mark the first use and include those that you use as follows; otherwise delete: Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. • If you reference UNIX® in the text, please mark the first use and include the following; otherwise delete: UNIX is a registered trademark of The Open Group in the United States and other countries. • If you reference Linux® in your presentation, please mark the first use and include the following; otherwise delete: Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. • If the text/graphics include screenshots, no actual IBM employee names may be used (even your own), if your screenshots include fictitious company names (e.g., Renovations, Zeta Bank, Acme) please update and insert the following; otherwise delete: All references to [insert fictitious company name] refer to a fictitious company and are used for illustration purposes only.