Discover 67 articles on Monitoring in mobile performance
Showing 20 of 67 articles (Page 3 of 4)
Booking.com discovered that standard performance monitoring tools from Apple, Google, and Firebase couldn't meet their needs. So they built their own—and just open-sourced it.
The Paytm Editorial Team reveals how they measure the real cost of user friction: tracking payment flows down to the millisecond, excluding network delays that mask app performance issues.
Angus Croll from Netflix reveals how his team slashed false performance alerts by 90% while catching more real regressions. The secret? They stopped using static thresholds entirely.
Karthik Jayasurya from Nextdoor reveals how they transformed notifications from random spam into personalized updates that neighbors actually want. The result? A 40% jump in engagement without sending more mess...
Victor Oliveira from Mercado Libre reveals a harsh truth: 53% of users uninstall apps due to performance issues. With 4.5 billion active Android and iOS devices worldwide, each performing differently, mobile pe...
Tokopedia built an automated performance testing pipeline that catches regressions before they hit production. Here's how they measure every build, every night.
Tokopedia's Android team achieved a 40% improvement in app start time and page load speed. Here's the systematic approach that got them there.
DoorDash's OpenTelemetry adoption hit a wall: 72% CPU utilization versus 56% without tracing. That's a costly tax for observability.
"My app is slow" - every engineer's nightmare. Slack's mobile team was tired of hitting dead ends when debugging performance issues.
Pinterest sends 1 million CI build events to Honeycomb daily. Here's how they turned that data into a competitive advantage for mobile development.
Walmart's engineering team reveals how observability tracing transformed their CI/CD pipeline reliability. The secret? Treating data requests like package tracking.
Jingwei Hao from Lyft reveals how real-time stats APIs caught a production crash spike at 9:55am, enabling engineers to ship a hotfix before most users even noticed the problem.
Fajar Ulin Nuha from Tokopedia reveals how their 50+ Android engineers manage a codebase that changes so dramatically every single week that assumptions become dangerous. Their solution? Become data-driven deve...
Hendry Setiadi from Tokopedia reveals how they built a custom logging system that catches production issues before users even notice. Firebase Crashlytics is great, but what if you need more?
Slack processes 8.5 billion spans daily, but their tracing system looks nothing like traditional distributed tracing. Here's why they rebuilt it from scratch.
Marianna Budnikova from Dropbox reveals why your mobile analytics are probably lying to you. And it's costing you two weeks every time you get it wrong.
Mercari's iOS team needed to monitor performance without building an entire infrastructure team. Here's how they did it in under a week.
Maya Reddy from Pinterest reveals how their team eliminated last-minute P1 bugs by automating ad metrics testing. The shift from bi-weekly manual QA to continuous integration transformed their release confidenc...
Julio Zynger from SoundCloud reveals how they ship mobile releases every two weeks without breaking things. Their secret? A release train model that turns chaos into predictability.
Meta's engineers were spending days or months debugging performance issues they couldn't reproduce in their device labs. Sound familiar?