Explore 694 articles on iOS performance
Showing 20 of 694 articles (Page 18 of 35)
Swiggy was drowning in analytics chaos. Thousands of events per session, scattered specs across docs, and manual verification eating up engineering time.
Johnson Li from Coupang reveals how migrating from Mac minis to AWS EC2 transformed their mobile CI/CD pipeline. Their team was drowning in 3,000+ daily builds with 1-hour wait times.
Swift just got a massive upgrade. Feli Bernutz, Matthaus Woolard, and Natalia Panferova break down the Swift 5.6 and 5.7 releases that are reshaping how iOS teams write concurrent, type-safe code.
Tinder was manually creating 40+ localized Lottie animations for every campaign. Their solution? A clever architecture that reduced it to just one.
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.
Robinhood eliminated 30% of ALL iOS crashes by refactoring a single screen. That screen drove 30% of their revenue at the time.
Ting Becker and Paul Hudson curated the best property wrapper resources from the Swift community. If you're still writing boilerplate code in Swift, you're missing out on one of the language's most powerful fea...
Swiggy's iOS team was watching Xcode compile for minutes after single-line changes. They cut that time by 75%.
Mercado Libre's mobile apps serve 4.5 billion active devices. A Galaxy A10 might take 5 seconds to load a screen—or just 1.67 seconds, depending on conditions.
Alvin Matthew Pratama from Tokopedia tackles a deceptively complex problem: validating social media URLs when each platform has wildly different URL structures. Regex alone won't cut it.
LazyPay was serving unoptimized images directly from S3, killing app performance and burning bandwidth. Their migration to Cloudinary cut image sizes by 70%.
Robinhood was taking weeks and multiple engineers just to make simple UI changes. Their solution? Server-Driven UI that lets them ship to all platforms without app releases.
Uber rewrote their Android rider app in 2016 and made an architectural choice that most Android teams avoid: deeply nested dependency injection scopes.
Swiggy's iOS team slashed build wait times by 80% and cut 8-10 minutes off every build. Here's the detailed playbook they used with Bitrise.
Etsy's iOS listing screen handles 16% of all app traffic. But after a decade, its monolithic architecture was slowing everything down.
Slack just wrapped a massive mobile refactor. The results? 68% of iOS and 92% of Android codebases modernized, with CI times slashed by over 60%.
Slack's mobile codebase was slowing teams down. Their solution? Break the monolith into hundreds of independent modules.
DoorDash makes millions of ML predictions per second, but their Redis-based feature store was becoming a massive cost and scalability bottleneck. Could client-side caching be the answer?
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.
Medium's iOS team ditched their monolith for Swift packages and SwiftUI. A year later, they're shipping features faster than ever.