Discover 167 articles on Testing in mobile performance
Showing 20 of 167 articles (Page 4 of 9)
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.
John Flanagan from DoorDash reveals how his team eliminated duplicate code between SwiftUI previews and snapshot tests. The solution? An open-source tool that cuts testing boilerplate to a single line.
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.
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.
Very Good Ventures shows how to build production-ready Flutter authentication in hours, not days. Their approach combines AWS Amplify with battle-tested architecture patterns for 100% test coverage.
Very Good Ventures just shipped a production Flutter SDK in three weeks with 100% test coverage. Here's how they partnered with Embrace to bring enterprise-grade observability to Flutter developers.
Shopify went all-in on React Native, but had one critical question: Is it actually as fast as native? They needed proof, not assumptions.
Turo's iOS team took their crash-free rate from 99% to 99.99% in just one year. Here's how a lean 5-engineer team achieved what most would consider impossible.
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.
Lyft's iOS tests were spending 93% of their time on steps that had nothing to do with what they were actually testing. Sound familiar?
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.
Dream11 handled 5.5 million concurrent users and 80 million requests per minute during IPL 2020. Their secret? A custom performance testing framework called Torque.