113 articles on Performance Profiling for Android performance
Showing 13 of 113 articles (Page 6 of 6)
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.
TripAdvisor ships a 100MB app every two weeks to millions of users. One regression could tank performance for their entire user base.
Facebook cut React Native Time to Interaction in half on low-end Android devices. The secret? They stopped trusting their testing tools and went straight to production data.
Marko Kevac from Bumble's Platform team benchmarked 6 associative array implementations to replace their aging Judy data structure. The winner? Not what you'd expect when memory matters.
Zalando's engineering team faced a tricky challenge: how do you know if a user actually *saw* an item in a scrolling list, not just flew past it?
Facebook built a 2,000-device testing lab inside a data center. The journey from tangled cables to custom EMI racks is a masterclass in scaling mobile performance testing.
Slack was making 4.2 million users wait through loading screens every single day. Time to fix that.
The React Native team made their app startup twice as fast. Here's how they tackled one of mobile's most critical performance challenges.
Skyscanner needed to store 1.6 billion weights to rank hotel prices. Their in-memory approach couldn't scale, so they turned to AWS.
Facebook processes thousands of mobile code changes weekly. How do they catch performance regressions before users feel the pain?