Uploaded byApteligent
Mobile DevOps
Mobile apps have unique challenges compared to web applications due to factors like fragmented devices, lack of communication from users, and the importance of reputation in app stores. To address these challenges, mobile DevOps integrates mobile app development with monitoring to ensure high performance, reliability and responsiveness. This involves monitoring APIs, SDKs and other dependencies for issues like errors, latency and crashes that degrade the user experience. The goal of mobile DevOps is to take feedback from monitoring to continuously improve the overall mobile app experience.
Mobile DevOps
- 2. Mobile DevOps Mobile Apps+ APIs = Mobile DevOps Alex Gaber // QCon New York 2014
- 3. Mobile Apps area new paradigm of application development
- 4. How did we gethere?
- 5. When was thelast time you bought a box of software?
- 6. Software Application History 1990’s – Thin / Thick Client Software – Client – Server application architectures  Waterfall Methodology – Slow release cycles
- 7.
- 8.  Continuous Integration Monitoring vs. Testing  Browser access and CDNs  Agile / Iterative / Scrum Web Application Development
- 9.  Single CodeBase  REST APIs enable app developers to mash multiple services together Web Application Development
- 10.
- 11. 2011 Before Packaged Software Fadesinto History…
- 12.  40k AppsAdded per Month Mobile Application Platforms Continue To Grow
- 13.  Multiple CodeBases  API connectivity + persistence becomes an issue due to 2G / 3G / 4G Mobile Application Development
- 14. Mobile App Devicesare Fragmented
- 15.  New Challenges More Difficult Mobile Application Development
- 16.
- 18. Applications Crash, butUsers Already Paid
- 19. Was it Windowsthat crashed or was it the application?
- 20. When was thelast time you clicked “Send”??
- 21. Web Application Crash Web404 error – Do you notify the site?
- 22.
- 23. Mobile App UsersCannot Communicate Easily
- 24.
- 25. For the FirstTime, User Experience has a Feedback Loop
- 26. Do end-users wantto help the app developer? • Mobile App Stores created developer reputation / feedback loop
- 27. What Do UsersDo When the App is Slow? 100%Did not do anything 100%Uninstall the App 100%Told a friend in person 100%Contacted support or told the vendor 100%Left a negative review on the app store 100%Shared the experience via social media Source: Crittercism end-user survey Q4’2013
- 28. “If everything istested, we don’t need to monitor” TRUE or FALSE?
- 29. What cannot betested prior to launch? Failure of shopping cart check-outs, referrals, etc. Transaction Errors HTTP Errors like 404’s, Errors accessing Cloud Services API & Network Errors Slow performance, High latenciesUnresponsive Apps Downtime due to app crashes Apps Crashes & Exceptions Performance issues due to geographyLocation
- 30. Mobile App Performance management(mAPM) intertwines mobile app development with DevOps
- 31. Comparing Web toMobile App Development > 99.9% UptimeWeb Applications expect Mobile Applications achieve < 99% Uptime
- 32. BEWARE of RESTAPIs causing sleepy mobile apps! z z z z
- 33. Mobile App APICalls  18% of API calls from mobile apps have an error rate of over 5% ď€ UNACCEPTABLE  9% of APIs in mobile apps have greater than 1 Second response ď€ UNACCEPTABLE
- 34. BEWARE of SDKsslowing down your Mobile Apps! Free Version Paid Version Uses a 3rd Party Mobile Ad SDK ~ 3% Crash Rate No Ads, No 3rd Party Mobile Ad SDK < 1% Crash Rate Sample Mobile App Scenario
- 35. Mobile Apps HaveLots of 3rd Party Dependencies 3rd Party APIs and SDKs can slow down your Mobile App Mobile Security SDKs Mobile Ad SDKs
- 36. Speaking of SDKsin your Mobile Apps…  The average mobile application consumes 6 different APIs / web services (Crittercism Mobile Benchmark Report 2014) – Mobile AD SDKs – Mobile Security SDKs – Mobile Analytics SDKs – Mobile Monitoring SDKs – RESTful APIs
- 37. • Mobile AppDevelopers need to monitor the APIs and SDKs that their mobile app is consuming • Trust but Verify Teamwork -> Mobile App Developers DevOps Team Mobile DevOps Optimizing Web Service API Integration to Mobile Apps
- 38. Optimizing Web ServiceAPI Integration to Mobile Apps  Never make the UI wait for an API – Decouple API from UI – Pre-fetch when possible  Cache data in local storage or SQLlite  Always test Apps in Offline Mode  Monitor from Mobile App as Endpoint – Web server monitoring is not enough – Consider Mobile Tax of 2G / 3G / 4G
- 39. What Does MobileDevOps Look Like?
- 40. One Endpoint hasa 3.0 second roundtrip What Does Mobile DevOps Look Like?
- 41. Adjust APIs basedon geographical performance What Does Mobile DevOps Look Like?
- 42. Take Feedback from MobileDevOps to improve your overall mobile app user experience.
- 44. Thank You Alex Gaber@intalex Crittercism @Crittercism