98 articles on UI Performance for Android performance
Showing 20 of 98 articles (Page 3 of 5)
Premise's Android team put Jetpack Compose 1.0 through rigorous performance testing before adopting it in production. The results? Surprising insights about render times, cold starts, and optimization strategie...
Snap's Lens Performance Toolkit has been sunset, but its replacement Mobile Monitor offers AR developers something better. Here's what changed and why it matters for your lens performance.
Snap's Lens Studio just gave AR developers a powerful weapon against performance issues. If your lenses are failing submission due to slow activation or low FPS, this tool is your answer.
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.
Lyft Bikes & Scooters was drowning in complexity: 3 vehicle types, multiple markets, and endless switch statements. Their solution? Move the UI logic to the server.
ShareChat cut janky frames by 75% and boosted feed scrolling by 60%. Here's how they debugged their way to a 4.3-star rating.
OkCredit reduced frozen frames by 40% by obsessing over a metric most Android teams ignore: screen response time.
Swiggy's search feature was a mess: 2,000+ lines in a single ViewModel, monolithic XML files, and performance issues. Time for a complete rewrite.
OkCredit's Android team was hitting a wall: complex XML layouts were causing frozen frames and ANRs. AndroidX's AsyncLayoutInflater wasn't cutting it.
Pinterest's Android team faced a unique challenge: playing multiple videos simultaneously in a two-column grid without killing performance. Here's how they optimized ExoPlayer to handle it.
Strava's engineering team faced a deceptively hard problem: how do you automatically detect when a runner stops moving without draining their battery or showing the wrong pace?
OkCredit slashed their ANR rate by 67% and cold startup time by 70%. Here's how they debugged one of Android's most frustrating problems.
Arlind Hajredinaj from SoundCloud reveals how a beautiful UI redesign accidentally tanked their image loading performance. The fix? A deep dive into Android optimization that every mobile team should read.
OkCredit ran a fascinating A/B test: Jetpack Compose vs XML layouts in production. The results surprised them—and reveal what most teams miss about Compose performance.
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.
Turo's Android team hit a wall: their single-device test setup couldn't keep up with their growing UI test suite. Hours of wait time for a single test run wasn't going to cut it.
Booking.com's Android team built their own rendering performance monitoring system. Here's why Google Play Console metrics weren't enough.
Tinder was manually creating 40+ localized Lottie animations for every campaign. Their solution? A clever architecture that reduced it to just one.
Alexandre Bruneau from Medium Engineering discovered that Jetpack Compose's elevation overlay only works with default Material theme colors. His workaround unlocks custom color elevation for any design system.