12 articles on Server Driven UI for iOS performance
Showing 12 of 12 articles (Page 1 of 1)
Brownfield React Native integration via “React Native as a package”
In the first post in this series Benoit Sarrazin discussed the adoption of The Composable Architecture in our iOS app. He covered the reasons for this change, the benefits it brought, and the challenges we face...
In the ever-evolving landscape of iOS development, architectural decisions can make or break a team’s productivity and code quality. For our large team of iOS developers working on a Server Driven UI (SDUI) pla...
I’m the main coder for a massive data project. It’s a 2+ million book archive with AI search and social interaction. We have been building the desktop version for 1+ year
A single backend response can do a lot more than you think.
DoorDash built a WebView-based FAQ hub for their Dasher app, using server-driven UI content and a promise-based communication protocol between native iOS/Android apps and web. This approach enables rapid conten...
Robinhood’s server-driven UI lets frontend devs make big changes, fast.
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
At Tinder, we enjoy delivering global-wide experiences to our members. As such, we deploy visually-rich content all around the world, and localization plays a huge role.
Carousell explores the problems that led them to build a server-driven dynamic UI system (fieldsets) for their marketplace, enabling dynamic sell forms, search filters, and listing details across iOS, Android, ...
Deep dive into Carousell's fieldset system architecture: JSON-based document schemas, component hierarchies, cross-platform rendering, backward compatibility via build versioning, and the request/response flow ...
Badoo's iOS team explains how they built a server-driven animation system to allow live streaming gift animations to be updated without requiring an App Store release. Using the Lottie library and Adobe After E...