51 articles on Monitoring for Android performance
Showing 20 of 51 articles (Page 1 of 3)
Snapchat treats performance as a core product feature, not just a requirement. Their custom tracing system catches regressions that off-the-shelf tools completely miss.
WHOOP's Android team turned a Google Play compliance warning into a masterclass in battery optimization. Their excessive wake lock sessions dropped from 15% to under 1% in just 30 days.
Ever tried debugging a mobile app crash without knowing what the user actually did? You're flying blind.
Google Play is about to start penalizing apps that drain your users' batteries. Starting March 2026, excessive wake lock usage could get your app buried in search results or flagged with a warning label.
Google's Android team just dropped a performance framework that meets you where you are. Whether you're a solo dev or leading a performance team, there's a clear path forward.
Ben Hjerrild and the Uber Mobile Data Platform team just solved a problem every mobile org faces: analytics chaos. Over 40% of their events had become meaningless custom logs, and iOS/Android were tracking thin...
Uber runs 50+ mobile apps across iOS and Android. How do you get consistent analytics when every team tracks things differently?
Shaurya Jaiswal from Slice reveals how his team cut app launch API calls from 28 to 12, improving startup time by 40%. The secret? A custom observability system that exposes what Firebase Performance Monitoring...
Skyscanner was drowning in observability chaos: multiple vendors, fragmented tools, and engineers losing confidence in their ability to debug production issues.
Your key metric just tanked 20%. Was it a code change? An OS update? A data pipeline bug? Pinterest built a platform to answer this question at scale.
Stefan Jandl from Sentry just cracked a tough problem: how do you auto-instrument performance monitoring in Unity games without asking developers to write a single line of code?
Real User Monitoring isn't just a performance tool. It's the bridge between what you think users experience and what actually happens in production.
Diego Parra from Mercado Libre's Performance Engineering team just shared how they slashed API response times by 60% with one strategic fix. The culprit? Regex compilations eating 40% of CPU cycles.
Your mobile app's first impression isn't just important. It's everything. The Fullstory Team breaks down why most teams are optimizing blind, relying on assumptions instead of actual user behavior data.
DoorDash was shipping experiments that crashed their app and degraded performance for weeks before anyone could identify the cause. They built an automated system to catch issues before customers feel the pain.
Supriyo Mondal from Walmart reveals how they shaved 500-600ms off view rendering times by changing a single boolean flag. Sometimes the biggest performance wins come from the smallest tweaks.
Edward Gou from Sentry reveals why their performance scores were lying to developers. A single slow pageload could tank your entire app's score, even when 99% of users had fast experiences.
Mercari rewrote their entire mobile app and faced a nightmare scenario: millions of users reporting the new version felt slower than the old one.
Anatole Beuzon and Bowen Chen from Datadog turned what seemed like a simple deployment alert into a months-long debugging odyssey. What they uncovered reveals how deceptively complex network latency issues can ...
Markus Hintersteiner from Sentry reveals how they cracked a tricky problem: tracking user interactions in Jetpack Compose without cluttering developers' code or killing performance.