# server-driven-ui

Server-driven UI is an architecture in which a server sends a structured description of an interface and the client renders it.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Yelp Combines Native and Server-Driven UI for Its AI Assistant

DevFeed: [Yelp Combines Native and Server-Driven UI for Its AI Assistant](<https://devfeed.tech/articles/yelp-combines-native-and-server-driven-ui-for-its-ai-assistant-121237.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/yelp-assistant-hybrid-ui/>)

Author: Leela Kumili

Published: 2026-11-06T14:25:00Z

Content type: article

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [server-driven-ui](<https://devfeed.tech/topics/server-driven-ui.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-architecture](<https://devfeed.tech/tags/ai-architecture.md>), [ai-assistant](<https://devfeed.tech/tags/ai-assistant.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [backend](<https://devfeed.tech/tags/backend.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [chaos](<https://devfeed.tech/tags/chaos.md>), [chat](<https://devfeed.tech/tags/chat.md>), [chatbots](<https://devfeed.tech/tags/chatbots.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [cross-platform](<https://devfeed.tech/tags/cross-platform.md>), [data](<https://devfeed.tech/tags/data.md>), [development](<https://devfeed.tech/tags/development.md>), [event-driven-architecture](<https://devfeed.tech/tags/event-driven-architecture.md>), [faster](<https://devfeed.tech/tags/faster.md>), [framework](<https://devfeed.tech/tags/framework.md>), [large-language-models](<https://devfeed.tech/tags/large-language-models.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mobile-development](<https://devfeed.tech/tags/mobile-development.md>), [native](<https://devfeed.tech/tags/native.md>), [news](<https://devfeed.tech/tags/news.md>), [pilot](<https://devfeed.tech/tags/pilot.md>), [platform](<https://devfeed.tech/tags/platform.md>), [rendering](<https://devfeed.tech/tags/rendering.md>), [server](<https://devfeed.tech/tags/server.md>), [server-driven-ui](<https://devfeed.tech/tags/server-driven-ui.md>), [server-side-rendering](<https://devfeed.tech/tags/server-side-rendering.md>), [ui](<https://devfeed.tech/tags/ui.md>), [yelp](<https://devfeed.tech/tags/yelp.md>), [yelp-assistant-hybrid-ui](<https://devfeed.tech/tags/yelp-assistant-hybrid-ui.md>)

### AI overview

Yelp's AI Assistant uses CHAOS for server-driven conversation rendering while keeping navigation and message input native. The backend sends a view configuration when a chat starts, then sends conversation events that update the existing view without refetching that configuration. Events can carry persistent messages, temporary typing indicators and quick replies, links, or actions such as disabling input when a project request is complete. This separation lets supported presentation changes reach users without a new app release and helped Yelp reuse its Android Assistant for the Biz Ask Anything pilot. The client still handles message state and interactions; recoverable errors trigger retries, while non-recoverable failures disable input and ask users to try again later. Yelp reports coordination and learning costs, and shared implementations may still behave differently across platforms.

### Source excerpt

Yelp combines native mobile controls with server-driven conversation rendering in its AI Assistant using the CHAOS framework. The architecture separates view configuration from conversation data, supports backend-driven chat interactions, and enables faster UI updates without new app releases. Yelp also discusses cross-platform challenges and reuse for its Biz Ask Anything pilot. By Leela Kumili

## Building EGP Cards at Merpay: Lessons from a Frontend Internship

DevFeed: [Building EGP Cards at Merpay: Lessons from a Frontend Internship](<https://devfeed.tech/articles/building-egp-cards-at-merpay-lessons-from-a-frontend-internship-56806.md>)

Original publisher: [Read original article](<https://engineering.mercari.com/en/blog/entry/20251225-building-egp-cards-at-merpay/>)

Author: Yusaku Miyata

Published: 2025-12-25T10:00:01Z

Content type: article

Language: en

Sources: [Mercari Engineering](<https://devfeed.tech/sources/mercari-engineering.md>)

Topics: [Front end](<https://devfeed.tech/topics/frontend.md>), [server-driven-ui](<https://devfeed.tech/topics/server-driven-ui.md>), [No-code](<https://devfeed.tech/topics/no-code.md>), [JSON](<https://devfeed.tech/topics/json.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [UI components](<https://devfeed.tech/topics/ui-components.md>), [dry-run](<https://devfeed.tech/topics/dry-run.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [dry-run](<https://devfeed.tech/tags/dry-run.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [internship](<https://devfeed.tech/tags/internship.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [json](<https://devfeed.tech/tags/json.md>), [no-code](<https://devfeed.tech/tags/no-code.md>), [server-driven-ui](<https://devfeed.tech/tags/server-driven-ui.md>), [ui-components](<https://devfeed.tech/tags/ui-components.md>)

### AI overview

A frontend internship at Merpay involved improving EGP Cards, a no-code tool for creating and publishing card-based UI components across Web, iOS, and Android. The article describes its Server-Driven UI architecture, JSON-based content storage, and a Dry Run feature that uses mock data to preview behavior before API calls or device testing.

### Source excerpt

Building EGP Cards at Merpay: Lessons from a Frontend Internship Hello, my name is @Yusaku (Yusaku Miyata), and I'm currently interning as a Frontend Engineer on the Growth Platform team at Merpay. This article is part of the Merpay & Mercoin Advent Calendar 2025, and I am honored to write the entry for Day 25. [...]

## Supercharging User Engagement: How Mercari is Using Server-Driven UI to Reduce Time-to-Market

DevFeed: [Supercharging User Engagement: How Mercari is Using Server-Driven UI to Reduce Time-to-Market](<https://devfeed.tech/articles/supercharging-user-engagement-how-mercari-is-using-server-driven-ui-to-reduce-time-to-market-56798.md>)

Original publisher: [Read original article](<https://engineering.mercari.com/en/blog/entry/20251214-supercharging-user-engagement-how-mercari-is-using-server-driven-ui-to-reduce-time-to-market/>)

Author: HummStefan

Published: 2025-12-16T10:00:08Z

Content type: article

Language: en

Sources: [Mercari Engineering](<https://devfeed.tech/sources/mercari-engineering.md>)

Topics: [server-driven-ui](<https://devfeed.tech/topics/server-driven-ui.md>), [App](<https://devfeed.tech/topics/app.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [development-process](<https://devfeed.tech/topics/development-process.md>), [UI components](<https://devfeed.tech/topics/ui-components.md>)

Tags: [apps](<https://devfeed.tech/tags/apps.md>), [business-logic](<https://devfeed.tech/tags/business-logic.md>), [components](<https://devfeed.tech/tags/components.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [development-process](<https://devfeed.tech/tags/development-process.md>), [growth](<https://devfeed.tech/tags/growth.md>), [server-driven-ui](<https://devfeed.tech/tags/server-driven-ui.md>)

### AI overview

Mercari's Merpay Growth Platform team describes using server-driven UI in its internal Engagement Platform CRM. The approach introduced a distributable EGP Card content type, enabling remote configuration for campaigns while preserving native performance and appearance. The article discusses the prior platform-specific implementation and its increasing configuration complexity.

### Source excerpt

This post is for Day 16 of Merpay & Mercoin Advent Calendar 2025 , brought to you by @Stefan_droid from the Merpay Growth Platform team. Introduction The Growth Platform team in Merpay is responsible for marketing and incentive related development across the entire company. Over the years, we have built an internal customer relationship management [...]

## Transitioning to Appcraft: Evolution of Zalando's server-driven UI framework

DevFeed: [Transitioning to Appcraft: Evolution of Zalando's server-driven UI framework](<https://devfeed.tech/articles/transitioning-to-appcraft-evolution-of-zalando-s-server-driven-ui-framework-47471.md>)

Original publisher: [Read original article](<https://engineering.zalando.com/posts/2024/05/appcraft.html>)

Author: Kanupriya Gupta

Published: 2024-05-15T22:00:00Z

Content type: article

Language: en

Sources: [Zalando](<https://devfeed.tech/sources/zalando-engineering-blog.md>)

Topics: [server-driven-ui](<https://devfeed.tech/topics/server-driven-ui.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [Framework](<https://devfeed.tech/topics/framework.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [versioning](<https://devfeed.tech/topics/versioning.md>), [JSON](<https://devfeed.tech/topics/json.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [backend](<https://devfeed.tech/tags/backend.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [elm](<https://devfeed.tech/tags/elm.md>), [framework](<https://devfeed.tech/tags/framework.md>), [frameworks](<https://devfeed.tech/tags/frameworks.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [ios](<https://devfeed.tech/tags/ios.md>), [json](<https://devfeed.tech/tags/json.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [server-driven-ui](<https://devfeed.tech/tags/server-driven-ui.md>), [ui](<https://devfeed.tech/tags/ui.md>), [zalando](<https://devfeed.tech/tags/zalando.md>), [zalando-app](<https://devfeed.tech/tags/zalando-app.md>)

### AI overview

Zalando describes Appcraft, a server-driven UI framework for delivering dynamic content across its mobile applications. The article explains why the company replaced the earlier TNA framework, citing rigid UI structures, cross-platform versioning difficulties, schema changes, and release coordination challenges.

### Source excerpt

This article outlines our server-driven UI framework utilised for mobile applications and delves into the reasons for retiring its predecessor.

## Server Driven UI

DevFeed: [Server Driven UI](<https://devfeed.tech/articles/server-driven-ui-24757.md>)

Original publisher: [Read original article](<https://medium.com/ymedialabs-innovation/server-driven-ui-facb948859dc?source=rss----8b5620c36355---4>)

Author: Girish H

Published: 2023-05-25T08:01:03Z

Content type: article

Language: en

Sources: [ymedialabs-innovation](<https://devfeed.tech/sources/ymedialabs-innovation-medium.md>)

Topics: [server-driven-ui](<https://devfeed.tech/topics/server-driven-ui.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [layout](<https://devfeed.tech/topics/layout.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [performance-optimization](<https://devfeed.tech/topics/performance-optimization.md>), [axe monitor](<https://devfeed.tech/topics/axe-monitor.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [android-layout](<https://devfeed.tech/tags/android-layout.md>), [content](<https://devfeed.tech/tags/content.md>), [data](<https://devfeed.tech/tags/data.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mobile-app](<https://devfeed.tech/tags/mobile-app.md>), [mobile-app-development](<https://devfeed.tech/tags/mobile-app-development.md>), [mobile-developer](<https://devfeed.tech/tags/mobile-developer.md>), [mobile-ui-design](<https://devfeed.tech/tags/mobile-ui-design.md>), [native](<https://devfeed.tech/tags/native.md>), [performance](<https://devfeed.tech/tags/performance.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [security](<https://devfeed.tech/tags/security.md>), [server](<https://devfeed.tech/tags/server.md>), [server-driven-ui](<https://devfeed.tech/tags/server-driven-ui.md>), [threats](<https://devfeed.tech/tags/threats.md>), [ui](<https://devfeed.tech/tags/ui.md>), [ui-components](<https://devfeed.tech/tags/ui-components.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>)

### AI overview

Server-driven UI lets a server provide data or instructions that a mobile app uses to build native interface components at runtime, instead of hard-coding every layout. The source presents this as a way to make changes such as adding fields more flexible and potentially shorten development cycles. It contrasts native components with web views on performance, platform-specific experience, security, and accessibility, claiming native components offer advantages in each area. The excerpt ends mid-sentence, so it does not establish the article's full guidance or implementation details.

### 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