113 articles on Testing for Android performance
Showing 20 of 113 articles (Page 2 of 6)
Shopify doubled developer productivity by turning the most tedious part of mobile development into a one-click experience.
Wealthfront's Android team had a problem: their test suite was slowing down every PR merge. Running all tests on every change wasn't scaling.
Skeelo's QA team built a scalable E2E testing framework using Python + Appium. Here's the architecture that keeps their mobile tests maintainable as the app grows.
Uber's mobile testing was broken. Engineers spent 30-40% of their time maintaining test scripts that broke with every UI change. So they built an AI that tests apps like a human would.
Duolingo catches critical bugs before users ever see them. Their secret? 70% of employees actively use internal builds daily.
Uber deploys 11,000 code changes weekly. How do they catch crashes before users notice? They built Healthline, powered by Apache Pinot.
Joana Melo from Klarna turned a 6-month diversity program into company-wide impact by solving a pain point that had defeated multiple engineering teams before her.
Cash App just open-sourced Turbine 1.0, solving one of the trickiest parts of Kotlin coroutines: testing Flows without the headache.
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.
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.
Swiggy was missing production deadlines because their UAT environments were constantly unstable or unavailable. Sound familiar?
Glance's engineering team serves 100M+ users where visual experience is everything. When UI performance drops, users notice immediately—and they leave.
Spotify Wrapped serves 150M+ users in a single morning. How do you load test for that kind of thundering herd?
Gojek's engineering team cracked a common CI/CD headache: how do you run automated tests from a separate repo without creating pipeline chaos?
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.
Swiggy's Android team was stuck in a painful cycle: rebasing PRs, waiting hours for full test suites to run, then doing it all over again. One frustrated engineer decided to fix it over a weekend.
Lyft discovered memory leaks affecting only 1% of users—issues that would never show up in local testing. Here's how they built a production monitoring system to catch what profiling tools miss.