Explore 20 articles from Grab on mobile performance
Showing 20 of 20 articles (Page 1 of 1)
Grab's Android team cracked a 6-year problem that stumped multiple attempts: enabling R8 optimization across 9 million lines of code. One engineer led the charge, and AI was the secret weapon.
Grab's engineering team just reclaimed terabytes of storage across 100+ million Android devices without breaking a sweat. Their secret? A clever twist on a decades-old caching algorithm.
Grab achieved 98% monthly active adoption of Cursor across their engineering org in just months. That's nearly 30 points higher than industry benchmarks for high-performing teams.
Ever tried debugging a mobile app crash without knowing what the user actually did? You're flying blind.
Grab moved 250+ Mac minis from a US cloud to a Malaysian data center. The results? 40% faster builds and $2.4M saved.
Grab's SDK was taking 4 minutes to initialize with 400MB of config data. That's a cold start problem that kills autoscaling.
Grab's configuration management SDK was crushing service performance with memory spikes and CPU throttling. 98% of services were loading 100x more data than they actually needed.
Grab's engineering team faced a brutal problem: rain in Southeast Asia would crash their entire ride-hailing system. When demand spiked locally, users everywhere suffered.
Grab's ML feature store went from 200ms to 2 second latency. The culprit? A single line of code in an async library.
Grab's engineering team discovered their Go apps were mysteriously throttling at 1.94 CPU cores but flying at 2 cores. The culprit? A sneaky interaction between Kubernetes VPA and GOMAXPROCS.
Grab's engineering team just unlocked 30% memory savings and 38% storage reduction with a simple compiler flag. Here's how Profile-Guided Optimization (PGO) delivered massive gains with minimal code changes.
Grab's iOS team turned flaky CI tests into a 50% CPU reduction story. Their secret? Observability tools and some creative workarounds for Xcode 13.1's notorious Spotlight bug.
Grab's engineering team learned the hard way: retries and circuit breakers aren't enough when you're running hundreds of microservices at scale.
Grab lost 95% of ride bookings for a full minute when a single Redis slave node failed. Their highly available cluster with multiple replicas somehow became a single point of failure.
Grab's Android app had 4 million lines of code and was bleeding users. Google's research showed every 6MB increase costs 1% of conversions.
Grab built their entire GrabPay merchant app in React Native, then used those learnings to rebuild core payment features in their main passenger app. The result? Half the maintenance resources with identical pe...
Grab went from one monolithic mobile app to over 1,000 modules. Here's what they learned about scaling a superapp.
Grab's logging bills were spiraling out of control. Their solution? A complete rethink of how they capture what happens in production.
Grab reduced their super app's startup time by 60% while shipping dozens of new features. Here's how they saved users 59,582 hours per day.
Grab cut app startup time by 60% while shipping dozens of new features. Here's how they did it without compromising velocity.