Discover 92 articles on Networking in mobile performance
Showing 20 of 92 articles (Page 4 of 5)
Michael Rebello from Lyft reveals how they scaled from hand-written APIs to a unified networking architecture serving 500+ endpoints. The journey involved killing technical debt, slashing payload sizes by 50%, ...
Artem Sharypov from Strava's Experience team rebuilt their entire Android upload service from scratch. Why throw away working code? Because sometimes technical debt costs more than a rewrite.
Jesse Wilson from Square just rewrote 25,000 lines of Java code in Kotlin without changing a single feature or fixing a single bug. Here's why that matters for your Android app.
Arinc Elhan from Connected2.me breaks down silent push notifications in iOS, and there's more to them than just background data delivery. Apple throttles them aggressively, and most developers don't know the li...
Uber operates across 600+ cities on 4,500+ mobile carriers. Their HTTP/2 stack was failing users in lossy wireless networks.
Caviar's mobile site was bleeding conversions. Their homepage took nearly 10 seconds to load, and 53% of users were bouncing before seeing a single restaurant.
Efe Karasabun from Thumbtack reveals how GraphQL solved their biggest mobile API headaches. No more over-fetching data or coordinating breaking changes across teams.
Jesse Wilson explains why Square is cutting off 11% of Android devices with OkHttp 3.13. Spoiler: your web servers might break too.
Uber's main app hit 60MB and struggled on older Android devices in emerging markets. So they built something radically different.
Netflix's Titus container platform hit a wall: their singleton leader couldn't handle the API query load. Here's how they scaled horizontally without breaking consistency guarantees.
Discord handles 2.6 million concurrent voice users with just 850 servers across 13 regions. Here's how they built a custom WebRTC architecture that scales.
Instagram serves 800 million monthly users, 80% outside the US. How do you make the app feel instant for everyone, regardless of network quality?
TripAdvisor ships a 100MB app every two weeks to millions of users. One regression could tank performance for their entire user base.
Instagram's background prefetching could easily drain batteries and waste data. Here's how they built a system that's both fast and responsible.
Sergey Skachkov and Ajinkya Apte from Zynga cut mobile game latency in half for global players. Their geo proxy solution turned frustrated users into retained ones.
Building offline-first React Native apps? The network will fail. Your app doesn't have to.
Zhiyao Wang and the Airbnb team tackled a massive problem: their mobile inbox was loading like a 2001 webmail client. With 100k+ messages per hour, every tap meant a network request, killing UX on slow connecti...
LinkedIn shipped a 75KB mobile experience that loaded in under 6 seconds on 100 Kbps connections. Six engineers built it in four months.
Twitter open sourced their iOS image pipeline after hitting a breaking point: 2GB caches, corrupted images, and no way to clear data when users logged out. Here's how they rebuilt it from scratch.
Callstack explores how Apollo Client transforms React Native app performance when working with GraphQL APIs. This 2016 piece laid groundwork that's still relevant for mobile teams today.