109 articles on Performance Profiling for Android performance
Showing 20 of 109 articles (Page 5 of 6)
Rico Harisin from Tokopedia reveals how their Android team shipped weekly releases while building a complete performance infrastructure from scratch. Their secret? Treating CI/CD like a product.
At Farfetch, a 0.1 second delay in warm app launch costs $4.2M annually. That's less time than it takes to blink.
Dropbox Android users couldn't see folders with Cyrillic characters or certain special names. The obvious fix? Way too risky to attempt.
Jay Kong from Google's Gaming and Graphics team just opened the beta for Android GPU Inspector, and early results are impressive. Diablo Immortal cut vertex bandwidth by 45%, while Crash Bandicoot slashed frame...
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.
Spotify's mobile infrastructure team turned build time chaos into predictable performance. Their secret? Making every engineer a data scientist.
Ivan Dyatlov from Bumble Tech discovered that WebRTC's H.264 hardware encoding failed on most Android 5.x devices despite official support claims. His deep dive into codec implementations reveals why video call...
Wesley Ong from Grindr Engineering tackles a blind spot in Android performance monitoring: Firebase tracks frame rates per Activity, but what about the Fragments inside them?
Grab reduced their super app's startup time by 60% while shipping dozens of new features. Here's how they saved users 59,582 hours per day.
Grab cut app startup time by 60% while shipping dozens of new features. Here's how they did it without compromising velocity.
AWS just shipped two features that solve opposite problems: making GraphQL APIs blazing fast and keeping DynamoDB writes bulletproof. Here's how they change the game for mobile backends.
Uber's Android team hit a wall: their profiling tools were either too slow or too inaccurate to debug real performance issues.
Mootaz Ltaief from OLX Engineering put four popular Android JSON parsers head-to-head using Jetpack Benchmark. The results reveal a brutal tradeoff: the fastest parser costs you 1.1 MB of app size.
Uber operates across 600+ cities on 4,500+ mobile carriers. Their HTTP/2 stack was failing users in lossy wireless networks.
Joel Sole and the Netflix encoding team reveal why codec comparison studies often contradict each other—and how they're fixing the problem. Their findings challenge conventional wisdom about H.264, H.265, and V...
Slack's engineering team faced a classic scale problem: three platforms, three definitions of 'app launch,' and zero ability to compare performance meaningfully.
Yelp's Android team cut search render time nearly in half while slashing dropped frames by 48%. Here's how they did it.
Yelp users were literally grunting while waiting for search results to load. That's when the Android team knew they had a performance problem.
Meta's engineers were spending days or months debugging performance issues they couldn't reproduce in their device labs. Sound familiar?
Saurabh Arora from Viki cut their Android app's memory footprint by 27% while preparing for the Next Billion Users. His team's optimization work landed them as an Android GO launch partner.