Revisiting Server-Driven UI

preview_player
Показать описание
In this episode of Front End Happy Hour, we dive back into the world of server-driven UI with fresh insights and experiences. Our special guest, Sherman Chen, a Senior Software Engineer at LinkedIn, joins us to share how LinkedIn leverages server-driven UI to enhance their applications. Tune in as we explore the benefits, challenges, and best practices for implementing server-driven UI in modern development.

0:00 - Introduction and Topic Overview
0:34 - Guest Introductions
2:24 - What is Server-Driven UI?
4:43 - Defining Server-Driven UI
6:12 - Early Experiences with Server-Driven UI
7:12 - Benefits of Server-Driven UI
8:24 - Challenges with Server-Driven UI
10:09 - Organizational and Implementation Issues
13:12 - Scaling and Complexity
16:51 - Interaction and State Management
18:23 - Fragmentation and Collaboration
21:40 - Case Studies and Examples
24:39 - Practical Applications
27:31 - Setting Boundaries and Expectations
28:33 - Remote Work and Communication Challenges
32:22 - Importance of UI Contracts
34:26 - Advice for Implementing Server-Driven UI
36:30 - Final Thoughts and Recommendations
38:38 - Listener Q&A and Closing Remarks
47:44 - Picks and Recommendations
Рекомендации по теме
Комментарии
Автор

Wow finally a podcast with active seniors developers talking about things that actually matter in software development!

SonAyoD
Автор

Great conversation! The All-In for devs. Love it.

OvercomerIdemudia
Автор

on the web, querystring was still used for a while for load-balanced session IDs to scale out web servers better (before the session could be reliably pinned at layer 7 to one server).. it also became real nice on web apps when the hosting app (browser) could close out and reopen (within a certain timeframe) and the user not have to log in and find the last page they were at, as long as they're coming from the same IP and haven't changed app versions (or w/e your constraints are).

ifatreefalse
Автор

Such an excelent perspective subscribed !

EliSoftwareDeveloper
Автор

One aspect to mention is that we are paying for the compute of the "UI logic" when done server side, but client side counting with the compute power of the client is the way to go most of the time. Most of the reasons I heard are not strong enough to justify having to compute/pay server side.

bodyproblems
Автор

What about SDUI for just design systems and assets? I mean is there any scope for SDUI without components. Because there are still many companies who don’t take tokenisation approach and hard-code literally everything. Do you there there is a scope of some product solving that issues ie, democratising SDUI?

m.design
Автор

Love the guy pointing out "This is just html"
yup that kinda sums it up

danielschmider
Автор

what are your thoughts on Flutter? Working with a single codebase for multiple platforms.

NikhilKesari