The Journey to Server Driven UI At Lyft Bikes and Scooters
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
How Lyft optimizes Android performance
Showing 7 of 7 articles (Page 1 of 1)
Detecting Android Memory Leaks in Production
Lyft hunts down sneaky memory leaks in their live Android apps with sharp tools.
Recovering from Crashes with Safe Mode
Lyft’s ‘Safe Mode’ kicks in after crashes to keep their app steady for users.
Monitoring CPU Performance of Lyft’s Android Applications
Lyft keeps a close eye on Android CPU use to ensure top-notch performance.
How a single Android developer improved Lyft’s Drivers app startup time by 21% in one month
Shares the story of a solo developer optimizing an Android app, offering insights into individual development strategies.
Mobile Performance @ Lyft
Lyft shares their tricks for keeping their mobile app smooth and user-friendly.
Decomposing network calls on the Lyft mobile apps
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 their ride (the “state of the world”):