Universal Apps: Architecture for the Modern Web
summary
Claim: rendering pages on the server and sending serialized state lets the browser hydrate without repaints, giving immediate content for SEO and perceived speed while switching to SPA interactivity. Implements with React or Vue and frameworks like Next/Nuxt; React 16 improved server renders. Costs are concrete: two runtime environments, missing window/document on Node, need isomorphic npm modules, caching or streams for performance, and testing both server-rendered and client-hydrated states.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:54Agenda
- 1:20Web Architectures
- 1:48Single Page Apps
- 2:47Why Build Universal Apps
- 3:16Perception of Performance
- 3:49Developer Benefits
- 4:25Framework Support
- 4:57Next React
- 5:20Initial State
- 6:30Visual Example
- 7:07Environments
- 8:05Performance
- 8:31Testing
- 9:18Conclusion
related talks
24mUniversal Applications
45mBuilding Isomorphic Apps (Updated)
44mServer Side Rendering from the trenches
33mUniversal React Apps Using Next.js
47mFrontend Architectures: The Next Generations
22mUniversal React Apps Using Next.js
31mDecoupled, Not Disconnected: State and Sync in Micro-Frontends
33mRendering on the Web: Performance Implications of Application Architecture