At DoorDash, dashing is highly process dependent.
Tag Archives: Android
Your Deep Links Might Be Broken: Web Intents and Android 12
Part of being a modern-day Android developer is keeping up with Google’s latest update that can have outsized effects and consequences on application’s performance, especially when new changes affect how older app versions function.
Generally, Google releases two types of changes that impact developers: API changes and behavior changes.
Fortunately, API changes tend to be obvious.
Eight Things We Learned from Implementing Payments in the DoorDash Android App
Effective implementation of payments in a mobile app requires precise attention to factors such as payment methods, the user experience, and fraud prevention.
Launching Dark Mode While Building a Scalable Design System
A large number of our DoorDash deliveries happen during the evening and in late night hours.
[Series] How I Spend My Time – iOS Mobile Product Engineer
Since joining DoorDash about a year and a half ago, I have been able to work on a number of teams as an iOS engineer such as Dasher, Drive, Geo-Intelligence, and Internationalization.
Contract Testing with Pact
As we migrate our systems to a microservices-oriented architecture at DoorDash, we have taken care to balance the excitement around anticipated benefits (development velocity, deployment independence, etc.) with a more measured assessment of our preparedness to work with the complexities introduced by more distributed systems.
Synchronizing Network Calls With RxJava
Most Android apps rely on network calls to a set of backend services.
Using Automated Testing to Scale Android Development with a Growing Team
At DoorDash, mobile is an integral part of our end user experience.