Android × UI Performance
Android UI Performance, page 2
Android UI Performance articles 31–60 of 101
Optimising the Swiggy Restaurant App
Swiggy's restaurant app was crashing under load. Their React Native app couldn't handle more than 100 orders on budget devices, and they needed to scale 10x.
Building Your Next Casual Game With Flutter
Zoey Fan from Google's Flutter team just dropped a major update to their Casual Games Toolkit—and it's packed with templates that could save you weeks of setup time. If you've been curious about Flutter for gam...
Making Direct Messages Reliable and Fast
Instagram DMs handle millions of messages per second. How do they make every send feel instant, even when your network drops mid-tap?
Making Swiggy's Order Tracking a Magical Experience
Swiggy discovered customers were anxiously checking their order tracking screen multiple times during the 20-45 minute delivery window. Their solution? Let users track orders while doing literally anything else...
Building a Better Instagram App for Android
Instagram cut their Android app startup time in half and reduced APK size by 50%. Here's how they did it.
Improving Comment Rendering on Android
Instagram's Android team faced a brutal problem: complex captions with emojis and links were causing 50ms UI thread blocks, making scrolling feel janky even on flagship devices.
Making Swiggy Buttery Smooth
Swiggy's iOS team cut their app launch time in half and reduced app size by 8MB. Here's how they did it.
Bringing HDR video to Reels
Meta just solved a problem most users never notice: making HDR video look great on billions of devices with wildly different capabilities.
Enhancing User Experience: Reducing ANR Rates with DataStore in Skeelo Android App
Skeelo's Android app was freezing on users. The culprit? SharedPreferences blocking the main thread and triggering ANR errors.
Native UI and multiplatform Compose with Redwood
Cash App just open-sourced Redwood, their answer to the multiplatform UI problem. Unlike other solutions, it renders with native UI toolkits instead of recreating them.
Beautiful Performant Android UI
Instagram built a full-screen video viewer that needed to feel buttery smooth on every Android device. Here's how they made animations delightful without killing performance.
Testing Android UI Performance Part 2
You found the jank in your Android app. Now what? Most teams stop at identifying the problem—but that's only half the battle.
Testing Android UI Performance
Glance's engineering team serves 100M+ users where visual experience is everything. When UI performance drops, users notice immediately—and they leave.
Measuring Render Performance with Jetpack Compose
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...
Performance Optimization Guide
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.
Mobile Lens Profiler: Case Study
Snap's engineering team just dropped a masterclass in mobile performance debugging. Ever wonder why your AR lens stutters on the first frame?
Mobile Monitor
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.
Lens Performance Toolkit
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.
The Journey to Server Driven UI At Lyft Bikes and Scooters
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 addresses Jank issues to increase feed scrolling by 60% | Developer stories | Android Developers
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.
Fan-tastic Search for Blazing Fast Results
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.
Screen Response Time: A Critical Metric for User Experience
OkCredit reduced frozen frames by 40% by obsessing over a metric most Android teams ignore: screen response time.
OKLayoutInflater
OkCredit's Android team was hitting a wall: complex XML layouts were causing frozen frames and ANRs. AndroidX's AsyncLayoutInflater wasn't cutting it.
Improving Auto Pause for Everyone
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?
Improving the Player on Android
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.
How We Reduced Our ANR by Three Times
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.
Image Loading and Optimization on Android
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.
Comparing Jetpack Compose Performance with XML
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.
Four Lessons in Making Pinterest Faster on Android
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.
Android UI Testing with Firebase
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.