Explore 733 articles on iOS performance
Showing 20 of 733 articles (Page 18 of 37)
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's iOS app was taking forever to launch. Their mobile team spent 3 months hunting down bottlenecks and achieved a 12x improvement in cold start time.
Reddit's mobile team just dropped their unfiltered take on iOS vs Android development in 2022. Spoiler: both platforms have some explaining to do.
Lazar Nikolov explores why Android and iOS are finally catching up to React Native and Flutter. The shift to declarative UI is reshaping native mobile development.
Andrea Scuderi from Just Eat reveals how his team tackled a 19,602-line legacy iOS module without a risky big-bang rewrite. Their 9-phase restructuring approach cut code by 23% while maintaining stability.
Airbnb just solved one of mobile animation's biggest performance problems. Lottie 4.0 eliminates the CPU overhead that was causing animations to drop frames and freeze.
Snap Research just proved that Vision Transformers can run as fast as MobileNet on actual mobile devices. Yes, really.
Swiggy slashed their Android app size by 22.6% in just one day. Here's how they did it without the usual complexity.
Klarna's A/B testing platform needed single-digit millisecond latency at 99.9%. Their Node.js service was spiking to seconds under load.
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.
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?
Veyndan Stuart from Cash App just open-sourced a solution to one of mobile development's most annoying problems: writing pagination logic twice for Android and iOS.
Uber's Client Platform Engineering team faced a massive challenge: rolling out MDM to 20,000+ employees across hundreds of global offices where standard Apple enrollment wouldn't work everywhere.
Spotify migrated 2,200+ mobile components and moved their entire iOS/Android codebase to Bazel across 100+ squads. Here's how they survived the chaos.
Grab's ML feature store went from 200ms to 2 second latency. The culprit? A single line of code in an async library.
Gojek turned ride-hailing into climate action with a simple toggle. One developer said it best: 'For the first time in my life, writing code generated physical outputs.'
Meetup sends 8-10 million notifications daily. Their queue kept backing up, sending messages late or not at all.
Lyft engineers faced a nightmare scenario: feature flags causing infinite crash loops on app launch, requiring emergency hotfixes and losing revenue. They built Safe Mode to break the cycle.
Slack's 8-person Mobile DevXp team saved $240K annually just by improving PR notifications. Most companies are massively underinvesting in developer experience.
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?