Integrating Extensions into Large-Scale iOS apps
Today, when you open Apple Maps and choose a destination, you are able to see a list of available Lyft offers, seamlessly routing you to the Lyft app to book your next ride.
Showing 7 of 7 articles (Page 1 of 1)
Today, when you open Apple Maps and choose a destination, you are able to see a list of available Lyft offers, seamlessly routing you to the Lyft app to book your next ride.
Our primary focus will be on the client-side aspects, with a brief overview of the server functionalities. To maintain brevity, we’ll refrain from providing an exhaustive description of the inner workings.
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’s ‘Safe Mode’ kicks in after crashes to keep their app steady for users.
Lyft tests iOS early with ‘Shift-Left,’ catching bugs before they grow big.
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 their ride (the “state of the world”):