Apps & API Monitoring
Apigee
@apigee
Ole Lensmar
@olensmar
Alan Ho
@karlunho
SmartBear
@SmartBear
Building a 5-Star Reputation for your Apps
groups.google.com/group/api-craft
groups.google.com/group/app-craft
youtube.com/apigee
slideshare.net/apigee
@olensmar
Ole Lensmar
@karlunho
Alan Ho
@SmartBear @Apigee
During webcast - participate on twitter hastag #5starapp
Agenda
• Why (Web) API performance matters
• How can you avoid performance issues?
• Synthetic Transaction monitoring
• Real User monitoring
• Recap pros/cons of different techniques
• Questions
What matters to the
user?
900,000 apps & growing
Performance Matters
• Poor reviews skew your
overall app ratings
• Majority of Poor Reviews
Occurred in first 24 hours
• Customers do not tolerate
software Errors
• Combination of App &
API problems
• Fixing Problems without
trace logs is difficult
Don’t crash
Don’t give me errors
Don’t slow me down
Return on Features vs. Performance
Benefit
Application Maturity
Inflection
How can you avoid
performance issues?
API performance = app performance
Indirect vs. Direct API Integration
3rd$party$APIs
Mobile$
Applica4on
API$Backend
Direct$Integra4on
Indirect$
Integra4on
(Mobile$Carrier)
3rd$party$APIs
Mobile$
Applica4on
API$Backend
Direct$Integra4on
Indirect$
Integra4on
(Mobile$Carrier)
Synthe4c$Monitoring
Func4onal$
Monitoring
Func4onal$and$Performance
Monitoring
Synthetic Monitoring
• Functional Consistency
• Perf. Consistency
• Proactive Error Detection
3rd$party$APIs
Mobile$
Applica4on
API$Backend
Direct$Integra4on
Indirect$
Integra4on
(Mobile$Carrier)
Synthe4c$Monitoring
Func4onal$
Monitoring
Func4onal$and$Performance
Monitoring
Real$User$Monitoring
Real User Monitoring
• API Errors
• API Performance
• Variation of Devices /
Networks
Demo
3rd party APIs
Mobile Application
API Backend
Direct Integration
Indirect
Integration
(Mobile Carrier)
AlertSite for API Monitoring
Functional
Monitoring
Functional and Performance
Monitoring
(Mobile Carrier)
Apigee Mobile AnalyticsReal User Monitoring
Synthetic Monitoring
Pros Cons
Real User
Monitoring
• Capture Real User
problems
• Exercise real devices and
networks
• Correlate with errors &
abandonment
• Need critical mass of traffic for
each API monitored
• Need to instrument your code
• Potential Bandwidth / Battery
issues
Synthetic
Transaction
Monitoring
• Can monitor all APIs all
the time
• Doesn’t require
instrumentation of app
• Can reuse existing test
assets from Dev & QA
• Doesn’t simulate real users /
devices / networks
• Need to setup and maintain
the monitors
• Cannot tell you the end
behavior of the app
Use both techniques!
• Reduce effect of cons of both techniques
• Use RUM traffic to create tests for Synthetic
Transaction Monitoring
• Correlate STM failures to usage in RUM
In Summary . . .
 Mobile app experience depends on API performance
 Success depends on meeting users’ performance
expectations
 Use multiple techniques for monitoring your app
Questions
THANK YOU
Questions and ideas to:
@olensmar
@karlunho
groups.google.com/group/api-craft
groups.google.com/group/app-craft

App & API Monitoring: Building a 5-Star Reputation for your Apps

Editor's Notes

  • #2 Creative Commons Attribution-Share Alike 3.0 United States License
  • #10 Main Point: Once you see bad reviews its too lateBusiness Points:Bad reviews impede your success and are bad for your brandTech Points:Better to be proactive and fix issues before having to be reactive to bad reviewsSequential Story: Illustrate specifically how performance and stability effect a reviewScript:When you look at app ratings you can see the confirmation of these findings. A bad review like the one here shows how a problem early in the apps release cycle can skew results for a long time. This shows the importance of finding and fixing issues related to stability and performance before the app is released as even within 24 hours the negative momentum built by bad reviews can be difficult to overcome. As expected, customers don’t like errors and problems with apps and the review comments will tell you all about the frustration they experience.
  • #11 Main Point: Once you see bad reviews its too lateBusiness Points:Bad reviews impede your success and are bad for your brandTech Points:Better to be proactive and fix issues before having to be reactive to bad reviewsSequential Story: Illustrate specifically how performance and stability effect a reviewScript:When you look at app ratings you can see the confirmation of these findings. A bad review like the one here shows how a problem early in the apps release cycle can skew results for a long time. This shows the importance of finding and fixing issues related to stability and performance before the app is released as even within 24 hours the negative momentum built by bad reviews can be difficult to overcome. As expected, customers don’t like errors and problems with apps and the review comments will tell you all about the frustration they experience.