Codestrong 2012 breakout session leveraging titanium as part of your mobile app lifecycle
Download as PPTX, PDF0 likes702 views
This document discusses the lifecycle approach to mobile application development. It outlines the key stages in a mobile app lifecycle: plan, build/connect, test, manage/release, and analyze. Each stage represents important steps, from requirements gathering and design in the plan stage to distribution, management, and analysis of usage in later stages. The document notes that as apps and operating systems increase in number, managing the lifecycle of mobile applications across their development and use has become more complex, requiring improved processes and visibility across roles.
Codestrong 2012 breakout session leveraging titanium as part of your mobile app lifecycle
- 1. Lifecycle Approach to Application Development Michael King Director Of Enterprise Strategy mking@appcelerator,com MobileDataMike
- 2. State of the Market Today • X number of Apps X Y number of screens X Z number of Operating systems = 1000s of apps • Connections to 100s of information sources, all with different permissions, data formats, security requirements…
- 3. what customers say… • “People think that a mobile app is small, simple and similar to a web/desktop app. They’ve realized it’s not.” • “With one app, we can manage the process. The problem is when we have more apps.” • “Loosely knit group of developers, islands of information.” • “Our testing is completely manual.” • “No way to follow what is happening to an app after release.”
- 4. Test, Manage, Analyze Connect Lifecycle and a Mobile Center of Build Cloud Services Excellence Titanium Market evolution and product maturity
- 5. Mobile App Lifecycle Analyze Plan Manage/R Analyze elease Manage/Dep Build/Connec Test loy Plant Build/Conne Test ct
- 6. Plan This stage represents everything that is done before the developer even turns on a monitor • Requirements Gathering • Resource planning • Wireframes
- 7. Build/Connect This stage represents all of the development (client and server) required to produce the app • Client side development • Multi platform • Multi architecture • Server side development • Traditional • Cloud based • Application factory approaches • Modularity • Libraries
- 8. Build/Connect (cont) This stage represents the connections required for the application to send and receive data • Connections to data sources • Enterprise • Public • Social • Authentication • Cascading permissions • Cloud vs Traditional
- 9. Test Test includes all of the tests required to ensure the application’s performance meets the requirements for stage one • Emulator testing • Functional and unit testing • Any additional on-device testing • Live network and source testing
- 10. Demo
- 11. Manage/Release • This is the management and distribution of the mobile app to the right users, it may include: • App Stores (iTunes, Google Play) deployments • Secure distribution of the app to employees • Updating/removal of the app • Security and management of application data
- 12. Analyze This step includes any analysis of the application and user behavior • Analyze application behavior • In relation to app usage • In relation to outside impacts • Analyze user behavior • Opportunities for improvement/next versions of the applications
- 13. Application Components Branded elements (logos, colors, graphical elements) Connection to CRM system Login/password admin Encryption of data in transit Developer then ‘stitches’ Connection to twitter/facebook the elements of the mobile application together
- 14. Who Cares About Mobile? Indie Dev Enterprise LoB Central IT Break the glass, get it done scale it, put process in place CEO/GM of CEO LoB Indie Developer LoB App CIO Owner/VP Apps/ CMO Mobility CoE / Development VP Mobility Management IT Ops Corporate Corporate … ….. Developer Developer Technical company confidential 14 Budget owner influencer
- 15. Mobile Application Lifecycle CEO/GM of “What are my customers doing with these mobile LoB banking apps?” LoB App “Show me where all of the all of the apps with Owner/VP Apps/ CMO have for our banking customers stand in development and testing” Development “Lets see how the latest increase in productivity of Management my Titanium team affected the testing queue” Corporate “I need to know where the app I was working on is Developer crashing?”
- 16. Mobile Application Lifecycle CEO “How many apps do we have? What are they doing for us?” “What are the employee apps using, in terms of CIO resources and modules?” “I need to know where every app in our estate Mobility CoE / VP stands, in terms of development, testing, and Mobility production” Corporate “What happened to the expense management Developer app I submitted to testing?”
- 17. Next-Generation Application Lifecycle Roles LOB App Owners and Release and Executives security managers (IT) Business Analysts (LOB) Functional and performance testers/ developers LOB and IT (IT or LOB) developers
- 18. Execs and Business App Analyze Plan Analysts, De Owners velopers Manage/ Build/Co Deploy nnect Release and Server and security Enterprise managers Test Developers Functional and performance testers Mobile App Lifecycle Partipants
- 19. Conclusions Plan • Lifecycle approaches can enable rapid Build/Co iteration of apps and constant Analyze nnect improvement of experiences • Role based views of apps in the life Release Test cycle are important as the app estate Manage grows • Testing visibility remains difficult across groups • Each participant in the life cycle has separate requirements for information
- 20. Thank you
Editor's Notes
- #4: Simpler, easily readablecodeReusablewidgetsReduces time from zero-to-app WritelesscodeCreatescalableappsLowerprobability of runtime errors
- #7: Simpler, easily readablecodeReusablewidgetsReduces time from zero-to-app WritelesscodeCreatescalableappsLowerprobability of runtime errors
- #8: Simpler, easily readablecodeReusablewidgetsReduces time from zero-to-app WritelesscodeCreatescalableappsLowerprobability of runtime errors
- #9: Simpler, easily readablecodeReusablewidgetsReduces time from zero-to-app WritelesscodeCreatescalableappsLowerprobability of runtime errors
- #10: Simpler, easily readablecodeReusablewidgetsReduces time from zero-to-app WritelesscodeCreatescalableappsLowerprobability of runtime errors
- #11: Industry leading capture playbackNo strings, no jail breaking and running on Wi Fi carrier or networksFunctional validation for every action, gesture, image, outputIntegrated with Ti Studio
- #12: Simpler, easily readablecodeReusablewidgetsReduces time from zero-to-app WritelesscodeCreatescalableappsLowerprobability of runtime errors
- #13: Simpler, easily readablecodeReusablewidgetsReduces time from zero-to-app WritelesscodeCreatescalableappsLowerprobability of runtime errors
- #15: Given the target uadinece, here is who we sell to
- #20: Simpler, easily readablecodeReusablewidgetsReduces time from zero-to-app WritelesscodeCreatescalableappsLowerprobability of runtime errors
- #21: Simpler, easily readablecodeReusablewidgetsReduces time from zero-to-app WritelesscodeCreatescalableappsLowerprobability of runtime errors