Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
Monitoring Your Mobile Apps in the Wild
Search
Greg Shackles
December 02, 2017
Technology
130
1
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Monitoring Your Mobile Apps in the Wild
Delivered at CodeCampSDQ
Greg Shackles
December 02, 2017
More Decks by Greg Shackles
See All by Greg Shackles
Building Modern Services with .NET Core 3 and gRPC
gshackles
0
220
Observability-Driven Development: What DevOps is Really About
gshackles
1
350
Building Scalable Applications with the Actor Model
gshackles
0
700
Creating a Voice-Driven TV Remote with Azure and Alexa
gshackles
0
170
Build 2017 Recap for Xamarin Developers
gshackles
0
160
Going Serverless: Event-Driven Architecture Without The Infrastructure
gshackles
0
240
Evolve 2016 Redux
gshackles
0
170
Instrumenting Your Mobile Monitoring Strategy
gshackles
0
4.8k
What's New in C# 6?
gshackles
1
270
Other Decks in Technology
See All in Technology
Claude の新機能を、 出た日に触って社内に届けるまで
rfdnxbro
1
190
初海外で注意すべきこと12選!!!安全快適なre:invent生活にするために
yuuuuuuu168
1
180
実体験から学ぶ分析エージェントの開発と運⽤
recruitengineers
PRO
8
2.4k
ウォンテッドリーの最近のプロダクトと技術の紹介
stomk
0
120
Rust で関数型ドメインモデリング
takonda
0
140
WasmをRustにする
sansantech
PRO
0
260
Persisting Massive Data with Rails ~Designing for 60 billion rows, and fighting the bottlenecks~ Railsで挑む大量データ永続化 〜600億件を永続化するための設計とボトルネックとの戦い〜
occhi
0
730
分析の民主化を支えるメタデータ整備の実践
kakehashi
PRO
4
1.4k
Railsで挑む大量データ永続化 〜600億件を永続化するための設計とボトルネックとの戦い〜
occhi
1
630
AIがコードを書く時代に、エンジニアは何で自分の価値を証明するのか / In an era where AI writes code how do engineers prove their value
carta_engineering
3
1.1k
OptunaHub: ブラックボックス最適化のためのプラットフォーム
pfn
PRO
0
140
Refining Active Record
shugo
0
160
Featured
See All Featured
No one is an island. Learnings from fostering a developers community.
thoeni
21
3.9k
How Software Deployment tools have changed in the past 20 years
geshan
2
35k
Site-Speed That Sticks
csswizardry
13
1.6k
The Impact of AI in SEO - AI Overviews June 2024 Edition
aleyda
6
1.2k
GraphQLの誤解/rethinking-graphql
sonatard
75
12k
Color Theory Basics | Prateek | Gurzu
gurzu
1
490
Exploring anti-patterns in Rails
aemeredith
4
540
brightonSEO & MeasureFest 2025 - Winning Strategies for Black Friday CRO & PPC - Christian Goodrich
cargoodrich
3
870
Future Trends and Review - Lecture 12 - Web Technologies (1019888BNR)
signer
PRO
0
3.8k
Building Adaptive Systems
keathley
44
3.2k
VelocityConf: Rendering Performance Case Studies
addyosmani
331
25k
Leading Effective Engineering Teams in the AI Era
addyosmani
9
2.7k
Transcript
Monitoring Your Mobile Apps in the Wild Greg Shackles Principal
Engineer, Olo @gshackles
[email protected]
github.com/gshackles
None
None
None
None
None
None
None
What to measure?
Standard Issue Metrics Screen hits OS version App version Device
type Session duration
What else can we look at?
How long are your users waiting?
60% Source: Forrester, November 2014 rate performance and response time
as their primary app expectation, ahead of features and functionality
Network Request duration Request success rate Request frequency Bandwidth usage
Network types
Performance Time to interactivity Memory usage Battery usage Database call
duration Cache hits/misses
How is the app being used? Beyond Performance
Behavior Define your own meaningful metrics Time to complete critical
flows Example: cart abandonment rate In-app actions
Real Insights Are they using that new feature you love?
Safe to remove old functionality? Improvements/regressions across releases A/B testing
How to monitor?
None
Let’s Code
Questions? Greg Shackles Principal Engineer, Olo @gshackles
[email protected]
github.com/gshackles