109 articles on Performance Profiling for Android performance
Showing 20 of 109 articles (Page 3 of 6)
Snap's engineering team just dropped a masterclass in mobile performance debugging. Ever wonder why your AR lens stutters on the first frame?
Snap's AR Lenses reach millions, but performance issues can kill engagement before users even see your creation. Here's how Snap ensures their AR experiences work across every device.
BAM just launched Flashlight, a Lighthouse-inspired tool that finally brings performance scoring to mobile apps. Android developers now have a standardized way to measure app performance.
Here's a performance optimization problem most Android teams don't see coming: your security tooling might be silently breaking your baseline profiles. Guardsquare just solved it.
Snap Research just proved that Vision Transformers can run as fast as MobileNet on actual mobile devices. Yes, really.
Zomato's Android app was slow. Their network layer was the bottleneck, costing them speed, bandwidth, and user patience.
Klarna's A/B testing platform needed single-digit millisecond latency at 99.9%. Their Node.js service was spiking to seconds under load.
Yi Yang from Google reveals why your Android performance measurements might be completely wrong. Debug builds can show 2-3x worse performance than what users actually experience.
Turo's Android team slashed their app startup time by 77%. Here's how they turned a sluggish launch into a lightning-fast experience.
Strava's Android team cut app launch time in half by treating performance optimization like athletic training: consistent measurement, strategic improvements, and relentless focus on efficiency.
Doni Winata from Traveloka's Android Infra team reveals how his team automated build benchmarking to catch performance regressions before they hit production. For projects with 300+ modules and 15-20 minute bui...
Pinterest was bleeding user engagement on Android. With 75% of signups coming from outside the U.S. and 90% of global smartphones running Android, they had to fix their performance problem fast.
Grab's engineering team discovered their Go apps were mysteriously throttling at 1.94 CPU cores but flying at 2 cores. The culprit? A sneaky interaction between Kubernetes VPA and GOMAXPROCS.
OkCredit serves millions in India's Tier-2/3 cities where flaky networks are the norm. Their Android team just cut network call times by 30% with some clever client-side optimizations.
Klarna's team removed their caching layer and saw a 25% performance boost. Wait, what?
Mercado Libre's Android team achieved a 24% performance boost without using Google's recommended Baseline Profiles or Macrobenchmark tools. How did they pull it off?
OkCredit slashed their Android app cold startup time by 70%. Here's the engineering playbook that made it happen.
Mercado Libre's mobile apps serve 4.5 billion active devices. A Galaxy A10 might take 5 seconds to load a screen—or just 1.67 seconds, depending on conditions.
Slack's engineering team ran into a classic performance testing problem: spinning up load tests was so time-consuming that teams avoided doing it. Their solution? Never stop testing.
Lyft's Android app serves millions of users daily, but how do you track CPU performance when hundreds of engineers ship code constantly? The team built a custom monitoring system from scratch.