Delivering Faster Cross-Platform UX Iteration at Delivery Hero with Server-Driven Tiles
summary
Delivery Hero builds a federated GraphQL supergraph with an Apollo router and a dedicated Tile Subgraph that returns render-ready tiles using @requires to pull domain fields. The system drops heavy SDKs, replaces a 3-month cross-team UI change with a one-week config rollout, resolves one vendor in ~40 ms, and speeds client render by ~100 ms. Implementation uses a federated data model, configuration-driven layouts, stable typed tile grammar, and server-side fallbacks for graceful degradation.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:25About Delivery Hero
- 3:31Cross-platform UX challenge
- 5:59Fluid FMS attempt
- 8:54Fluid FMS lessons
- 11:01Two-layer GraphQL approach
- 13:09Server-driven tiles benefits
- 17:47Tiles with federated GraphQL
- 21:55Tile schema details
- 25:07Current state and future
- 29:24Key solution principles
- 32:58Open floor for questions
related talks
27mTurbocharging the UIs
30mThe Recipe For Scalable Frontends
41m'Divide et impera' with GraphQL and SSR
34mServer Driven UIs: the future of cross-platform rendering
40mThe Recipe For Scalable Frontends
31mReimagining the frontend-backend divide thanks to GraphQL
18mServer-Driven UI: Building Dynamic React Applications
24mIncremental rewrites with React, HTMX, and TanStack Start
