Turbocharging the UIs
summary
Zomato describes two concrete wins: using react server components on Next 13/14 to stream HTML and fetch data on the server, cutting client JavaScript to zero for many UI parts, hitting smooth 60 FPS and much higher Lighthouse scores and rendering over 700 static pages for Weather Union; and adopting module Federation to split a monolithic restaurant partner dashboard so teams ship independent micro UIs (an ads management center launched separately) reducing release friction and speeding delivery in production.
AI-written summary · about
chapters (10)
- 0:00Introduction to Turbocharging UIs
- 2:30React Server Components overview
- 7:30Data fetching in Next.js
- 11:50Pages vs App Router
- 13:59How RSCs solve problems
- 17:34Zomato’s RSC implementation
- 19:42Module Federation introduction
- 22:10Monolith to micro frontends
- 24:20Module Federation results
- 26:06Closing and future plans
related talks
45mSpeeding up Code, Webpages and Teams
32mPractical Performance Tips Building Progressive Web Apps
43mDelivering Faster Cross-Platform UX Iteration at Delivery Hero with Server-Driven Tiles
31mSpeeding up Startup for Large React Apps
17mThe Frontend Cloud: Crafting superior web experiences
24mOptimising React’s TTI
31mReact Server Components Elevating Speed, Interactivity, and User Experience
29mQuo vadis, frontend?
