Why Airbnb, Lyft, and Netflix Use Server-Driven UI

Server-Driven UI isn't theoretical. The biggest mobile apps in the world — apps with hundreds of millions of users — have built and deployed SDUI systems in production.

This article breaks down the real implementations at Airbnb, Netflix, Lyft, Shopify, DoorDash, Nubank, Roblox, and Yelp. What problems they faced, what they built, and what they learned.

Airbnb: Ghost Platform

"What if clients didn't need to know they were even displaying a listing? What if we could pass the UI directly to the client and skip the idea of listing data entirely? That's essentially what SDUI does — we pass both the UI and the data together."

— Ryan Brooks, Airbnb (Android Platform Engineer)

What They Solved

• Platform fragmentation — iOS, Android, and web all render from the same response
• Experimentation velocity — "Launching A/B experiments on all platforms is as simple as changing one source of truth"
• Old version updates — Users on outdated app versions still see new features

Key Lesson

Airbnb emphasizes that SDUI requires strong tooling. Without visual editors and debugging tools, the complexity can overwhelm smaller teams.

Netflix: CLCS

"One of the big pros here is the updating of the UI without a client update, because the server itself is what is driving the UI. What is so key about that, especially for our mobile applications, is that we can update the UI without needing to submit it to Apple or to Google."

— Christopher Luu, Netflix (Growth Engineering)

What They Solved

• Device diversity — Netflix runs on TVs, phones, tablets, game consoles. SDUI lets them share logic across wildly different platforms.
• Instant updates — Growth experiments can launch without waiting for app review
• Team scalability — Backend engineers can ship UI without mobile expertise

Lyft: Canvas

"While the migration hasn't been without its pain (it's a pretty big paradigm shift from what we were doing before), it's been a huge boon to our productivity. We went in fully aware of the drawbacks of SDUI and think we've come up with an approach that gives us all of the benefits and solutions to the drawbacks."

— Alex Hartwell, Lyft (iOS Engineer)

What They Solved

• Experimentation speed — Server-driven experiments take 1-2 days vs. 2+ weeks for client-driven
• Live Activities — Dynamic island content updated from the server
• Complex flows — Multi-step ride booking flows controlled entirely from backend

Key Lesson

Lyft notes that SDUI has a snowball effect — "the more you build on top of the platform the more powerful and useful it grows."

Shopify: Shop App

"We were bound by a weekly release cadence. The server-driven UI architecture allows us to launch experiments whenever we deem necessary."

— Shopify Engineering

What They Solved

• Release bottleneck — Broke free from weekly release cycles
• A/B testing — Product team can run experiments without engineering involvement
• Merchant customization — Different stores can have different layouts

DoorDash: Mosaic / Facets

What They Solved

• Generic components — Same component definitions power different features
• Rapid iteration — Marketing banners updated without app releases
• Support tools — Customer service screens updated in real-time

Yelp: CHAOS

What They Solved

• 8 clients, 1 response — Massive reduction in code duplication
• Instant changes — UI updates propagate to all platforms simultaneously
• Consistency — Users get identical experience regardless of platform

Nubank: Catalyst

What They Solved

• Multi-market complexity — Different regulations, languages, and product configurations across 3 countries managed from a single backend
• Feature velocity — New financial products ship in minutes, not weeks
• Flutter + SDUI — Built on Flutter with a custom DSL, proving SDUI works at massive scale in cross-platform frameworks

Read the full breakdown: How Nubank Uses Server-Driven UI to Ship Features to 115 Million Customers in Minutes

Roblox: SDUI for Growth

What They're Building

• SDUI-powered growth engine — "Building a scalable engine—including SDUI, deep linking, and automated notification stacks—to deploy dynamic growth interventions"
• Lifecycle management — Transitioning from "merchandising mindset" to "lifecycle engine mindset" across acquisition, activation, retention, and reactivation
• 18+ audience expansion — As Roblox matures its content catalog, SDUI enables rapid experimentation with different user segments without app updates

Key Lesson

Roblox's hiring signals that SDUI is evolving beyond a mobile engineering tool into core growth infrastructure. When a $68B company builds their growth strategy around SDUI, it validates the pattern for every team doing mobile experimentation. See also: SDUI for Growth Engineering.

Common Patterns Across All Companies

Looking at these implementations, several patterns emerge:

1. They All Built Custom

Every major company built their own SDUI system. Why? Because existing tools didn't meet their scale or flexibility requirements. This is changing as productized solutions emerge.

2. GraphQL is Popular

Airbnb, Shopify, Yelp, and DoorDash all use GraphQL for their SDUI APIs. The strong typing and flexibility of GraphQL maps well to UI definitions.

3. Incremental Adoption Works

None of these companies went "all SDUI" overnight. They started with specific flows (experiments, onboarding, settings) and expanded over time.

4. Tooling is Critical

Every team emphasizes that SDUI without good tooling is painful. Visual editors, debugging tools, and testing infrastructure are essential.

What This Means for Your Team

The pattern is proven — and the business case for SDUI is clear. The question isn't whether SDUI works — it's whether you have the resources to build it yourself.

Most companies don't have the engineering bandwidth to spend 6-12 months building custom infrastructure. That's why we built Pyramid — get started in minutes, not months.