Optimizing OpenTelemetry's Span Processor for High Throughput and Low Latency
DoorDash tunes OpenTelemetry for fast tracing with low lag overhead.
Showing 20 of 400 articles (Page 15 of 20)
DoorDash tunes OpenTelemetry for fast tracing with low lag overhead.
Bank of America cut in-app response times by 50% with Adobe’s help.
Microsoft shrinks LinkedIn’s Android app with practical cuts.
Dropbox sniffs out Android memory leaks to keep their app running lean.
AWS Amplify’s CDN caching makes apps load faster with less wait.
Zalando digs into how Flexbox works in Jetpack Compose for Android UI.
Pinterest uses Honeycomb to keep their CI clear, stable, and easy to watch.
Walmart traces CI/CD performance to keep their pipeline reliable.
Pinterest revamped their CI system, splitting tasks and streamlining to cut build times by over half.
Dropbox cut Android startup time by 30% with some clever tweaks.
Microsoft tracks Android app size in CI to catch bloat early on.
In the first part, we discussed what ANR is and what are the ways of tracking it. In this article, you will find information on what problems we found in our application, how we fixed them, and the results we achieved.
One of the worst things that can happen to your app’s responsiveness is an Application Not Responding (ANR) dialogue. A high ANR rate may affect user experience and, potentially, Google Play search positions and featuring.
Dropbox overhauled their Android testing setup for smoother, faster runs.
The Grammarly app on both Android and iOS is a native keyboard. The motivation behind building a keyboard, as opposed to a traditional mobile app like a text editor
Huawei’s Leak Canary sniffs out Android memory leaks like a pro.
Farfetch fine-tunes their app startup with deeper optimizations.
Netflix syncs Android and iOS logic with Kotlin Multiplatform for reliability.
Dropbox found a weird but genius fix for an Android path problem.
When Lyft was first developed, it was built using a monolithic server architecture. Within this architecture, all mobile clients relied on a single endpoint for fetching all data pertaining to the user and their ride (the “state of the world”):