Discover 32 articles on Server Driven UI in mobile performance
Showing 12 of 32 articles (Page 2 of 2)
Daniel Tome from Qantas explores how Server-Driven UI lets you update your mobile app's interface without waiting for App Store approval. It's basically bringing HTML's flexibility to native apps.
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.
Nubank built a Server Driven UI framework that now powers 43% of their app and 70% of all new features. Here's why they ditched traditional mobile releases.
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.