Explore 19 articles from DoorDash on mobile performance
Showing 19 of 19 articles (Page 1 of 1)
DoorDash handles 2 billion orders annually, and every ETA prediction matters. Their old tree-based models couldn't keep up with the complexity.
DoorDash was shipping experiments that crashed their app and degraded performance for weeks before anyone could identify the cause. They built an automated system to catch issues before customers feel the pain.
DoorDash ships a new iOS app version every single week. Here's how they coordinate testing, releases, and hotfixes across multiple teams without losing their minds.
Manolo Sañudo from DoorDash reveals how their iOS team ships weekly releases without breaking things. Spoiler: it's not about having more QA people.
DoorDash was sending cart abandonment notifications to users who were still actively browsing. The result? Annoying customers and missing conversion opportunities.
DoorDash's team cracked a classic mobile dilemma: how do you push FAQ updates instantly without waiting weeks for app store approvals? Their solution cut deployment time from 2+ weeks to under 24 hours.
Md Al Mamun and Michael Thole from DoorDash reveal how their 100+ engineer iOS team eliminated project merge conflicts entirely. The secret? A command-line tool that turns hours of painful XML debugging into se...
Filip Busic from DoorDash reveals how three targeted optimizations slashed iOS app launch time by 60%. The culprits? String operations, hashing strategies, and sneaky third-party framework initializers.
DoorDash cut their iOS app launch time by 60%. Here's how they did it with three targeted optimizations that any mobile team can learn from.
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.
DoorDash just proved SwiftUI is enterprise-ready. Their secret? Don't start with a rewrite.
DoorDash users were waiting up to 10 seconds for pages to load. Here's how their team turned performance audits into measurable conversion wins.
Zoltan Lippai from DoorDash cracked a problem that stumped early SwiftUI adopters: how do you programmatically scroll when Apple didn't give you the tools? His team built their own solution for iOS 13.
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?
Sonic Wang from DoorDash breaks down Kotlin coroutines from bytecode to scheduler. If you've ever wondered what actually happens when you call 'suspend', this deep dive reveals the magic.
DoorDash's Android team learned the hard way that adding payments isn't just about processing transactions. It's about building a system that scales across countries, payment methods, and user expectations.
DoorDash's OpenTelemetry adoption hit a wall: 72% CPU utilization versus 56% without tracing. That's a costly tax for observability.
David Phan from DoorDash reveals how they rebuilt two distinctly branded iOS apps from a single codebase after acquiring Caviar. The result? 90% shared code with completely different user experiences.
Maria Sharkina from DoorDash discovered that Android's Navigation Library has a critical flaw: it forces navigation before your app is ready. Here's how her team solved it without breaking deep links or the bac...