How Lyft optimizes Android performance
Showing 9 of 9 articles (Page 1 of 1)
Across the past couple of years, different mobile app teams across Lyft have been moving to Server Driven UI (SDUI) for three main reasons: To deal with business complexity
Lyft hunts down sneaky memory leaks in their live Android apps with sharp tools.
Lyft’s ‘Safe Mode’ kicks in after crashes to keep their app steady for users.
Implementation and production deployment of Envoy Mobile networking library for mobile applications.
Lyft keeps a close eye on Android CPU use to ensure top-notch performance.
Shares the story of a solo developer optimizing an Android app, offering insights into individual development strategies.
Lyft shares their tricks for keeping their mobile app smooth and user-friendly.
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 thei...
Evolution of mobile networking strategies and optimizations at Lyft.