Explore 13 articles from Gojek on mobile performance
Showing 13 of 13 articles (Page 1 of 1)
Raditya Gumay from GoTo discovered his navigation UI was recomposing 60+ times per minute. The culprit? A single lambda inside a data class that looked completely innocent.
Gojek's Android app was taking 14.35 seconds to launch. With 500+ modules and millions of lines of code, something had to change.
Gojek was sending 97-99% of driver bid notifications successfully. They rewrote the system and hit 99.9%+.
Gojek discovered that 11 of their top destinations in Jakarta weren't restaurants or malls. They were train stations and bus hubs.
Gojek's driver app modularization cut CI build times by 33% and unlocked team-level productivity metrics. Here's what they learned from breaking up their monolith.
The article link appears to be broken or unavailable. This is a 404 error page from Medium, not the actual Gojek engineering article about modularizing their Android driver app.
Gojek's Android driver app was drowning: 30-minute CI builds, 10-minute local builds, and a team that had outgrown its monolithic codebase. Something had to give.
Gojek's engineering team cracked a common CI/CD headache: how do you run automated tests from a separate repo without creating pipeline chaos?
The article link appears to be broken or unavailable. I cannot access the content about GoTransit's mobility integration.
Gojek turned ride-hailing into climate action with a simple toggle. One developer said it best: 'For the first time in my life, writing code generated physical outputs.'
Gojek runs 15,000+ VMs across 250+ GCP projects serving millions of customers. How do they manage infrastructure at this scale without chaos?
Gojek's iOS team was bleeding 11 minutes per build. 100 engineers, 350 daily CI pipelines, and a productivity crisis that demanded action.
Gojek's driver app serves 2 million+ partners who depend on it for their daily income. When the app goes down for even an hour, drivers lose significant earnings—so a rewrite was high stakes.