This discussion is designed to clarify the differences between client and server components, highlighting their respective advantages and disadvantages. Additionally, it will examine situations that determine the appropriate use of each type of component.

Building a server driven UI with React is perfect as Reacts dynamic nature makes it easy to render and update UIs based on API responses but it still requires many round trips over the network. React 19 and RSCs are a perfect solution to this problem! By leveraging the new features in React 19 we can now build an even more performant server driven UI. In this talk I’ll demo how I’ve been able to leverage React 19 and RSCs in an enterprise application to build server driven UIs.

Migrating a production app is not an easy feat, especially if it's actively being used by over a million people. In this talk, we'll explore how we rebuilt our homepage and product page on the app directory using next.js 13. We'll highlight some of the challenges we faced and the solutions we came up with

I’ve been building UI components with React for a while now, and I’ve read a lot about server-side rendering (SSR). From what I’ve read, I didn’t expect SSR to affect how React components are built.

Lately, I’ve been working on a component library, and one of the consumer teams I worked with uses SSR. After building many components, I received feedback that several of them weren’t working correctly when SSR was used. This got me thinking about why this was happening and how SSR might affect building React components.