# server-driven-ui Published articles for server-driven-ui. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How Yelp Keeps Server-Driven UI Consistent Across Four Platforms DevFeed: [How Yelp Keeps Server-Driven UI Consistent Across Four Platforms]() Original publisher: [Read original article]() Author: Radu Comaneci, Software Engineer Published: 2026-04-22T00:00:00Z Content type: article Language: en Sources: [Yelp]() Topics: [Design system](), [cross-platform](), [ui](), [Web](), [Android](), [iOS](), [Framework]() Tags: [android](), [cross-platform](), [design-system](), [ios](), [platforms](), [server-driven-ui](), [ui](), [web]() ### AI overview This article explains how Yelp integrates its CHAOS server-driven UI framework with the Cookbook design system and the auto-generated Konbini bridge library. The approach is intended to keep UI components and their behavior consistent across Yelp's Web, iOS, and Android applications, including Python/CHAOS backend representations. ### Source excerpt If you've read our earlier post, you already know about CHAOS--the server-driven UI (SDUI) framework we built at Yelp that powers our dynamic views. Until now, we've explored its architecture, backend implementation, and component model. In this post, we'll dive into how we integrated CHAOS with Yelp's cross-platform design system, Cookbook, and the auto-generated bridge library, Konbini. Introduction to Cookbook At Yelp, we support two major applications across our Web, iOS, and Android platforms: Yelp and Yelp for Business. This results in six different variations, which makes it challenging to maintain a unified experience. To address this challenge, we created... ## Ship products faster with SDUI DevFeed: [Ship products faster with SDUI]() Original publisher: [Read original article]() Author: Shane Myrick Published: 2023-07-13T18:35:59Z Content type: tutorial Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [GraphOS](), [ui](), [backends](), [API]() Tags: [apis](), [business-logic](), [graphos](), [graphql](), [how-to](), [server-driven-ui]() ### AI overview This post explains how travel companies can use Server-Driven UI with GraphQL to move changeable business logic from client applications to the server. It argues that centralizing frequently updated logic can reduce coordination across multiple apps and enable faster updates without waiting for app releases. ### Source excerpt This post is a part of our "How to build connected travel apps with Apollo GraphOS" series. Also in this series: - Delivering personalized travel experiences with GraphQL - Mitigate scraping and bot attacks with GraphOS - Seamlessly integrate with partners to enhance the travel experience When booking a vacation there are many different steps that require very different needs. ## Server Driven UI DevFeed: [Server Driven UI]() Original publisher: [Read original article]() Author: Girish H Published: 2023-05-25T08:01:03Z Content type: tutorial Language: en Sources: [ymedialabs-innovation - Medium]() Topics: [ui](), [Mobile](), [Development](), [Web]() Tags: [accessibility](), [android](), [android-app-development](), [kotlin](), [mobile](), [mobile-app-development](), [mobile-ui-design](), [performance](), [server-driven-ui](), [ui](), [ui-components]() ### AI overview This article explains server-driven UI, in which a server provides data or instructions that a mobile app uses to render native interface components dynamically. It presents the approach as a way to reduce hard-coded layout changes and improve flexibility, and compares native components with web views in performance, user experience, security, and accessibility. ### Source excerpt Photo by Amélie Mourichon on Unsplash Server-driven UI or dynamic layout is a technique that allows the server to send data or instructions to the client, which the client then uses to render the user interface dynamically. This can improve the user experience by providing more personalised or relevant content Why do we need to use Server Driven UI? As a mobile developer, have you ever had to add a new field to a native Android layout and it would take up the entire sprint which includes development, QA and release cycle? Or, have you ever had a client who was hesitant to use web views to render content in their app? These are common issues that can be solved by implementing server-driven UI in your mobile app. Server-driven UI allows developers to render native components using data provided by a server. This means that instead of hard-coding all the layouts in the app, you can fetch the data from a server and dynamically create the UI components at runtime. This can save a lot of development time and make the app more flexible to changes in the future. Additionally, using server-driven UI can also improve the performance as the native components are rendered directly in the app, which can lead to faster load times and better performance overall. You can find some of the major differences between Native components and web-view below Performance: Native components are much faster and provide better performance as compared to web views. Web views usually require a lot of resources to render the content, which can result in slow loading times and a poor user experience. User experience: Native components provide a better user experience as they are designed specifically for the platform they are running on. They can take advantage of the device's features and offer a consistent look and feel across the entire app. Security: Native components are considered more secure as compared to web views. Web views can be vulnerable to security threats such as cross-site scriptin ## Implementing Server-Driven UI Architecture on the Shop App DevFeed: [Implementing Server-Driven UI Architecture on the Shop App]() Original publisher: [Read original article]() Author: Ashwin Narayanan Published: 2022-11-22T16:00:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Mobile](), [ui](), [Shopify](), [App](), [Development]() Tags: [architecture](), [experiments](), [intern](), [mobile](), [release-cadence](), [server-driven-ui](), [shopify](), [ui]() ### AI overview Shopify's Shop Store team implemented server-driven UI for the Shop App's Store Screen. The architecture lets the server control store sections and customize layouts for different merchants, while addressing component reuse, compatibility with older clients, and faster experimentation. ### Source excerpt Ashwin explains why and how we implemented server-driven UI in the Shop App's Store Screen, and his experience working on the project as a Dev Degree intern. ## The Backend Developer's Guide to GraphQL Summit 2022 DevFeed: [The Backend Developer's Guide to GraphQL Summit 2022]() Original publisher: [Read original article]() Author: Melissa Annecchini Published: 2022-09-06T14:56:04Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [Back end](), [API](), [Security](), [gateway](), [Localization (l10n)]() Tags: [announcement](), [api](), [apollo](), [apollo-federation](), [backend](), [batching](), [conference](), [developer](), [gateway](), [global](), [graphql](), [guide](), [resolvers](), [security](), [server-driven-ui](), [summit]() ### AI overview A guide to GraphQL Summit 2022 for backend developers, highlighting sessions on supergraph management, GraphQL security testing, Apollo Federation batching, server-driven UI, and localization. ### Source excerpt Calling all backend developers! If you are looking to learn more about building, managing, and securing your supergraph at scale, then this blog is for you. Read on for your backend developer's guide to GraphQL Summit 2022. #ICYMI: GraphQL Summit 2022 is back in person October 3-5 in San Diego for 3 days of surf, sun, and all things GraphQL. Register today to avoid all the FOMO. ## Kotlin Mumbai: Multiplatform projects and server-driven UI DevFeed: [Kotlin Mumbai: Multiplatform projects and server-driven UI]() Original publisher: [Read original article]() Author: Siddhesh Patil Published: 2021-08-18T18:15:34Z Content type: article Language: en Sources: [Sid Patil - Android Engineer and Kotlin Advocate]() Topics: [Kotlin Multiplatform](), [multiplatform](), [Compose](), [GraphQL](), [SwiftUI](), [Android](), [ui]() Tags: [adit-lal-talks](), [android](), [android-events-in-mumbai](), [apollo](), [best-android-developer-communities](), [compose](), [declarative](), [development](), [gde-talks](), [gdg-groups](), [graph-ql](), [graphql](), [ios](), [jetpack-compose](), [john-oreilly-talks](), [kotlin](), [kotlin-for-ios](), [kotlin-multiplatform](), [kotlin-mumbai](), [kotlin-user-groups](), [multiplatform](), [server-driven-ui](), [server-driven-ui-using-compose-and-epoxy](), [swiftui](), [ui]() ### AI overview An event page describing Kotlin Mumbai talks on server-driven UI and on using GraphQL with Apollo in Kotlin Multiplatform projects. The talks cover shared iOS and Android code, Jetpack Compose on Android, and SwiftUI on iOS. ### Source excerpt Build multiplatform projects with SwitfUI and compose and learn the art of server driven UI on Android with John Oreilly and Adit Lal