113 articles on Testing for Android performance
Showing 20 of 113 articles (Page 3 of 6)
Strava's Android team hit a wall: testing server-driven UI meant wrestling with Charles Proxy crashes, EOF errors, and 3-4 minute build times. An intern decided to fix it.
Swiggy discovered 8% of their delivery drivers were running cloned apps and spoofing GPS locations. This was breaking their live order tracking system and creating chaos for customers.
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.
Strava thought they had a few hundred crashes per day. Crashlytics revealed they were missing 42,000 crashes per week.
Ishan Khanna from Tinder shares a hard-earned lesson: that shiny third-party SDK could be a ticking time bomb for your app. Here's the framework his team uses to avoid disaster.
Instawork runs over 1 million tests daily in their CI pipeline. Here's how they made unit testing a core engineering practice, not an afterthought.
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.
Swiggy was drowning in analytics chaos. Thousands of events per session, scattered specs across docs, and manual verification eating up engineering time.
Booking.com's Android team built their own rendering performance monitoring system. Here's why Google Play Console metrics weren't enough.
Very Good Ventures shows how to build a production-ready Flutter app with Supabase that achieves 100% test coverage. This isn't your typical Firebase clone tutorial.
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.
Tokopedia's iOS team was drowning in 30-minute unit test cycles with 65 developers fighting over 9 CI/CD machines. They cut that time by 8X.
Spotify just open-sourced the tool that helped them slash their Android app size by 9%. Here's why app size matters more than you think.
Tokopedia shipped Android App Bundles and immediately hit a wall: mystery crashes on random devices. The culprit? Sideloaded APKs missing critical resources.
Karan Saimbhi from Just Eat Takeaway compares testing Jetpack Compose to watching Back to the Future on different formats—the content stays the same, but the method evolves. Here's what changes when you move fr...
New OS releases can break your app overnight. The React Native team shares critical changes in iOS 15 and Android 12 that could impact your users.
Victoria Gonda from Square tackles a tricky KMP problem: Kotlin/Native doesn't support I/O, yet your shared tests need to read fixture files. Here's the workaround that makes it possible.
Revolut's iOS team ships weekly updates with minimal regression. Their secret? Making unit tests actually fun to write.
Microsoft Teams Mobile merges 50+ commits daily from 350+ developers. How do they catch performance regressions before users feel the pain?
Kevin Cianfarini from Cash App discovered a sneaky threading bug that stumped his entire team. The culprit? A misunderstood feature in Kotlin's coroutine testing tools that silently breaks thread assertions.