Codestrong 2012 breakout session mobile platform and infrastructure

  • View

  • Download

Embed Size (px)

Text of Codestrong 2012 breakout session mobile platform and infrastructure

  • 1.Mobile Matters: Technologies toEnable Mobile First EnterprisesMichael King Director of Enterprise StrategyAppcelerator @mobiledatamike

2. Mobile Matters:Technologies toEnable Mobile FirstEnterprises 3. Agenda State of the market Technologies to support mobile-first enterprises A lifecycle approach Creating an app factory Requirements for a next generation mobile platform 4. State of the marketMassive device fragmentation, firstwith Android, now beginning withAppleEnterprises has no control over thedevices their customer apps will beconsumed on, and with BYOD, lesscontrol for employee appsNo end to fragmentation in site 5. Native Development WEB Separate development teamsiPhone Different development languages Different development SAP environments Android Impossible to align delivery schedulesOracle Each App must be built 3-4 times BB No reusable componentsNo way to enforce standards ofSocialdesign or governanceToo costly, too timeWindows 8 consuming, impossible to sustain 6. HTML5 As the Cure?WEBSAPHTML 5 +CSS Oracle SocialGives you a write once, run poorly everywhere experience 7. Traditional Mobile Enterprise Application Platform ArchitectureA new market requires a new approach 8. What Weve Heard From Our ClientsChallenges:We require visibility across the entire Mobile Application Lifecycle:Plan, Build/connect, Test, Release/Manage, and AnalyzeWe require connections to multiple backend systems, public networks,web services and social networksI cant train people on all of the studios and development languages required,and my outsourcing partner doesnt have the developers/skills I needI have islands of information about my apps, some in the LOBs, some in theapps teams, some in testing, and no way to manage all of my appsThe market and LOBs demand rapid application response, I need to enforcegovernance, branding standards, and consistent connection methods 9. Agenda State of the market Technologies to support mobile-first enterprises A lifecycle approach Creating an app factory Requirements for a next generation mobile platform 10. Technologies For Mobile-First Compelling UI/IX Mobile Device management/Mobile application management Next generation mobile app platforms 11. Compelling UI/UX A well designed, compelling app is easier to learn and easier to use, everyday If the app focuses on UI and device specific interactions, it will achieve:Lower support costsReduce training timeAchieve higher adoptionAchieve application goals more rapidly BYOD (Bring your Own Device) evolves quickly to Bring Your Own App (BYOA) forcing the Enterprise to focus on application design and user centric interfaces even for employee facing apps! 12. MDM vs MAM MDM: Mobile Device Management: A device centric security and management capability, to encrypt, mange and wipe the entire device MAM: Mobile Application Management: An application or data centric method of distribution and securing the application or solely the data that application uses Both may be appropriate, depending on regulations, device ownership, application requirements and security posture Can be purchased in a traditional client server model or hosted/cloud based Costs range from 3-4 dollars per device per month to 400-500 per device for a perpetual license 13. Next Generation Platform Its not about any device, its about all of them, at anytime Consistency of user state across devices, maintain the applications state,with unique device-specific functions, views, and look/feel Data sources are both owned and public; ERP, CRM, Social, Web, Maps Sharing of information across applications via the cloud Information flows and permissions are infinite, based on developer requirements 14. Benefits of a Platform Approach Transform PhaseBenefits outweigh Acceleratecost of platformPhaseExplore PhaseZero Apps Number of Applications 15. Agenda State of the market Technologies to support mobile-first enterprises A lifecycle approach Creating an app factory Requirements for a next generation mobile platform 16. Mobile Application LifecycleAnalyzePlanManage/ Build/CoReleasennectTest 17. Mobile App Lifecycle Execs andBusiness App Owners Analysts, DevelAnalyzePlan opers Manage/ Build/Co Releasennect Release and Server and securityEnterprise managers Test Developers Functional and performance testers 18. Mobile Application LifecycleCEO/GM of What are my customers doing with these mobileLoBbanking apps? LoB AppShow me where all of the all of the apps with haveOwner/VPApps/ CMO for our banking customers stand in developmentand testingDevelopment Lets see how the latest increase in productivity ofManagement my Titanium team affected the testing queue Corporate I need to know where the app I was working on is Developer crashing? 19. Mobile Application LifecycleCEO How many apps do we have? What are theydoing for us?What are the employee apps using, in terms of CIOresources and modules?I need to know where every app in our estate Mobility CoE / VP stands, in terms of development, testing, and Mobility productionCorporate What happened to the expense managementDeveloper app I submitted to testing? 20. Agenda State of the market Technologies to support mobile-first enterprises A lifecycle approach Creating an app factory Requirements for a next generation mobile platform 21. Application factory While everyone starts with oneapp As enterprise builds multipleapplications, standardizationenables repeatability The enterprise will quickly move todisposable applications Each application running on a newdevice class is a new application 22. Application Components Branded elements(logos, colors, graphicalelements)Connection to CRM systemLogin/password adminEncryption of data in transit Developer then stitches Connection to twitter/facebook the elements of the mobile application together 23. Next Generation Platform Visibility across the entire Mobile ApplicationRequirements: Lifecycle Build, test, deploy, manage, analyze Vibrant, involved ecosystem of SIs anddevelopers to extend the platform Standards-based development language andstudio Ability to integrate best of breed tools(MAM, Testing, Bug Reporting) Modular capabilities to componentize appelements for maximum reusability, andenforcement of standards 24. AppceleratorMobile Client Development with Titanium Appcelerator Mobile Cloud Platform APICloud Storage API Services Services Push(Data & Services(backupEngineFile))Custom Connector LayerExamplesCustom/Legacy 25. MEAP vs Next Generation Next Generation Advantages Scalability VS Single developmentenvironment Client side Server side Lower Cost (less upfront Mobile Client Development with Titaniuminvestment) More Deployment Appcelerator Mobile Cloud Platform options (VPC, BehindCloud APIServic es APIServicPush Servic esStorage(DataFirewall)Engines(back& File)e up)Custom Connector Layer 26. Rating Development Options Traditional Native Traditional MEAP Next Generation ApplicationPlatformsMobile Application ApproachesPlatformsEnforceableN/AYes, limited toYes, fully extensiblestandards for supported optionsthrough theapplication elements ecosystemNative, Hybrid and N/ANo, native orYesHTML app supportwrapperOpen architecture forN/ANo, closed systems Yesintegration of best ofbreedEcosystem of SI, Yes, depending onSIs but fewOpen ecosystemISVs and developersOS developers/ISVsStandards-based, N/AProprietary, In the samecustomizablesignificant additional developmentbackend connectorscosts 27. Mobile Maturity Model 28. Conclusions Technologies for the mobile first enterpriseare: MDM/MAM Next Generation Platforms UI/UX Application factory Approaches will enable ITto react quickly to the requests from the LOBs Next generation platforms must enablevisibility across the App lifecycle, regardlessof role Mobile maturity goals will dictate the pace oftechnology investments