20 articles on Server Driven UI for iOS performance
Showing 20 of 20 articles (Page 1 of 1)
Zalando is migrating 90+ screens across iOS and Android to React Native without rebuilding their entire app. Here's how they're pulling it off for 52M+ customers.
Tripadvisor's mobile team was drowning in nearly-identical UI components. Their server-driven UI framework promised speed but delivered the opposite.
Tripadvisor's iOS team was drowning in coordinator spaghetti. Navigation paths were impossible to trace, and even senior engineers couldn't debug their own flows.
Timotius Leonardo Lianoto from IDN Engineering just solved a problem most iOS teams don't even realize they have: Remote Config is quietly eating memory and creating testing nightmares.
Careem was losing weeks waiting for app releases just to update a banner. During Ramadan, when customer behavior shifts daily, that delay was killing their food business.
Swift vs React Native: the debate that never dies. But what does the data actually show?
Duolingo ships UI changes in minutes, not weeks. Their server-driven UI system bypasses app store releases entirely.
Zalando powers 13 dynamic mobile pages without waiting for app store releases. Here's how they built a server-driven UI framework that ships changes same-day.
Andrea Scuderi from Just Eat reveals why backend-driven UI can be a double-edged sword. His team ships UI changes without app releases, but the testing complexity nearly broke their workflow.
DoorDash's team cracked a classic mobile dilemma: how do you push FAQ updates instantly without waiting weeks for app store approvals? Their solution cut deployment time from 2+ weeks to under 24 hours.
Robinhood was taking weeks and multiple engineers just to make minor UI tweaks. Their Server Driven UI platform cut that to hours with one engineer.
Lyft Bikes & Scooters was drowning in complexity: 3 vehicle types, multiple markets, and endless switch statements. Their solution? Move the UI logic to the server.
Strava's Android team hit a wall: testing server-driven UI meant wrestling with Charles Proxy crashes, EOF errors, and 3-4 minute build times. An intern decided to fix it.
Tinder was manually creating 40+ localized Lottie animations for every campaign. Their solution? A clever architecture that reduced it to just one.
Robinhood was taking weeks and multiple engineers just to make simple UI changes. Their solution? Server-Driven UI that lets them ship to all platforms without app releases.
Airbnb ships features simultaneously across web, iOS, and Android without waiting for app store releases. Their secret? Server-driven UI.
Siaw Young from Carousell reveals how they built a system that lets them update thousands of product categories without pushing app updates. The secret? A cross-platform markup language that operates at a highe...
Siaw Young from Carousell reveals how they built a server-driven UI system that lets them ship features without app releases. Think HTML for mobile apps—but way more powerful.
Valerii Che from Bumble solved a problem every mobile team faces: how do you ship new animations without waiting days for App Store approval? His solution decouples design updates from release cycles entirely.
Zalando faced an impossible triangle: daily content updates, premium native UX, and distributed teams without native experience. Their solution? Server-driven UI before it was cool.