Explore 937 articles on Android performance
Showing 20 of 937 articles (Page 20 of 47)
Flipkart shaved 30% off page load times in their React Native app with 500M weekly visits. Here's how they did it without rewriting everything.
Fullstory got a wake-up call when a prospect flagged a 6% startup time increase from their Android SDK. Even when disabled, the SDK was adding 100ms to app launches.
Square manages hundreds of mobile engineers in a monorepo, all contributing to apps that must stay under Google Play's 150 MB limit. How do they prevent app bloat at scale?
Meta's Engineering blog just hit a 404. Sometimes even the biggest tech companies deal with broken links and content migrations.
Cash App just open-sourced Turbine 1.0, solving one of the trickiest parts of Kotlin coroutines: testing Flows without the headache.
The article link appears to be broken or unavailable. This is a 404 error page from Medium, not the actual Gojek engineering article about modularizing their Android driver app.
Swiggy was bleeding money on video bandwidth costs. The culprit? Videos being requested at 270px, 272px, 275px... you get the idea.
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.
Emre Muhammet Engin from Getir tackles a truth bomb: if your code is hard to test, your design probably sucks. His deep dive into MockK shows Android developers how to fix that.
Glance's engineering team scaled their load testing from basic scripts to a full Kubernetes-powered distributed system. Here's how they did it with Locust.
AWS Device Farm now supports rooted Android devices, unlocking granular performance benchmarking that was previously impossible at scale.
Patrick Tyska and Terry Yiu from Cash App reveal how the same $1,000 needs to display four different ways across their app. Their solution? Kotlin Multiplatform to consolidate 10 separate money formatters into ...
Premise's mobile team caught a sneaky 3x build time regression that only showed up in CI. Here's how they hunted it down using Gradle Enterprise.
You found the jank in your Android app. Now what? Most teams stop at identifying the problem—but that's only half the battle.
Anatole Beuzon and Bowen Chen from Datadog turned what seemed like a simple deployment alert into a months-long debugging odyssey. What they uncovered reveals how deceptively complex network latency issues can ...
Swiggy was missing production deadlines because their UAT environments were constantly unstable or unavailable. Sound familiar?
70% of users expect apps to launch in 3 seconds. 63% will abandon yours if it takes more than 5.
Glance's engineering team serves 100M+ users where visual experience is everything. When UI performance drops, users notice immediately—and they leave.
Pepperfry's engineering team cut API response times by parallelizing requests. Here's how they used Java multi-threading to handle scale without blocking.
Robinhood was taking weeks and multiple engineers just to make minor UI tweaks. Their Server Driven UI platform cut that to hours with one engineer.