Explore 19 articles from Uber on mobile performance
Showing 19 of 19 articles (Page 1 of 1)
Ben Hjerrild and the Uber Mobile Data Platform team just solved a problem every mobile org faces: analytics chaos. Over 40% of their events had become meaningless custom logs, and iOS/Android were tracking thin...
Uber runs 50+ mobile apps across iOS and Android. How do you get consistent analytics when every team tracks things differently?
Uber's mobile testing was broken. Engineers spent 30-40% of their time maintaining test scripts that broke with every UI change. So they built an AI that tests apps like a human would.
Uber deploys 11,000 code changes weekly. How do they catch crashes before users notice? They built Healthline, powered by Apache Pinot.
Uber's iOS app startup metrics became 130% inflated overnight. The culprit? iOS 15's pre-warming feature broke their entire measurement system.
Uber's Client Platform Engineering team faced a massive challenge: rolling out MDM to 20,000+ employees across hundreds of global offices where standard Apple enrollment wouldn't work everywhere.
Uber built a web app that loads in 3 seconds on 2G networks. Here's how they made it smaller than a typical image file.
Uber rewrote their Android rider app in 2016 and made an architectural choice that most Android teams avoid: deeply nested dependency injection scopes.
Uber rewrote their entire driver app serving 3 million drivers. How do you ship that without breaking your business?
Uber's iOS app was bleeding users: every time it crossed Apple's download limit, they lost 10% of installations and 20% of first-time bookings.
Uber threw away years of code and rebuilt their rider app from scratch. Here's why that radical decision paid off.
Uber's Android team hit a wall: their profiling tools were either too slow or too inaccurate to debug real performance issues.
Uber operates across 600+ cities on 4,500+ mobile carriers. Their HTTP/2 stack was failing users in lossy wireless networks.
Uber ran 129 experiments across 354 projects to answer one question: What's the real cost of adopting Kotlin at scale?
Uber's main app hit 60MB and struggled on older Android devices in emerging markets. So they built something radically different.
Uber rewrote their entire driver app with hundreds of engineers over 18 months. Joel Spolsky once called rewrites 'the single worst strategic mistake' a software company can make.
Uber scaled from a dozen iOS engineers to hundreds in just a few years. Their tooling nearly collapsed under the weight.
UberEats needed a Restaurant Dashboard for 3-party logistics. Their web app couldn't cut it, so they bet on React Native before it was proven at scale.
Uber completely rewrote their rider app from scratch. Here's why they threw away years of code and started over.