What is Server-Driven UI?

Server-driven UI is an emerging technique used by companies like Airbnb, Lyft, and Zapier for:
- more component-driven development
- a balance of personalization and performance
- better content workflows for teams
Examples of server-driven UI platforms include Builder.io (www.builder.io)

[@bpospanov]

very short and useful. thank you

[@angelotessaro]

Very good and dynamic explanation. Thank you!

[@niteshjaiswar7805]

great explanation. thank you

[@techbro3085]

Very nice information

[@abhishekshrestha7437]

Thanks for the solid advice! How would you tackle seo with this approach?

[@brawnyvenky9584]

Thanks for the video. Can you point us to a tutorial where we can build this purely with react without any custom libraries.

[@shubhamdeshmukh9287]

awesome

[@user-wm8dc8rw8r]

You haven't mentioned a few very valuable benefits of using server driven ui:
1. It ensures consistent UI between different platforms (in case you have a web app and native apps).
2. Native apps are difficult to update, it takes much longer than just updating a js file on a website and some users are reluctant to update their apps. So, it provides a much easier and faster way to update native app.

[@yashmmee]

Thanks for great the content!
Its interesting that html can be mapped one and only one json. But html is easier to read and work than a json. So we write web in html not json.
But now, our html (jsx) files are so bloated that is scary to non-dev teammates and we can’t tell them go there edit what you want.
So, now we fall backed to json because html and jsx no good anymore and created a full blown gui on top of it, so other can work with it.
In an ideal world, our markup is so clean and intuitive that other people could work on the same file. You know, web was not only accessible to read , but also accessible to write and edit.
(I like how Astro is trying to feel this gap here)
In a practical world, this is really cool way to solve
Thank for sharing