# 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