×
Copy
Open
Link
Embed
Share
Beginning
This slide
Copy link URL
Copy link URL
Copy iframe embed code
Copy iframe embed code
Copy javascript embed code
Copy javascript embed code
Share
Tweet
Share
Tweet
Slide 1
Slide 1 text
Instrumenting Your Mobile Monitoring Strategy Greg Shackles Principal Engineer, Olo @gshackles
[email protected]
github.com/gshackles
Slide 2
Slide 2 text
No content
Slide 3
Slide 3 text
No content
Slide 4
Slide 4 text
No content
Slide 5
Slide 5 text
No content
Slide 6
Slide 6 text
No content
Slide 7
Slide 7 text
No content
Slide 8
Slide 8 text
What to measure?
Slide 9
Slide 9 text
Standard Issue Metrics Screen hits OS version App version Device type Session duration
Slide 10
Slide 10 text
What else can we look at?
Slide 11
Slide 11 text
How long are your users waiting?
Slide 12
Slide 12 text
60% Source: Forrester, November 2014 rate performance and response time as their primary app expectation, ahead of features and functionality
Slide 13
Slide 13 text
Network Request duration Request success rate Request frequency Bandwidth usage Network types
Slide 14
Slide 14 text
Performance Time to interactivity Memory usage Battery usage Database call duration Cache hits/misses
Slide 15
Slide 15 text
How is the app being used? Beyond Performance
Slide 16
Slide 16 text
Behavior Define your own meaningful metrics Time to complete critical flows Example: cart abandonment rate In-app actions
Slide 17
Slide 17 text
Real Insights Are they using that new feature you love? Safe to remove old functionality? Improvements/regressions across releases A/B testing
Slide 18
Slide 18 text
How to monitor?
Slide 19
Slide 19 text
HockeyApp
Slide 20
Slide 20 text
Let’s Code
Slide 21
Slide 21 text
Questions? Greg Shackles Principal Engineer, Olo @gshackles
[email protected]
github.com/gshackles